architecture-designer

Design high-level software architectures and document decisions with Architecture Decision Records.

Updated Jun 9, 2026
One-click install
npx skills add https://github.com/alsmadi99/dotfiles --skill architecture-designer-alsmadi99
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-designer
Source: https://github.com/alsmadi99/dotfiles/tree/main/claude/skills/architecture-designer
Command: npx skills add https://github.com/alsmadi99/dotfiles --skill architecture-designer-alsmadi99

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Architects and engineers often struggle to translate requirements into robust, scalable architectures. This skill provides structured guidance to capture decisions, evaluate trade-offs, and communicate designs clearly.

Core Features & Use Cases

  • Architecture diagrams for system relationships and data flows.
  • Architecture Decision Records (ADRs) to document decisions and rationale.
  • Trade-off analysis across patterns, technologies, and deployment options.
  • Component interaction design and scalability planning.
  • Infrastructure pattern selection and risk assessment for growth.

Quick Start

Provide the system requirements and constraints, and ask Architecture Designer to generate an ADR and a high-level architecture diagram.

Frequently Asked Questions about architecture-designer

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

FAQPage Schema
How do I write an Architecture Decision Record to document system design trade-offs?

Writing an Architecture Decision Record involves documenting your system design decisions and rationale to evaluate trade-offs. You provide system requirements and constraints to generate structured ADRs that align stakeholders on architectural choices.

What is the best way to evaluate architecture trade-offs across deployment options?

Evaluating architecture trade-offs requires comparing patterns, technologies, and deployment options to determine infrastructure suitability. You can produce structured trade-off analyses that map system relationships and data flows to guide decision-making.

Can I use this approach for architecture reviews of existing microservices?

Architecture reviews for existing microservices are supported by evaluating component interactions and data flows. You can assess current infrastructure patterns and scalability planning against new requirements to identify structural risks.

When do I need to create an ADR for software architecture decisions?

You need to create an ADR when making significant software architecture decisions involving trade-offs across patterns or technologies. Documenting these decisions captures the rationale and ensures stakeholder alignment during system design and reviews.

Does architecture design require specific infrastructure dependencies to generate diagrams?

Architecture design does not require specific infrastructure dependencies to generate diagrams. You provide system requirements and constraints, and the skill produces high-level architecture diagrams and ADRs without external module dependencies.