Architecture Decision Framework
SkillDocs & knowledgeArchitecture is an agent skill that provides an architectural decision-making framework. It guides the agent through requirements analysis, trade-off evaluation, and ADR documentation when making architecture decisions or analyzing system design.
Available today. Use it from your connected AI after setup.
No other account needed.
Have an agent environment that supports loading skills.
Then ask your AI: use the Architecture Decision Framework skill
What your AI can do with it
- Asks discovery questions to classify the project before designing
- Evaluates trade-offs between architecture options
- Records decisions as ADRs using provided templates
- Selects patterns using decision trees and anti-pattern guidance
- References MVP, SaaS, and Enterprise example architectures
- Runs a validation checklist before finalizing architecture
Getting started
- Have an agent environment that supports loading skills.
- Add the architecture skill to your available skills.
- Ask the agent to make an architecture decision or analyze a system design; it will ask discovery questions, weigh trade-offs, and write ADRs.
- Optionally pair it with related skills such as database-design, api-patterns, or deployment-procedures.
What this skill tells your AI
The instructions your AI receives, as published by davila7/claude-code-templates in cli-tool/components/skills/development/architecture/SKILL.md and read by ahel’s review.
"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
Signals
- GitHub stars
- 32k
- Forks
- 4k
- Last commit
- Sep 2026
Others that do the same job
Questions
- What does the skill read?
- It only reads project files and its own reference documents, covering context discovery, trade-off analysis, pattern selection, examples, and a patterns reference. It reads only files relevant to the request.
- When should I use it?
- Use it when making architecture decisions or analyzing system design, such as starting an architecture design or documenting decisions.
- Does it modify my project?
- Its allowed tools are Read, Glob, and Grep, so it reads files rather than modifying them; it records choices as ADRs using templates.
- What principle does it follow?
- Start simple and add complexity only when proven necessary, since removing complexity is much harder than adding it.
Advanced
- Item type
- skill
- Key
architecture-davila7- Source
- github.com/davila7/claude-code-templates