Architecture Patterns
Domain skill for system design, structural evaluation, and architecture decisions.
Iron Law
DESIGN ARCHITECTURE FROM FUNCTIONALITY, NOT TO FUNCTIONALITY. If you can't trace a component to a user flow, delete it.
Architecture serves user flows. Not the other way around.
Prerequisite: Map Flows First
Before designing ANYTHING, enumerate flows. Track each design activity as a task:
TaskCreate("Map user/admin/system flows", "Enumerate all flows before des
[Description truncada. Veja o README completo no GitHub.]