architecture-designer

Design system architectures and document ADRs for distributed systems.

2|Updated Apr 6, 2026

Search Tags:#architecture #scalability #adr #distributed-systems #design-patterns #system-design #decision-records

Ready to run

npx skills add https://github.com/augustscl/awesome-xiawang-skills --skill architecture-designer-augustscl

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture-designer
Source: https://github.com/augustscl/awesome-xiawang-skills/tree/main/architecture-designer-0.1.0
Command: npx skills add https://github.com/augustscl/awesome-xiawang-skills --skill architecture-designer-augustscl

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Architects and engineering teams often struggle to produce consistent, scalable designs and maintain traceability across evolving requirements.

Core Features & Use Cases

Architecture guidance for distributed systems and cloud deployments, including pattern recommendations (monolith, modular monolith, microservices, event-driven).
ADR creation & decision documentation to capture trade-offs and rationale for long-term maintainability.
Architecture reviews & pattern analysis to assess risks, scalability, resilience, and cost implications.

Quick Start

Provide a concise system design for a new service with scalability, reliability, and cost constraints.

Frequently Asked Questions about architecture-designer

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

FAQPage Schema

How do I design a distributed system architecture for scalability and reliability?▼

Designing distributed system architecture requires evaluating structural patterns like microservices or event-driven designs against non-functional requirements. This process enforces trade-off analysis to balance scalability, resilience, and cost implications.

What is an architecture decision record and when do I need one?▼

An architecture decision record (ADR) captures trade-offs and design rationale for long-term maintainability. You need ADRs when making significant structural choices in distributed systems to ensure traceability across evolving requirements and team alignment.

How do I conduct an architecture review for cloud-native deployments?▼

Conducting an architecture review for cloud-native deployments involves assessing structural risks, scalability, and cost implications through pattern analysis. This review evaluates your current design against recommended patterns like modular monoliths or event-driven architectures.

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

Choosing between microservices and a modular monolith requires analyzing trade-offs specific to your scalability and reliability constraints. Pattern analysis evaluates deployment complexity and team boundaries to align the structure with your non-functional requirements.

Can I generate a concise system design with cost constraints automatically?▼

You can generate a concise system design incorporating scalability, reliability, and cost constraints by providing your project parameters. The output includes structural pattern recommendations and enforced trade-off analysis aligned with your operational limits.

Why does architecture documentation matter for evolving requirements?▼

Architecture documentation matters because it captures trade-offs through decision records, maintaining traceability across evolving requirements. Without documented architecture decisions, engineering teams struggle to produce consistent and scalable designs over time.