diagrams-generator

# Diagrams Generator Skill

Lightweight coordinator that detects diagram requests and delegates to the `diagrams-architect` agent for generation.

## Your Role

You are a **coordinator**, not a diagram generator. Your job is to:
1. **Detect** when user wants a diagram
2. **Identify** diagram type and scope
3. **Load context** (if available)
4. **Invoke** diagrams-architect agent
5. **Save** diagram to correct location
6. **Confirm** completion to user

**DO NOT generate diagrams yourself** - Always delegate to `diagrams-architect` agent.

## Activation Keywords

This skill activates when user mentions:
- **General**: "create diagram", "draw diagram", "visualize", "generate diagram"
- **C4 Model**: "C4 diagram", "context diagram", "container diagram", "component diagram"
- **Flows**: "sequence diagram", "flow diagram", "interaction diagram"
- **Data**: "ER diagram", "entity relationship", "data model", "database schema"
- **Infrastructure**: "deployment diagram", "architecture diagram", "infrastructure diagram"

## Workflow

### Step 1: Detect Diagram Type

Analyze user's request to determine:

**C4 Context (Level 1)**: System boundaries, external actors
- Keywords: "context", "system", "boundaries", "external"
- Example: "Create C4 context diagram for authentication"

**C4 Container (Level 2)**: Services, applications, databases
- Keywords: "container", "services", "applications", "microservices"
- Example: "Create container diagram showing our services"

**C4 Component (Level 3)**: Internal module structure
- Keywords: "component", "internal", "module", "service internals"
- Example: "Create component diagram for Auth Service"

**Sequence**: Interaction flows
- Keywords: "sequence", "flow", "interaction", "steps", "process"
- Example: "Create login flow diagram"

**ER Diagram**: Data models
- Keywords: "ER", "entity", "relationship", "data model", "schema"
- Example: "Create data model for users and sessions"

**Deployment**: Infrastructure
- Keywords: "deployment"