architecture-designer

Guide architecture pattern selection and document decisions with ADRs.

4|1|Updated Mar 18, 2026

Search Tags:#design #architecture #documentation #adr #trade-offs #system-design

Ready to run

npx skills add https://github.com/xcrrr/claude-skills --skill architecture-designer-xcrrr

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture-designer
Source: https://github.com/xcrrr/claude-skills/tree/main/skills/coding/architecture-designer
Command: npx skills add https://github.com/xcrrr/claude-skills --skill architecture-designer-xcrrr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines architecture decision-making for software projects, helping teams choose appropriate patterns and document rationale with ADRs.

Core Features & Use Cases

Guide pattern selection (monolith, modular monolith, microservices, event-driven) based on context.
Document Architecture Decisions using ADR templates, including trade-off analysis and rationale.
Support for generating and maintaining ADRs to align teams and future work.

Quick Start

Draft an ADR to justify choosing a modular monolith 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 write an Architecture Decision Record for system design?▼

To write an Architecture Decision Record (ADR), follow a repeatable process to gather requirements, compare architectural options, and document trade-offs. This approach captures the rationale and consequences of your system design decisions.

What is the best way to choose between a microservices and modular monolith architecture?▼

Comparing microservices and a modular monolith requires analyzing trade-offs based on your specific context. You can evaluate architectural patterns by gathering requirements and documenting the rationale to select the most appropriate structure.

How do I document trade-offs for early technology stack decisions?▼

Documenting trade-offs for technology stack decisions involves comparing architectural options and recording the consequences. Creating ADRs provides a repeatable process to justify your selections and align your team on the rationale.

When do I need to create ADRs for software projects?▼

You need to create ADRs for software projects during early system design, when making technology stack decisions, or when selecting patterns like event-driven architectures. They capture consequences and align teams on future work.

Can I use this process to justify an event-driven architecture for a new service?▼

Yes, you can use this process to justify an event-driven architecture for a new service. It guides pattern selection by comparing architectural options and producing documented ADRs that capture the trade-off analysis and rationale.

What are the limitations of using ADRs for system design documentation?▼

ADRs document decisions and trade-offs but require consistent maintenance to remain useful. While they capture consequences and rationale, they do not replace the need to gather requirements and compare architectural options before finalizing your system design.