diagram-generator

Create Mermaid diagrams for architecture visualization.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "diagram-generator" with this command: npx skills add camoa/claude-skills/camoa-claude-skills-diagram-generator

Diagram Generator

Create Mermaid diagrams for architecture visualization.

Activation

Activate when you detect:

  • "Create diagram for X"

  • "Visualize the architecture"

  • "Show me the data flow"

  • "Draw the entity relationships"

Workflow

  1. Determine Diagram Type

Ask if unclear:

What should this diagram show?

  1. Data flow (how data moves through system)

  2. Service relationships (dependencies between services)

  3. Entity relationships (database structure)

  4. Sequence (interaction over time)

  5. State (entity lifecycle)

  6. Gather Elements

Based on type, ask:

Data Flow:

  • What is the starting point?

  • What are the processing steps?

  • What is the final destination?

Service Relationships:

  • What is the main service?

  • What does it depend on?

  • Are there event subscribers?

Entity Relationships:

  • What entities are involved?

  • What are the relationships (one-to-many, etc.)?

  1. Generate Diagram

Create appropriate Mermaid code:

Data Flow:

flowchart LR A[Input] --> B[Process] B --> C[Output]

Service Dependencies:

graph TD A[MainService] --> B[Dependency1] A --> C[Dependency2]

Entity Relationships:

erDiagram ENTITY1 ||--o{ ENTITY2 : has ENTITY1 ||--|| ENTITY3 : references

Sequence:

sequenceDiagram Actor->>Component: Action Component-->>Actor: Response

State:

stateDiagram-v2 [] --> State1 State1 --> State2 State2 --> []

  1. Present Diagram

Show the Mermaid code to user and ask:

Here's the diagram:

{mermaid code block}

Adjustments needed? (describe changes or "looks good")

  1. Add to Architecture

Once approved, use Edit tool to add to appropriate architecture file:

{Diagram Title}

{One sentence describing what this shows}

```mermaid {diagram code} ```

Diagram Templates

Drupal Request Flow

flowchart LR A[Request] --> B[Routing] B --> C[Controller] C --> D[Service] D --> E[Entity] E --> F[Response]

Plugin System

graph TD A[PluginManager] --> B[Discovery] A --> C[Factory] B --> D[Annotations] B --> E[YAML] C --> F[Plugin Instance]

Form Submit Flow

sequenceDiagram User->>Form: Submit Form->>Form: validateForm() Form->>Form: submitForm() Form->>Service: Process data Service-->>Form: Result Form-->>User: Redirect/Message

Stop Points

STOP and wait for user:

  • After asking diagram type

  • After showing generated diagram

  • Before adding to architecture file

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

General

html-generator

No summary provided by upstream source.

Repository SourceNeeds Review
General

memory-manager

No summary provided by upstream source.

Repository SourceNeeds Review
General

requirements-gatherer

No summary provided by upstream source.

Repository SourceNeeds Review
General

core-pattern-finder

No summary provided by upstream source.

Repository SourceNeeds Review