About architecture
An architecture decision skill that helps teams derive designs from requirements, evaluate trade-offs, and record significant choices as ADRs. It favors starting simply and provides references for selecting patterns and reviewing decisions.
Key features
- 01Requirement- and constraint-led design
- 02Trade-off analysis and ADR templates
- 03Pattern selection references
- 04Validation checklist for architecture decisions
Use cases
- 01Choosing patterns for a new system
- 02Recording rationale for major architecture choices
- 03Reviewing whether a design is more complex than necessary
Install
Copy the command and run it in a terminal.
$
npx skills add https:/After installing, type/architecturein Claude Code to confirm it loaded.
Bundled files
References and scripts installed along with SKILL.md.
context-discovery.mdexamples.mdpattern-selection.mdpatterns-reference.mdtrade-off-analysis.mdDetails
From the project READMEArchitecture Decision Framework
"Requirements drive architecture. Trade-offs inform decisions. ADRs capture rationale."
🎯 Selective Reading Rule
Read ONLY files relevant to the request! Check the content map, find what you need.
| File | Description | When to Read |
|---|---|---|
context-discovery.md | Questions to ask, project classification | Starting architecture design |
trade-off-analysis.md | ADR templates, trade-off framework | Documenting decisions |
pattern-selection.md | Decision trees, anti-patterns | Choosing patterns |
examples.md | MVP, SaaS, Enterprise examples | Reference implementations |
patterns-reference.md | Quick lookup for patterns | Pattern comparison |
🔗 Related Skills
| Skill | Use For |
|---|---|
@[skills/database-design] | Database schema design |
@[skills/api-patterns] | API design patterns |
@[skills/deployment-procedures] | Deployment architecture |
Core Principle
"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
Validation Checklist
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
When to Use
This skill is applicable to execute the workflow or actions described in the overview.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Comments
Markdown supported