architecture
Architectural decision-making framework. Includes requirements analysis, trade-off evaluation, and ADR documentation templates for systematic system design.
Introduction
The Architecture skill provides a structured framework for engineering teams to navigate complex system design challenges. It is designed for software architects, lead developers, and technical project managers who need to ensure that architectural choices are well-documented, defensible, and aligned with project constraints. By emphasizing the principle that simplicity is the ultimate sophistication, this skill helps users avoid over-engineering while providing a rigorous methodology for evaluating competing design alternatives.
-
Facilitates systematic requirements analysis to identify core constraints and project scope.
-
Provides templates for Architectural Decision Records (ADRs) to capture the context, consequences, and rationale behind design choices.
-
Includes a trade-off analysis framework to evaluate pros and cons across performance, scalability, maintainability, and complexity.
-
Offers decision trees and pattern-selection guides to assist in choosing between monolithic, microservices, serverless, or event-driven architectures.
-
Supports integration with other domain-specific skills like database schema design, API patterns, and deployment procedures.
-
Use this skill when initiating a new project to perform context discovery or when proposing changes to existing system architecture.
-
Inputs typically involve project requirements, technical constraints, or performance bottlenecks; outputs include structured decision logs and recommended architectural patterns.
-
Follow the validation checklist to ensure all decisions have clear trade-offs, simpler alternatives have been considered, and the chosen pattern matches team expertise.
-
Always prioritize the 'Selective Reading Rule': only consult the files relevant to the current decision (e.g., check pattern-selection.md for choosing technologies or trade-off-analysis.md for documenting impact).
-
Remember that while complex patterns have their place, they should only be introduced when strictly necessary, as removing complexity is significantly harder than adding it.
Repository Stats
- Stars
- 7,243
- Forks
- 1,430
- Open Issues
- 36
- Language
- TypeScript
- Default Branch
- main
- Sync Status
- Idle
- Last Synced
- Apr 29, 2026, 07:00 AM