architecture-diagrams
Generate mermaid architecture diagrams. Use when visualizing system flows, component relationships, sequences, or data models.
When & Why to Use This Skill
This Claude skill automates the creation of professional Mermaid architecture diagrams, enabling developers and architects to visualize complex system flows, component relationships, and data models directly from code or descriptions. It streamlines technical documentation by generating syntactically correct diagrams for flowcharts, sequence diagrams, and database schemas, ensuring visual clarity in software engineering projects.
Use Cases
- Visualizing System Architecture: Automatically generate high-level component diagrams to illustrate how different parts of a software system interact and depend on each other.
- Documenting API and User Flows: Create sequence diagrams to map out complex asynchronous API calls, authentication flows, or step-by-step user interaction paths.
- Database Schema Mapping: Generate Entity Relationship (ER) diagrams to visualize data models and table relationships for better database design and communication.
- Workflow and Decision Logic: Produce clear flowcharts to document business logic, decision trees, or CI/CD pipeline processes for technical and non-technical stakeholders.
| name | architecture-diagrams |
|---|---|
| description | Generate mermaid architecture diagrams. Use when visualizing system flows, component relationships, sequences, or data models. |
Architecture Diagrams
Generate clear mermaid diagrams with proper syntax and styling.
Workflow
Identify diagram type based on what you're visualizing:
flowchart- Process flows, decision trees, workflowssequenceDiagram- API calls, user interactions, async flowsgraph- Component relationships, dependencieserDiagram- Data models, database schemas
Gather context using code tools:
- Use
finderto locate relevant components - Use
Readto understand relationships - Link to source files in diagram notes
- Use
Generate diagram using Amp's
mermaidtool:- Keep labels concise (3-4 words max)
- Use consistent naming conventions
- Add notes for complex relationships
Cite sources - Link diagram elements to actual code locations
Quick Reference
See diagram-templates.md for syntax examples.
When to Use
- Visualizing system architecture or component relationships
- Documenting API flows or user interactions
- Creating database/data model diagrams
- Explaining complex workflows or decision trees
Key Principles
- One concept per diagram - Split complex systems into multiple diagrams
- Top-to-bottom or left-to-right - Consistent flow direction
- Color-code by concern - Use subgraphs or styling for grouping
- Always cite code - Diagrams should reference actual implementations