visual-communicator

Visual Communicator Skill

Purpose

To ensure that complex ideas are always accompanied by visual representations using Mermaid diagrams, adhering to the standard defined in GEMINI.md.

Trigger Conditions

• User asks for an explanation of code, architecture, or flow.
• You are writing a spec or implementation_plan.
• User explicitly asks for a diagram.

Decision Logic: Which Diagram?

Execution Rules

1. Always Visualize: Do not just explain with text; show it with a diagram first.
2. Syntax Safety:
   • Quote labels with special chars: id["Label (Info)"].
   • Avoid HTML in labels if possible.
3. Context Placement:
   • If writing an Artifact (markdown), embed the diagram directly.
   • If chatting, provide the diagram in the chat response.

Example Templates

Flowchart

graph TD
    A[Start] --> B{Condition?}
    B -- Yes --> C[Process]
    B -- No --> D[End]

Sequence

sequenceDiagram
    participant U as User
    participant S as Server
    U->>S: Request
    S-->>U: Response