architecture-design

Generate architecture documents, ADRs, and Mermaid/PlantUML diagrams from product requirements.

3|2|Updated May 21, 2017
One-click install
npx skills add https://github.com/ducminhgd/tutorial-notes --skill architecture-design-ducminhgd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architecture-design
Source: https://github.com/ducminhgd/tutorial-notes/tree/main/.claude/skills/arch-design
Command: npx skills add https://github.com/ducminhgd/tutorial-notes --skill architecture-design-ducminhgd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turning vague product ideas into concrete software architectures that teams can implement.

Core Features & Use Cases

  • System context and container diagrams (C4/PlantUML/ Mermaid) to illustrate boundaries and interactions.
  • Technology stack recommendations aligned with constraints and non-functional requirements.
  • Data modeling, integration design, and architectural decision records (ADRs) to codify choices.
  • Engineering guidelines, coding conventions, and deployment considerations to accelerate delivery.

Quick Start

Provide a product requirement brief and I will generate a complete architecture design with diagrams and ADRs.

Frequently Asked Questions about architecture-design

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

FAQPage Schema
How do I design a software architecture from product requirements?

Designing software architecture from product requirements involves generating tech stack selections, component breakdowns, data models, and C4 diagrams. This process outputs comprehensive architecture documents, ADRs, and Mermaid or PlantUML diagrams to guide implementation.

Can I generate C4 model diagrams for a distributed system?

Yes, you can generate C4 model diagrams for distributed systems. The system produces system context and container diagrams using PlantUML or Mermaid to illustrate system boundaries and component interactions.

What is the best way to document architectural decisions for a new tech stack?

The best way to document architectural decisions is by generating Architectural Decision Records (ADRs). ADRs codify technology stack choices, integration designs, and constraints aligned with non-functional requirements to accelerate team delivery.

Does this system design process cover deployment and security guidelines?

Yes, the system design process covers deployment and security guidelines. It provides structured guidance for deployment, security, observability, and engineering conventions alongside the core data modeling and component breakdown.

When do I need architectural decision records and system context diagrams?

You need architectural decision records and system context diagrams when translating vague product ideas into concrete software architectures. They codify tech stack choices and illustrate boundaries for web, mobile, data, or distributed platforms.