{"id":"c0455725-3d92-4a11-8070-465dbd8af812","shortId":"dt8F6N","kind":"skill","title":"baoyu-diagram","tagline":"Create professional, dark-themed SVG diagrams of any type — architecture diagrams, flowcharts, sequence diagrams, structural diagrams, mind maps, timelines, illustrative/conceptual diagrams, and more. Use this skill whenever the user asks for any kind of technical or conceptual d","description":"# Diagram Generator\n\nCreate professional SVG diagrams across multiple diagram types. All output is a single self-contained `.svg` file with embedded styles and fonts.\n\n## Supported Diagram Types\n\n| Type | When to Use | Key Characteristics |\n|------|-------------|-------------------|\n| **Architecture** | System components & relationships | Grouped boxes, connection arrows, region boundaries |\n| **Flowchart** | Decision logic, process steps | Diamond decisions, rounded step boxes, directional flow |\n| **Sequence** | Time-ordered interactions between actors | Vertical lifelines, horizontal messages, activation bars |\n| **Structural** | Class diagrams, ER diagrams, org charts | Compartmented boxes, typed relationships (inheritance, composition) |\n| **Mind Map** | Brainstorming, topic exploration | Central node, radiating branches, organic layout |\n| **Timeline** | Chronological events | Horizontal/vertical axis, event markers, period spans |\n| **Illustrative** | Conceptual explanations, comparisons | Free-form layout, icons, annotations, visual metaphors |\n| **State Machine** | State transitions, lifecycle | Rounded state nodes, labeled transitions, start/end markers |\n| **Data Flow** | Data transformation pipelines | Process bubbles, data stores, external entities |\n\n## Design System\n\n### Color Palette\n\nSemantic colors for component categories:\n\n| Category | Fill (rgba) | Stroke | Use For |\n|----------|-------------|--------|---------|\n| Primary | `rgba(8, 51, 68, 0.4)` | `#22d3ee` (cyan) | Frontend, user-facing, inputs |\n| Secondary | `rgba(6, 78, 59, 0.4)` | `#34d399` (emerald) | Backend, services, processing |\n| Tertiary | `rgba(76, 29, 149, 0.4)` | `#a78bfa` (violet) | Database, storage, persistence |\n| Accent | `rgba(120, 53, 15, 0.3)` | `#fbbf24` (amber) | Cloud, infrastructure, regions |\n| Alert | `rgba(136, 19, 55, 0.4)` | `#fb7185` (rose) | Security, errors, warnings |\n| Connector | `rgba(251, 146, 60, 0.3)` | `#fb923c` (orange) | Buses, queues, middleware |\n| Neutral | `rgba(30, 41, 59, 0.5)` | `#94a3b8` (slate) | External, generic, unknown |\n| Highlight | `rgba(59, 130, 246, 0.3)` | `#60a5fa` (blue) | Active state, focus, current step |\n\nFor flowcharts and sequence diagrams, assign colors by role (actor, decision, process) rather than by technology.\n\n### Typography\n\nUse embedded SVG `@font-face` or system monospace fallback:\n\n```svg\n\n```\n\nFont sizes by role:\n- **Title:** 16px, weight 700\n- **Component name:** 11-12px, weight 600\n- **Sublabel / description:** 9px, weight 400, color `#94a3b8`\n- **Annotation / note:** 8px, weight 400\n- **Tiny label (on arrows):** 7-8px\n\n### Core Visual Elements\n\n**Background:** `#0f172a` (slate-900) with subtle grid:\n```svg\n\n \n \n \n\n\n\n```\n\n**Arrowhead marker (standard):**\n```svg\n\n \n\n```\n\n**Arrowhead marker (colored) — create per-color as needed:**\n```svg\n\n \n\n```\n\n**Open arrowhead (for async/return messages):**\n```svg\n\n \n\n```\n\n### SVG Structure & Layering\n\nDraw elements in this order to get correct z-ordering (SVG paints back-to-front):\n\n1. Background fill + grid pattern\n2. Region/group boundaries (dashed outlines)\n3. Connection arrows and lines\n4. Opaque masking rects (same position as component boxes, `fill=\"#0f172a\"`)\n5. Component boxes (semi-transparent fill + stroke)\n6. Text labels\n7. Legend (bottom-right or bottom area, outside all boundaries)\n8. Title block (top-left)\n\nThe opaque masking rect trick is essential — semi-transparent component fills will show arrows underneath without it:\n```svg\n\n\n\n\nAPI Gateway\nKong / Nginx\n```\n\n### Spacing Rules\n\nThese prevent overlapping — follow them strictly:\n\n- **Component box height:** 50-70px (standard), 80-120px (large/complex)\n- **Minimum gap between components:** 40px vertical, 30px horizontal\n- **Arrow label clearance:** 10px from any box edge\n- **Region boundary padding:** 20px inside edges around contained components\n- **Legend placement:** At least 20px below the lowest diagram element\n- **Title block:** 20px from top-left, outside diagram content area\n- **viewBox:** Always extend to fit all content + 30px padding on all sides\n\n### Component Patterns\n\n**Standard box (service/process):**\n```svg\n\n\nName\ndescription\n```\n\n**Decision diamond (flowchart):**\n```svg\n\n \n \n Condition?\n\n```\n\n**Database cylinder:**\n```svg\n\n \n \n \n \n \n \n \n \n PostgreSQL\n\n```\n\n**Region boundary:**\n```svg\n\nAWS us-east-1\n```\n\n**Security group:**\n```svg\n\nVPC / Security Group\n```\n\n## Type-Specific Layout Guidance\n\nDetermine this SKILL.md file's directory path as `{baseDir}`. Read the reference file for the specific diagram type before starting layout. Reference files are located at `{baseDir}/references/` and contain detailed layout algorithms and examples.\n\n### Architecture Diagrams\n→ Read `{baseDir}/references/architecture.md`\n\nKey points: left-to-right or top-to-bottom data flow. Group related services in region boundaries. Use buses/connectors between layers. Place databases at the bottom or right.\n\n### Flowcharts\n→ Read `{baseDir}/references/flowchart.md`\n\nKey points: top-to-bottom primary flow. Diamonds for decisions with Yes/No labels on exit arrows. Rounded rectangles for start/end. Use the Highlight color for the happy path.\n\n### Sequence Diagrams\n→ Read `{baseDir}/references/sequence.md`\n\nKey points: actors as boxes at top, vertical dashed lifelines, horizontal arrows for messages (solid=sync, dashed=return). Time flows downward. Activation bars show processing. Number messages if complex.\n\n### Structural Diagrams\n→ Read `{baseDir}/references/structural.md`\n\nKey points: compartmented boxes (name / attributes / methods for class diagrams). Relationship lines: solid with filled diamond=composition, solid with empty diamond=aggregation, dashed arrow=dependency, solid triangle=inheritance.\n\n### Mind Maps\nFree-form radiating layout from a central concept. Use organic curves (`` with cubic beziers) for branches. Vary branch colors using the palette. Larger font for central node, decreasing as you go outward.\n\n### Timelines\nHorizontal or vertical axis line. Event markers as circles or diamonds on the axis. Description text offset to alternating sides to avoid overlap. Use color to categorize event types.\n\n### State Machines\nRounded-rect states with double-border for composite states. Filled circle for initial state, bullseye for final state. Curved arrows for self-transitions. Label all transitions with `event [guard] / action` format.\n\n## Output Rules\n\n1. Output a **single `.svg` file** — no external dependencies except the Google Fonts import\n2. Set `viewBox` to fit all content with 30px padding; do NOT set fixed `width`/`height` attributes (let the SVG scale responsively)\n3. Include `xmlns=\"http://www.w3.org/2000/svg\"` on the root `