architecture-designer

Design architecture decisions and ADR documentation for complex systems.

588|41|Updated May 13, 2026

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

Ready to run

npx skills add https://github.com/zai-org/Synapse --skill architecture-designer-zai-org

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture-designer
Source: https://github.com/zai-org/Synapse/tree/main/.setup/skills/clawhub/skills/architecture-designer
Command: npx skills add https://github.com/zai-org/Synapse --skill architecture-designer-zai-org

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Architects and teams need structured guidance for system design decisions and ADR documentation to ensure consistency, traceability, and maintainability across complex software landscapes.

Core Features & Use Cases

ADR-driven architecture decisions and documentation
System design pattern evaluation and decision support
Architecture reviews and design guidance for scalability and maintainability
Use Case: evaluate between monolith and microservices and capture ADRs for key tradeoffs

Quick Start

Design a new system architecture for a distributed service and document the key ADRs to guide implementation.

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 for distributed systems?▼

Document architecture decisions for distributed systems using ADR-driven design to capture tradeoffs, ensure traceability, and maintain consistency across microservices and data stores. This approach records context, evaluated patterns, and outcomes.

What is the best way to evaluate monolith versus microservices architecture?▼

Evaluating monolith versus microservices architecture involves applying system design pattern evaluation to compare tradeoffs in scalability and maintainability. Key decisions are captured in ADRs to guide implementation and ensure traceable design choices.

How do I conduct an architecture review for scalability and maintainability?▼

Conduct an architecture review for scalability and maintainability by assessing existing system designs against design patterns and deployment strategies. The review identifies improvements and produces design artifacts with documented ADRs.

When do I need ADR documentation in system design?▼

You need ADR documentation in system design when making complex architecture decisions that impact distributed systems, data stores, or deployment strategies. ADRs ensure decisions are traceable, consistent, and maintainable across software landscapes.

Can I use this approach to design new architectures for microservices and data stores?▼

Yes, you can use this approach to design new architectures for microservices and data stores. It guides planning scalable, maintainable solutions, evaluates applicable design patterns, and generates key design artifacts with ADR-driven documentation.

What are the limitations of ADR-driven architecture design?▼

ADR-driven architecture design focuses on capturing decisions and evaluating patterns for complex systems, but it does not implement code or deploy infrastructure. It produces design guidance and documentation artifacts rather than executable software or runtime environments.