skills.rest
DauQuangThanh
DauQuangThanhCOMMUNITY
Explore all skills by this author →
GitHub

architecture-design

Design architecture deliverables including Mermaid diagrams, ADRs, and deployment roadmaps.

14|11|Updated Dec 1, 2025
Search Tags:#design#architecture#mermaid#roadmap#ADR#diagram
One-click install
npx skills add https://github.com/DauQuangThanh/hanoi-rainbow --skill architecture-design-dauquangthanh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: architecture-design
Source: https://github.com/DauQuangThanh/hanoi-rainbow/tree/main/skills/architecture-design
Command: npx skills add https://github.com/DauQuangThanh/hanoi-rainbow --skill architecture-design-dauquangthanh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Architects and engineers struggle to turn requirements into coherent system designs, roadmaps, and documentation. This Skill provides structured architecture thinking to produce comprehensive designs across styles (monolith, microservices, serverless), including diagrams, ADRs, spec documents, and implementation roadmaps.

Core Features & Use Cases

  • Requirements analysis & architecture planning: Capture drivers, constraints, and success criteria to shape the architecture.
  • System design delivery: Produce layered architecture, component diagrams, data models, API contracts, and deployment guidance.
  • Documentation output: Create ADRs, technical specs, and implementation roadmaps for project planning and governance.

Quick Start

Analyze a product idea or legacy system and generate a complete architecture design with diagrams, ADRs, and a deployment plan.

Frequently Asked Questions about architecture-design

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

FAQPage Schema
How do I design software architecture from requirements to deployment?▼

To design software architecture from requirements, you analyze drivers and constraints to produce layered diagrams, data models, API contracts, ADRs, and deployment roadmaps. This structured approach ensures coherent system designs across monolith, microservices, serverless, and event-driven patterns.

What is the best way to document architecture decisions for technical governance?▼

The best way to document architecture decisions is by creating Architecture Decision Records (ADRs) alongside technical specifications. ADRs capture the context, decision, and consequences, providing clear governance and implementation roadmaps for engineering teams.

How do I generate architecture diagrams for microservices and serverless systems?▼

You generate architecture diagrams for microservices and serverless systems using Mermaid syntax. This produces visual component and layered architecture diagrams that map out system interactions, data models, and deployment flows directly from your requirements.

When should I use event-driven architecture patterns over a modular monolith?▼

You should use event-driven architecture patterns over a modular monolith when your requirements demand high decoupling and asynchronous processing. Analyzing your specific constraints and success criteria determines whether monolith, microservices, or serverless styles fit your system design.

Related Skills

Explore More Software Engineering Skills→
EnigmaWUEnigmaWU
1

define-architectural-drivers

Translate raw product requirements into architectural drivers for system design.

Community
Advanced
lexicalninjalexicalninja
2

technical-spec-writer

Generate technical specifications covering architecture, data models, API contracts, and deployment strategies.

Community
Advanced
nimadorostkarnimadorostkar
25

diagrams

Generate Mermaid diagrams as code for version-controlled documentation.

Community
Intermediate
atanakaatanaka

activity-to-usecase-v1

Generate use case specifications, PlantUML diagrams, and JSON from UML activity diagrams.

Community
Advanced