Skip to content

architecture

“Requirements drive architecture. Trade-offs inform decisions. ADRs capture rationale.”

Read ONLY files relevant to the request! Check the content map, find what you need.

FileDescriptionWhen to Read
context-discovery.mdQuestions to ask, project classificationStarting architecture design
trade-off-analysis.mdADR templates, trade-off frameworkDocumenting decisions
pattern-selection.mdDecision trees, anti-patternsChoosing patterns
examples.mdMVP, SaaS, Enterprise examplesReference implementations
patterns-reference.mdQuick lookup for patternsPattern comparison

SkillUse For
@[skills/database-design]Database schema design
@[skills/api-patterns]API design patterns
@[skills/deployment-procedures]Deployment architecture

“Simplicity is the ultimate sophistication.”

  • Start simple
  • Add complexity ONLY when proven necessary
  • You can always add patterns later
  • Removing complexity is MUCH harder than adding it

Before finalizing architecture:

  • Requirements clearly understood
  • Constraints identified
  • Each decision has trade-off analysis
  • Simpler alternatives considered
  • ADRs written for significant decisions
  • Team expertise matches chosen patterns

Always identify gaps and suggest next steps to users. In case there is no gaps anymore, then AI should clearly state that there is no gap left.