architecture-designer

Design scalable system architectures and write Architecture Decision Records.

1|1|Updated Apr 16, 2026
One-click install
npx skills add https://github.com/iCesofT/awesome-ai --skill architecture-designer-icesoft
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-designer
Source: https://github.com/iCesofT/awesome-ai/tree/main/agents/skills/architecture-designer
Command: npx skills add https://github.com/iCesofT/awesome-ai --skill architecture-designer-icesoft

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Architects and teams need a structured approach to design scalable systems and capture architectural decisions via ADRs to ensure consistency, traceability, and communication across teams.

Core Features & Use Cases

  • Create high-level architecture designs and system diagrams.
  • Write Architecture Decision Records (ADRs) to document trade-offs and decisions.
  • Evaluate technology options, patterns, and scalability strategies for complex domains.
  • Plan for evolving requirements and multi-service integrations, with stakeholder reviews.

Quick Start

Provide your system requirements and constraints to generate an architecture diagram and ADRs.

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 microservices?

Create scalable system architectures by providing your requirements and constraints to generate architecture diagrams, trade-off analyses, and ADRs tailored for large, multi-service systems.

What is the best way to design scalable system architectures?

Create scalable system architectures by providing your requirements and constraints to generate architecture diagrams, trade-off analyses, and ADRs tailored for large, multi-service systems.

How do I perform a trade-off analysis for system design?

Perform a trade-off analysis by evaluating technology options, patterns, and scalability strategies against your complex domain requirements to capture architectural decisions and plan for evolving needs.

Can I generate architecture diagrams for multi-service systems?

Yes, you can generate high-level architecture diagrams for multi-service systems by inputting your system requirements and constraints to visualize complex integrations and scalability planning.

When do I need ADRs for architecture planning?

You need ADRs for architecture planning when ensuring consistency, traceability, and communication across teams during stakeholder reviews of evolving requirements and multi-service integrations.

Does this approach work for multi-service scalability planning?

Yes, this approach supports multi-service scalability planning by evaluating patterns and strategies for complex domains, accommodating evolving requirements and integrations with stakeholder reviews.