本文へ移動
cccskills
無料GitHub で公開

mermaid-architecture

Use when generating, documenting, or updating architecture diagrams, flowcharts, sequence, ER, class, or state diagrams using Mermaid in docs/architecture/.

インストール方法を見る

含まれるファイル(25)

  • SKILL.md9.2 KB
  • assets/api-design-template.md9.9 KB
  • assets/architecture-design-template.md7.7 KB
  • assets/database-design-template.md13.9 KB
  • assets/feature-design-template.md11.3 KB
  • assets/system-design-template.md16.0 KB
  • examples/fastapi/README.md20.2 KB
  • examples/java-webapp/README.md38.1 KB
  • examples/node-webapp/README.md21.2 KB
  • examples/python-etl/README.md25.9 KB
  • examples/react/README.md18.3 KB
  • examples/spring-boot/README.md13.4 KB
  • references/guides/code-to-diagram/README.md25.9 KB
  • references/guides/diagrams/activity-diagrams.md13.6 KB
  • references/guides/diagrams/architecture-diagrams.md32.8 KB
  • references/guides/diagrams/deployment-diagrams.md17.6 KB
  • references/guides/diagrams/sequence-diagrams.md27.3 KB
  • references/guides/resilient-workflow.md15.8 KB
  • references/guides/troubleshooting.md16.3 KB
  • references/guides/unicode-symbols/guide.md13.5 KB
  • references/guides/wiki-ticket-and-github.md2.7 KB
  • references/mermaid-diagram-guide.md15.0 KB
  • scripts/extract_mermaid.py11.4 KB
  • scripts/mermaid_to_image.py10.8 KB
  • scripts/resilient_diagram.py23.8 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Mermaid Architecture Diagrams

Create structured, high-contrast, production-ready Mermaid architecture diagrams, workflows, and system design documentation. Native diagrams render directly in Markdown viewers (GitHub, GitLab, Obsidian, wikis) with optional image exports (PNG/SVG) generated via Mermaid CLI (mmdc / npx @mermaid-js/mermaid-cli).

📁 Storage Location (docs/architecture/)

All generated architecture diagrams, source .mmd files, exported images, and system design documents must be stored in docs/architecture/, consistent with the drawio-architecture convention:

docs/architecture/
├── system-architecture.md             # Architecture documentation with embedded Mermaid blocks
├── <name>_<type>_<title>.mmd          # Source Mermaid definitions
├── <name>_<type>_<title>.png          # Optional exported raster image
└── <name>_<type>_<title>.svg          # Optional exported vector image

Ensure the directory exists before saving:

mkdir -p docs/architecture

When to Use

  • The user asks for an architecture diagram, system structure, component overview, C4 model, microservices topology, or data flow.

  • Documenting API interactions, service call sequences, authentication flows, or request lifecycles.

  • Visualizing workflows, state machines, business logic, ETL pipelines, or decision trees.

  • Mapping code to diagrams (Spring Boot, FastAPI, React, Node/Express, Python ETL, Java).

  • Creating or updating full design documents (System Design, Architecture, API Design, Database Schema).

  • In the Orchestrator pipeline (Phase 5): invoked via /architecture (the umbrella skill that owns docs/architecture/) to update or generate native Markdown Mermaid diagrams.

  • User asks or mentions this skill in English (e.g., "use /mermaid-architecture", "run mermaid-architecture", "generate mermaid diagram").

  • O usuário pede ou menciona esta skill em português (ex.: "use /mermaid-architecture", "execute mermaid-architecture", "gerar diagrama mermaid").

When NOT to Use

  • Visual drag-and-drop editing with native .drawio format → use /drawio-architecture.
  • Freehand sketch or casual whiteboard drawing → use Excalidraw or tldraw.
  • PlantUML-specific legacy diagrams (Salt wireframes, timing diagrams).

Orchestrator Integration

In the Orchestrator lifecycle (Phase 5 — Verification & QA Gate), the orchestrator calls /architecture, which routes work to the specialized engines:

  1. /drawio-architecture updates the visual editable .drawio system diagram.
  2. /mermaid-architecture runs immediately after to generate or update the native Mermaid architecture diagrams and embedded Markdown files in docs/architecture/.
  3. /create-readme then references the generated diagrams in README.md.

Diagram Types & Selection Guide

Diagram TypeBest Used ForGuide to Load
Architecture / C4System context, containers, microservices, component boundariesreferences/guides/diagrams/architecture-diagrams.md
SequenceAPI interactions, auth flows, inter-service messaging, async eventsreferences/guides/diagrams/sequence-diagrams.md
Activity / FlowchartBusiness processes, approval pipelines, ETL stages, decision treesreferences/guides/diagrams/activity-diagrams.md
Deployment / CloudCloud infrastructure (AWS, Azure, GCP), Kubernetes, networkingreferences/guides/diagrams/deployment-diagrams.md
Class / ER / StateData models, database schemas, lifecycle transitionsreferences/guides/wiki-ticket-and-github.md

Resilient Workflow with Error Recovery

To prevent syntax errors from reaching documentation, follow the resilient validation cycle:

flowchart LR
    A[1. Identify Diagram Type] --> B[2. Save .mmd to docs/architecture]
    B --> C{3. Validate Syntax}
    C -->|Valid| D[4. Embed in Markdown / Export]
    C -->|Invalid| E[5. Search Troubleshooting]
    E --> F[6. Apply Fix & Retry]
    F --> C

    classDef step fill:#90EE90,stroke:#333,color:darkgreen
    classDef decision fill:#FFD700,stroke:#333,color:black
    class A,B,D,E,F step
    class C decision

Script Execution

Use the bundled resilient script to generate diagrams directly into docs/architecture/:

# Generate diagram with automatic syntax validation and image export
python3 skills/mermaid-architecture/scripts/resilient_diagram.py \
    --code "flowchart TD; A[Client] --> B[API Gateway]" \
    --output-dir docs/architecture \
    --markdown-file system_architecture \
    --diagram-num 1 \
    --title "overview" \
    --format png \
    --json

If mmdc is not installed globally, the script automatically uses npx -y @mermaid-js/mermaid-cli.


High-Contrast Styling (Mandatory)

All diagrams must ensure readable text on both light and dark backgrounds by always specifying color: in every classDef:

graph TB
    classDef primary fill:#90EE90,stroke:#333,stroke-width:2px,color:darkgreen
    classDef secondary fill:#87CEEB,stroke:#333,stroke-width:2px,color:darkblue
    classDef database fill:#E6E6FA,stroke:#333,stroke-width:2px,color:darkblue
    classDef error fill:#FFB6C1,stroke:#DC143C,stroke-width:2px,color:black

    %% Rule: Every classDef MUST include color: property

Semantic Unicode Symbols

Always incorporate Unicode symbols to increase visual scanning speed and clarity:

  • 👤 Users: 👤 User, 👨‍💼 Admin
  • 🌐 Network: 🌐 Load Balancer, 🌐 API Gateway, ☁️ Cloud
  • ⚙️ Compute: ⚙️ Service, ⚡ Worker, 🚀 Microservice
  • 💾 Storage: [(💾 Database)], [(⚡ Redis Cache)], 📦 Object Storage
  • 📨 Messaging: 📨 Event Bus, 📬 Message Queue, 📢 PubSub
  • 🔐 Security: 🔐 Auth Service, 🛡️ Firewall, 🔑 Secrets
  • 📊 Observability: 📊 Metrics, 📝 Logs, 🚨 Alerts

Code-to-Diagram Extraction

When generating architecture from existing source code:

  1. Analyze entry points: Read controllers, routes, API specs (@RestController, @app.get, Express routes, Controllers).
  2. Trace service dependencies: Follow injected services, repositories, message queues, and DB contexts.
  3. Map infrastructure: Read docker-compose.yml, Helm charts, Terraform, or cloud configs.
  4. Choose view:
    • High-level component topology → architecture-diagrams.md
    • Method/call flow → sequence-diagrams.md
    • Business state transitions → activity-diagrams.md
  5. Refer to framework templates in examples/ (spring-boot, fastapi, react, node-webapp, python-etl, java-webapp).

Design Document Templates (assets/)

When full architecture or system documentation is required, populate the corresponding template and save to docs/architecture/:

Document TypeTemplate PathTarget Output
Architecture Designassets/architecture-design-template.mddocs/architecture/architecture-design.md
System Designassets/system-design-template.mddocs/architecture/system-design.md
API Designassets/api-design-template.mddocs/architecture/api-design.md
Database Designassets/database-design-template.mddocs/architecture/database-design.md
Feature Designassets/feature-design-template.mddocs/architecture/feature-<name>-design.md

Python Utilities

The skill includes standalone utilities in scripts/:

# Extract diagrams from markdown, validate, or convert
python3 skills/mermaid-architecture/scripts/extract_mermaid.py docs/architecture/system.md --validate

# Convert .mmd to PNG or SVG
python3 skills/mermaid-architecture/scripts/mermaid_to_image.py docs/architecture/overview.mmd docs/architecture/overview.png

# Full resilient generation with error diagnostics
python3 skills/mermaid-architecture/scripts/resilient_diagram.py --code "..." --title "service_map"

References

  • references/guides/diagrams/architecture-diagrams.md — C4 model, microservices, component architecture
  • references/guides/diagrams/sequence-diagrams.md — API interactions, service calls
  • references/guides/diagrams/activity-diagrams.md — Workflows and processes
  • references/guides/diagrams/deployment-diagrams.md — Cloud, infrastructure, and deployment
  • references/guides/unicode-symbols/guide.md — Complete semantic symbol index
  • references/guides/troubleshooting.md — 28 common syntax error solutions
  • references/guides/resilient-workflow.md — Error recovery and validation protocol
  • architecture — Umbrella skill that owns docs/architecture/ and routes diagram work to this engine
  • drawio-architecture — Companion skill for editable draw.io visual diagrams

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Single owner of everything under docs/architecture/ — ADRs, architecture and design documents, and architecture diagrams. Routes each deliverable to the right engine: /mermaid-architecture for Markdown-native diagrams, /drawio-architecture for editable .drawio diagrams, and the optional archify skill for interactive standalone HTML diagrams (used only when already installed in the environment; never installed at runtime). Use whenever architecture documentation, ADRs, or architecture diagrams must be created or updated.

日本語の概要は準備中です。原文の説明を表示しています。

afonsoft/skills102026年10月9日 更新

Use when building a new MCP server in TypeScript, Python, or C# that exposes tools to LLMs.

日本語の概要は準備中です。原文の説明を表示しています。

afonsoft/skills102026年10月9日 更新

Use when reviewing code before it merges, whether written by an agent or a human.

日本語の概要は準備中です。原文の説明を表示しています。

afonsoft/skills102026年10月9日 更新

Use when the user asks to connect an AI agent to external apps via Composio, or when Composio CLI or MCP setup fails.

日本語の概要は準備中です。原文の説明を表示しています。

afonsoft/skills102026年10月9日 更新

Use when initializing or migrating an AI agent harness in a repository.

日本語の概要は準備中です。原文の説明を表示しています。

afonsoft/skills102026年10月9日 更新

Use when turning approved plans, specs, PRDs, or Epics into trackable GitHub Issues.

日本語の概要は準備中です。原文の説明を表示しています。

afonsoft/skills102026年10月9日 更新

afonsoft のスキルをすべて見る

このスキルの問題を報告する