domains / families / software-engineering / architecture-designer

architecture-designer

separate

Use when designing new high-level system architecture, reviewing existing designs, or making architectural decisions. Invoke to create architecture diagrams, write Architecture Decision Records (ADRs), evaluate technology trade-offs, design component interactions, and plan for scalability. Use for system design, architecture review, microservices structuring, ADR authoring, scalability planning, and infrastructure pattern selection — distinct from code-level design patterns or database-only design tasks.

When to use

• Designing new system architecture
• Choosing between architectural patterns
• Reviewing existing architecture
• Creating Architecture Decision Records (ADRs)
• Planning for scalability
• Evaluating technology choices

When not to use

• code-level design patterns
• database-only design tasks

Skill page

Source