About architecture
A software architecture skill for developers planning system designs. It guides requirements discovery, pattern selection, trade-off analysis, and recording significant decisions as ADRs, with an emphasis on starting simply.
Key features
- 01Requirements and constraint discovery
- 02Architecture pattern selection
- 03Trade-off analysis and ADR templates
- 04Examples for MVP, SaaS, and enterprise
- 05Final architecture validation checklist
Use cases
- 01Clarifying requirements before designing a system
- 02Comparing architecture patterns and their trade-offs
- 03Recording rationale for significant design decisions
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
Comments
Markdown supported