Architecture Designer puts Claude in the role of a principal architect. It collects functional and non-functional requirements, matches them to architecture patterns, draws the result and records each significant choice as an ADR.
The skill pushes for explicit trade-offs, failure modes and operational cost, and warns against building for scale that nobody has asked for.
What You Get
- A requirements summary covering functional and non-functional needs
- A Mermaid architecture diagram of the main components and data flow
- ADRs with status, context, decision, alternatives and consequences
- Technology recommendations with a rationale for each
- A list of risks with mitigations
Common Use Cases
- Choosing between a monolith and microservices
- Writing an ADR for a database selection
- Reviewing an existing design for single points of failure
- Planning how a system will scale
- Gathering non-functional requirements before a build
What Makes It Unique
The skill is for high-level design, and it says so: it is separate from code-level design patterns and from database-only work. Its references include an ADR template, a database selection guide and a non-functional requirements checklist, and its rules require alternatives to be evaluated before any technology is chosen.
Under The Hood
The skill is a SKILL.md with five reference files on patterns, the ADR template, system design, database selection and non-functional requirements. It has no scripts and runs no commands. The agent reads the references that match the task and writes the design as text, Mermaid and markdown documents. It does not fetch web pages or call outside APIs.