Claude skill
Architecture
Architecture is a Claude skill in the Engineering plugin, built by Anthropic. Create or evaluate an architecture decision record (ADR).
What it does
The description in the skill's SKILL.md, which Claude reads to decide when to use it:
Create or evaluate an architecture decision record (ADR). Use when choosing between technologies (e.g., Kafka vs SQS), documenting a design decision with trade-offs and consequences, reviewing a system design proposal, or designing a new component from requirements and constraints.
The skill's instructions (about 305 words) cover:
- Usage
- Modes
- Output — ADR Format
- If Connectors Available
- Tips
How to use it
- Architecture comes inside the Engineering plugin, so you get it by installing that plugin, along with its 9 other skills. A plugin installs as one unit, with all its skills. The plugin's page has the install steps, and plugins are saved to your Claude account.
- Ask Claude for the task. When your request matches the skill's description, Claude loads it.
- To pick it yourself in Claude chat, type
/or click + and choose architecture. In Claude Code and Cowork, type:/engineering:architecture <decision or system to design>
Source
- Plugin
- Engineering (Anthropic)
- SKILL.md
- View on GitHub
- Repo stars
- 36,253
- Repo last pushed
- Nov 13, 2026
- Checked
- Nov 16, 2026
More skills in Engineering
- Code ReviewReview code changes for security, performance, and correctness.
- DebugStructured debugging session — reproduce, isolate, diagnose, and fix.
- Deploy ChecklistPre-deployment verification checklist. Use when about to ship a release, deploying a change with database migrations or feature flags, verifying CI status and approvals before going to production…
- DocumentationWrite and maintain technical documentation.
- Incident ResponseRun an incident response workflow — triage, communicate, and write postmortem.
- StandupGenerate a standup update from recent activity.
- System DesignDesign systems, services, and architectures.
- Tech DebtIdentify, categorize, and prioritize technical debt.
- Testing StrategyDesign test strategies and test plans. Trigger with "how should we test", "test strategy for", "write tests for", "test plan", "what tests do we need", or when the user needs help with testing…