mermaid-diagrams

Generate domain-structured Mermaid diagrams with enforced naming conventions.

Updated Jan 18, 2026

Search Tags:#architecture #documentation #mermaid #diagrams #domain-based #diagram-prefix

Ready to run

npx skills add https://github.com/333-333-333/agents --skill mermaid-diagrams-333-333-333

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: mermaid-diagrams
Source: https://github.com/333-333-333/agents/tree/main/skills/mermaid-diagrams
Command: npx skills add https://github.com/333-333-333/agents --skill mermaid-diagrams-333-333-333

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create standardized Mermaid diagrams to visually document software architecture using domain-based organization and consistent file naming.

Core Features & Use Cases

Domain-based diagram organization under docs/diagrams
Filename prefixes by diagram type (flow-, seq-, er-, class-, state-, c4-, etc.)
Enforced conventions: title comments, descriptive node IDs in camelCase, and domain-focused organization to improve readability and traceability.
Use Case: Document software architecture, system interactions, and data flows with consistent diagrams that are easy to render and share.

Quick Start

Create a new Mermaid diagram under docs/diagrams for your domain using the appropriate prefix (e.g., flow-, seq-, er-, class-, state-, c4-) and a descriptive name with a .mmd extension.

Frequently Asked Questions about mermaid-diagrams

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

FAQPage Schema

How do I structure Mermaid diagrams for software architecture documentation?▼

To structure Mermaid diagrams, place them under docs/diagrams using domain-based folders. Apply filename prefixes like flow-, seq-, or er- to categorize diagram types, ensuring consistent architectural documentation across domains.

What file naming prefixes should I use for Mermaid sequence and flow diagrams?▼

Use diagram-type prefixes such as flow- for flowcharts, seq- for sequence diagrams, er- for entity relationships, class- for class diagrams, state- for state diagrams, and c4- for C4 architecture diagrams.

Can I use this to document auth and payments domain interactions?▼

Yes, you can document auth and payments interactions. The Skill generates domain-structured Mermaid diagrams to visualize system interactions and data flows specifically across auth, payments, and architecture domains.

What's the best way to enforce consistent node IDs in Mermaid architecture diagrams?▼

Enforce consistent node IDs by using descriptive camelCase names. The Skill enforces project conventions by requiring camelCase node IDs and two-line title comments to maintain diagram readability and traceability.

Do I need external dependencies to generate domain-structured Mermaid diagrams?▼

No external dependencies are required. The Skill operates independently to enforce file naming conventions, domain-based folder organization under docs/diagrams, and two-line title comments for Mermaid diagrams.