architecture
Architecture guides decision-making through requirements analysis, trade-off evaluation, and ADR documentation. It helps teams capture design rationale and choose patterns systematically, emphasizing simplicity and constraint-aware choices.
Architecture documents your system design decisions using trade-off analysis and ADR templates.
AI-generated summary based on this skill's SKILL.md
Install
vudovn/ag-kit/architecture · repository language: TypeScript
git clone https://github.com/vudovn/ag-kit
cp -r ag-kit/.agents/skills/architecture ~/.claude/skills/architecturenpx skillfed install vudovn/ag-kit/architectureFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How to make architecture decisions with Architecture?
Architecture guides your decision-making by starting with requirements analysis and constraint identification. The skill helps you evaluate trade-offs systematically, compare architectural patterns against your specific needs, and document choices using ADR (Architecture Decision Record) templates. This ensures decisions are captured with clear rationale, making it easier for teams to understand why patterns were chosen and what alternatives were considered.
What is an architecture decision record template?
Architecture provides ADR templates that structure how you document architectural decisions. An ADR captures the decision context, options evaluated, the chosen solution, and its trade-offs. Architecture emphasizes documenting your design rationale so teams can reference the reasoning behind pattern selections, constraints that drove choices, and consequences of each decision. This framework helps maintain institutional knowledge across projects.
How does Architecture help with system design trade-off analysis?
Architecture enables trade-off analysis by helping you map requirements and constraints against architectural options. The skill guides you through evaluating patterns systematically—weighing factors like simplicity, scalability, team capability, and maintenance burden. Architecture emphasizes constraint-aware choices, ensuring your final design reflects realistic trade-offs rather than theoretical ideals, and documents these trade-offs so future decisions build on clear reasoning.
How do I document architecture decisions using Architecture?
Architecture provides structured ADR documentation frameworks that capture decision context, alternatives considered, and rationale. The skill guides you through writing clear decision records that explain what problem you solved, why you chose your pattern, and what trade-offs you accepted. This documentation approach helps teams validate architecture against requirements and makes it easier to revisit decisions when constraints or capabilities change.
Can Architecture help me evaluate and compare architectural patterns?
Yes. Architecture guides pattern evaluation by helping you analyze requirements and constraints first, then systematically compare options against those criteria. The skill supports trade-off assessment before finalizing choices, ensuring you understand the consequences of each pattern. Architecture emphasizes choosing patterns that fit your team's capabilities and project constraints, not just selecting theoretically optimal designs.
What makes Architecture's approach to design decisions different?
Architecture emphasizes simplicity and constraint-aware decision-making rather than pursuing perfect designs. The skill combines requirements analysis, systematic pattern comparison, and ADR documentation to create a complete decision framework. By capturing trade-off rationale and validating choices against team capabilities, Architecture helps teams make decisions they can actually execute and maintain, while building shared understanding across the organization.
SKILL.md
rendered from the published skill — quoted content, verbatim
Architecture 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
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 6 files
.agents/skills/architecture/SKILL.md
.agents/skills/architecture/context-discovery.md
.agents/skills/architecture/examples.md
.agents/skills/architecture/pattern-selection.md
.agents/skills/architecture/patterns-reference.md
.agents/skills/architecture/trade-off-analysis.md