architecture-diagrams
Generate mermaid architecture diagrams. Use when visualizing system flows, component relationships, sequences, or data models.
$ 安裝
git clone https://github.com/korallis/Amp-OS /tmp/Amp-OS && cp -r /tmp/Amp-OS/profiles/default/skills/architecture-diagrams ~/.claude/skills/Amp-OS// tip: Run this command in your terminal to install the skill
SKILL.md
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
Repository

korallis
Author
korallis/Amp-OS/profiles/default/skills/architecture-diagrams
2
Stars
0
Forks
Updated17h ago
Added6d ago