
Use when: Initiating a new software project
How it works:
Prioritize deep research before starting code development to ensure valuable direction.
Use architectural forensic analysis to align business logic and technical feasibility, treating code as a liability needing justification.
Tip: Avoid blind adoption of new frameworks; focus on context preservation and long-term asset value.
Use when: Developing AI-augmented solutions
How it works:
Prioritize preserving the intent behind system designs, ensuring each decision log is documented.
Build audit-ready systems with transparent logic for stakeholders to understand.
Tip: Prevent "Architectural Amnesia" by maintaining human understanding of system functions.
Use when: Planning new feature implementation
How it works:
Simulate the feature's lifecycle to preemptively identify potential technical debts.
Analyze AI-generated modules to catch issues that might arise at scale.