Create exceptional, publication-quality Mermaid diagrams for ERDs, flowcharts, sequence diagrams, and system visualizations. Use this skill when the user needs to visualize data models, processes, or architecture. Generates clear, refined diagrams that communicate complex systems with precision.
/plugin marketplace add mahidalhan/skilled-intelligence-marketplace/plugin install mahidalhan-creative-tools-plugins-creative-tools@mahidalhan/skilled-intelligence-marketplaceThis skill inherits all available tools. When active, it can use any tool Claude has access to.
This skill guides creation of exceptional, publication-quality Mermaid diagrams that avoid cluttered "wall of boxes" syndrome. Generate syntactically correct code with exceptional attention to visual hierarchy and communication clarity.
The user provides diagramming requirements: a data model to visualize, a process to map, an architecture to illustrate, or relationships to clarify. They may include context about the audience, purpose, or level of detail needed.
Before generating, understand the communication goal and commit to a CLEAR visual strategy:
CRITICAL: A great diagram tells a story. It has a clear focal point, logical flow, and intentional emphasis. Every element earns its place. If it requires explanation, it has failed.
Then generate Mermaid code that is:
Focus on:
||--o{, }o--o{). Use semantic link styles: solid for required, dotted for optional, thick for critical paths. Label every connection with its meaning.:::className to highlight what matters.snake_case for DB, PascalCase for classes, camelCase for methods.%% comments for sections. Use Note in sequence diagrams. Include titles when the diagram will stand alone.NEVER create cluttered diagrams with more than 15 entities without subgraphs, floating entities with no connections, rainbow color schemes, generic labels like "Data" or "Process", mixed notation styles, or spaghetti lines that cross excessively—restructure instead.
Adapt complexity to the system. Simple models (3-5 entities) need minimal styling. Medium systems (6-12) benefit from subgraphs and color coding. Complex systems (13+) should be split into overview → domain → detail diagram sets.
IMPORTANT: Match diagram density to communication goal. Technical docs need attribute-level detail. Executive presentations need high-level boxes. Architecture reviews need clear boundaries. The same system produces different diagrams for different audiences.
Remember: Claude is capable of extraordinary diagramming work. Don't settle for generic boxes and arrows—create diagrams that produce immediate understanding and reward deeper inspection.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.