Comprehensive guide for creating software diagrams using Mermaid syntax. Use when users need to create, visualize, or document software through diagrams including class diagrams (domain modeling, object-oriented design), sequence diagrams (application flows, API interactions, code execution), flowcharts (processes, algorithms, user journeys), entity relationship diagrams (database schemas), C4 architecture diagrams (system context, containers, components), state diagrams, git graphs, pie charts, gantt charts, or any other diagram type. Triggers include requests to "diagram", "visualize", "model", "map out", "show the flow", or when explaining system architecture, database design, code structure, or user/application flows.
93
92%
Does it follow best practices?
Impact
92%
1.33xAverage score across 3 eval scenarios
Passed
No known issues
ERD diagram conventions
Uppercase entity names
0%
100%
Singular entity names
0%
100%
PK markers present
100%
100%
FK markers present
100%
100%
UK markers used
0%
100%
Correct cardinality notation
100%
100%
Junction table for many-to-many
75%
75%
Timestamps included
100%
100%
Relationship labels
100%
100%
Comment in diagram
100%
100%
erDiagram declaration
100%
100%
All six entities present
100%
100%
Sequence diagram features
actor for human user
0%
100%
participant for system components
100%
100%
Dotted arrows for responses
100%
100%
autonumber present
100%
100%
alt/else for error paths
40%
100%
opt block used
0%
0%
par block used
0%
0%
Activation markers
0%
100%
Notes added
100%
100%
sequenceDiagram declaration
100%
100%
Token refresh flow
100%
100%
No %% with curly braces
100%
100%
Class diagram conventions and theming
Visibility modifiers
100%
100%
Inheritance relationship
100%
100%
Realization/Interface relationship
100%
100%
Composition vs aggregation
0%
50%
Multiplicity on relationships
100%
100%
Class stereotypes
100%
100%
YAML frontmatter config
0%
100%
base theme for custom colors
100%
100%
Two separate diagrams
100%
100%
Relationship labels
100%
100%
classDiagram declaration
100%
100%
Method syntax with return types
100%
100%
Comments in diagrams
0%
100%
3027f20
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.