architecture-designer

Design high-level system architectures and document decisions with Mermaid diagrams and ADRs.

19|3|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/dirien/yet-another-agent-harness --skill architecture-designer-dirien
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-designer
Source: https://github.com/dirien/yet-another-agent-harness/tree/main/.claude/skills/architecture-designer
Command: npx skills add https://github.com/dirien/yet-another-agent-harness --skill architecture-designer-dirien

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The architecture-designer skill helps engineering teams avoid ad-hoc, under-documented architecture decisions by providing a structured workflow to gather requirements, evaluate trade-offs, and produce clear Architecture Decision Records and diagrams that stakeholders can review.

Core Features & Use Cases

  • Requirements synthesis: Gather and summarize functional and non-functional requirements with an NFR checklist.
  • Architecture creation: Produce high-level diagrams (Mermaid preferred) and component interactions for microservices, serverless, or monolithic patterns.
  • Decision documentation: Generate ADRs that list context, alternatives, decisions, consequences, and trade-offs for stakeholder review.
  • Use Case: Use this skill to design a new order processing system, choose a database strategy, or review an existing microservices split with operational cost and failure-mode considerations.

Quick Start

Use the architecture-designer skill to produce a requirements summary, a Mermaid high-level diagram, and an ADR describing the key technology decisions for a new service.

Frequently Asked Questions about architecture-designer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I document architecture decisions and trade-offs for a new microservices system?

To document architecture decisions, generate Architecture Decision Records (ADRs) that outline context, alternatives, decisions, and consequences. This structured approach ensures stakeholders can review technology trade-offs and operational costs for microservices or distributed systems.

What is the best way to create high-level architecture diagrams for distributed web services?

Creating high-level architecture diagrams is best done using Mermaid syntax to visualize component interactions. This allows you to map out microservices, serverless, or monolithic patterns clearly for stakeholder review and scalability planning.

How do I gather functional and non-functional requirements before a system design review?

Gathering requirements involves synthesizing functional needs and producing a non-functional requirements (NFR) checklist. This ensures your architecture review captures operational costs, failure modes, and scalability constraints for distributed web services.

Can I use this approach for both greenfield system design and reviewing an existing microservices split?

Yes, this approach applies to both greenfield system design and reviewing existing microservices splits. It helps evaluate technology trade-offs, failure modes, and operational costs by producing ADRs and Mermaid diagrams for stakeholder review.

Why do I need an NFR checklist and risk mitigation plan for scalability planning?

An NFR checklist and risk mitigation plan are needed for scalability planning to identify non-functional constraints and anticipate failure modes. They ensure your architecture design accounts for operational costs and distributed system risks before implementation.