architecture
Architecture helps you build decision records for technology choices, system designs, and architectural proposals. It structures your analysis across options, trade-offs, and consequences—whether you're choosing between platforms like Kafka and SQS, reviewing a microservices design, or building a new component from requirements.
Architecture creates structured decision records that document technology choices with options, trade-offs, and consequences.
AI-generated summary based on this skill's SKILL.md
Install
anthropics/knowledge-work-plugins/architecture · repository language: Python
git clone https://github.com/anthropics/knowledge-work-plugins
cp -r knowledge-work-plugins/engineering/skills/architecture ~/.claude/skills/architecturenpx skillfed install anthropics/knowledge-work-plugins/architectureFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How do I create an architecture decision record?
Architecture helps you build structured decision records (ADRs) to document and justify technology choices. Start by defining the decision context, list the options you're evaluating, analyze trade-offs for each option, document your chosen solution, and record the consequences. ADRs create a clear audit trail of why architectural decisions were made, making it easier for teams to understand past choices and their rationale.
How should I evaluate system design proposals?
Architecture guides you through reviewing proposed designs against your requirements and constraints. Assess each proposal by examining its trade-offs, scalability implications, operational complexity, and alignment with your system goals. Document what works well, identify potential risks, and note any action items needed before implementation. This structured critique helps teams make informed decisions before committing resources.
What's the best way to compare event bus options like Kafka vs SQS?
Architecture supports comparing multiple architectural options with trade-off analysis. When evaluating Kafka versus SQS, consider factors like throughput requirements, latency needs, operational overhead, cost structure, and integration complexity. Document the strengths and weaknesses of each option, then justify your selection based on your specific constraints and priorities. This comparison becomes part of your decision record.
How can I design a new system component from scratch?
Architecture helps you design new system components and services starting from requirements and constraints. Define what the component must accomplish, identify your technical and operational constraints, explore multiple design approaches, analyze their trade-offs, and document your chosen architecture with its consequences. This ensures your design is deliberate and justified rather than ad-hoc.
What should I document about architectural decisions?
Architecture emphasizes documenting not just the decision itself, but also the consequences and action items that follow. Record the context that prompted the decision, the options considered, the rationale for your choice, and any follow-up work needed. This comprehensive documentation helps future team members understand the full picture and anticipate downstream impacts.
What's an effective architecture decision-making framework?
Architecture provides a structured framework for technology selection and system design decisions. It guides you to clarify the decision context, enumerate realistic options, perform trade-off analysis across multiple dimensions, make an explicit choice with clear reasoning, and document consequences. This systematic approach reduces bias, ensures stakeholder alignment, and creates a valuable record for organizational learning.
SKILL.md
rendered from the published skill — quoted content, verbatim
/architecture
> If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Create an Architecture Decision Record (ADR) or evaluate a system design.
Usage
/architecture $ARGUMENTS
Modes
Create an ADR: "Should we use Kafka or SQS for our event bus?" Evaluate a design: "Review this microservices proposal" System design: "Design the notification system for our app"
See the system-design skill for detailed frameworks on requirements gathering, scalability analysis, and trade-off evaluation.
Output — ADR Format
```markdown
ADR-[number]: [Title]
Status: Proposed | Accepted | Deprecated | Superseded Date: [Date] Deciders: [Who needs to sign off]
Context
[What is the situation? What forces are at
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 1 file
engineering/skills/architecture/SKILL.md