[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73G3EAQWKCM8DB8D0N0QSVG":3,"skill-same:01M73G3EAQWKCM8DB8D0N0QSVG":216},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M73G3EAQWKCM8DB8D0N0QSVG","fireworks-tech-graph",null,"Use when the user wants to create any technical diagram - architecture, data flow, flowchart, sequence, agent\u002Fmemory, or concept map - and export as SVG+PNG. Trigger on: \"画图\" \"帮我画\" \"生成图\" \"做个图\" \"架构图\" \"流程图\" \"可视化一下\" \"出图\" \"generate diagram\" \"draw diagram\" \"visualize\" or any system\u002Fflow description the user wants illustrated.","shengdabai\u002FTony-Claude-Code-Skills","shengdabai","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F116417419?v=4","01M70F6D2WY5PQV5A92BKYJQEW","Tony Sheng","01M70F6D3GAAAYZ5H4CC1G8VXM",3,"MIT","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ffireworks-tech-graph\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ffireworks-tech-graph\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: fireworks-tech-graph\ndescription: >-\n  Use when the user wants to create any technical diagram - architecture, data\n  flow, flowchart, sequence, agent\u002Fmemory, or concept map - and export as\n  SVG+PNG. Trigger on: \"画图\" \"帮我画\" \"生成图\" \"做个图\" \"架构图\" \"流程图\"\n  \"可视化一下\" \"出图\" \"generate diagram\" \"draw diagram\" \"visualize\" or any\n  system\u002Fflow description the user wants illustrated.\n---\n\n# Fireworks Tech Graph\n\nGenerate production-quality SVG technical diagrams exported as PNG via `rsvg-convert`.\n\n## Install Source\n\nInstall this skill from GitHub:\n\n```bash\nnpx skills add yizhiyanhua-ai\u002Ffireworks-tech-graph\n```\n\nPublic package page:\n\n```text\nhttps:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002F@yizhiyanhua-ai\u002Ffireworks-tech-graph\n```\n\nDo not pass `@yizhiyanhua-ai\u002Ffireworks-tech-graph` directly to `skills add`, because the CLI expects a GitHub or local repository source.\n\nUpdate command:\n\n```bash\nnpx skills add yizhiyanhua-ai\u002Ffireworks-tech-graph --force -g -y\n```\n\n## Helper Scripts (Recommended)\n\nFour helper scripts in `scripts\u002F` directory provide stable SVG generation and validation:\n\n### 1. `generate-diagram.sh` - Validate SVG + export PNG\n```bash\n.\u002Fscripts\u002Fgenerate-diagram.sh -t architecture -s 1 -o .\u002Foutput\u002Farch.svg\n```\n- Validates an existing SVG file\n- Exports PNG after validation\n- Example: `.\u002Fscripts\u002Fgenerate-diagram.sh -t architecture -s 1 -o .\u002Foutput\u002Farch.svg`\n\n### 2. `generate-from-template.py` - Create starter SVG from template\n```bash\npython3 .\u002Fscripts\u002Fgenerate-from-template.py architecture .\u002Foutput\u002Farch.svg '{\"title\":\"My Diagram\",\"nodes\":[],\"arrows\":[]}'\n```\n- Loads a built-in SVG template\n- Renders nodes, arrows, and legend entries from JSON input\n- Escapes text content to keep output XML-valid\n\n### 3. `validate-svg.sh` - Validate SVG syntax\n```bash\n.\u002Fscripts\u002Fvalidate-svg.sh \u003Csvg-file>\n```\n- Checks XML syntax\n- Verifies tag balance\n- Validates marker references\n- Checks attribute completeness\n- Validates path data\n\n### 4. `test-all-styles.sh` - Batch test all styles\n```bash\n.\u002Fscripts\u002Ftest-all-styles.sh\n```\n- Tests multiple diagram sizes\n- Validates all generated SVGs\n- Generates test report\n\n**When to use scripts:**\n- Use scripts when generating complex SVGs to avoid syntax errors\n- Scripts provide automatic validation and error reporting\n- Recommended for production diagrams\n\n**When to generate SVG directly:**\n- Simple diagrams with few elements\n- Quick prototypes\n- When you need full control over SVG structure\n\n## Workflow (Always Follow This Order)\n\n1. **Classify** the diagram type (see Diagram Types below)\n2. **Extract structure** — identify layers, nodes, edges, flows, and semantic groups from user description\n3. **Plan layout** — apply the layout rules for the diagram type\n4. **Load style reference** — always load `references\u002Fstyle-1-flat-icon.md` unless user specifies another; load the matching `references\u002Fstyle-N.md` for exact color tokens and SVG patterns\n5. **Map nodes to shapes** — use Shape Vocabulary below\n6. **Check icon needs** — load `references\u002Ficons.md` for known products\n7. **Write SVG** with adaptive strategy (see SVG Generation Strategy below)\n8. **Validate**: Run `rsvg-convert file.svg -o \u002Fdev\u002Fnull 2>&1` to check syntax\n9. **Export PNG**: `rsvg-convert -w 1920 file.svg -o file.png`\n10. **Report** the generated file paths\n\n## Diagram Types & Layout Rules\n\n### Architecture Diagram\nNodes = services\u002Fcomponents. Group into **horizontal layers** (top→bottom or left→right).\n- Typical layers: Client → Gateway\u002FLB → Services → Data\u002FStorage\n- Use `\u003Crect>` dashed containers to group related services in the same layer\n- Arrow direction follows data\u002Frequest flow\n- ViewBox: `0 0 960 600` standard, `0 0 960 800` for tall stacks\n\n### Data Flow Diagram\nEmphasizes **what data moves where**. Focus on data transformation.\n- Label every arrow with the data type (e.g., \"embeddings\", \"query\", \"context\")\n- Use wider arrows (`stroke-width: 2.5`) for primary data paths\n- Dashed arrows for control\u002Ftrigger flows\n- Color arrows by data category (not just Agent\u002FRAG — use semantics)\n\n### Flowchart \u002F Process Flow\nSequential decision\u002Fprocess steps.\n- Top-to-bottom preferred; left-to-right for wide flows\n- Diamond shapes for decisions, rounded rects for processes, parallelograms for I\u002FO\n- Keep node labels short (≤3 words); put detail in sub-labels\n- Align nodes on a grid: x positions snap to 120px intervals, y to 80px\n\n### Agent Architecture Diagram\nShows how an AI agent reasons, uses tools, and manages memory.\nKey conceptual layers to always consider:\n- **Input layer**: User, query, trigger\n- **Agent core**: LLM, reasoning loop, planner\n- **Memory layer**: Short-term (context window), Long-term (vector\u002Fgraph DB), Episodic\n- **Tool layer**: Tool calls, APIs, search, code execution\n- **Output layer**: Response, action, side-effects\nUse cyclic arrows (loop arcs) to show iterative reasoning. Separate memory types visually.\n\n### Memory Architecture Diagram (Mem0, MemGPT-style)\nSpecialized agent diagram focused on memory operations.\n- Show memory **write path** and **read path** separately (different arrow colors)\n- Memory tiers: Working Memory → Short-term → Long-term → External Store\n- Label memory operations: `store()`, `retrieve()`, `forget()`, `consolidate()`\n- Use stacked rects or layered cylinders for storage tiers\n\n### Sequence Diagram\nTime-ordered message exchanges between participants.\n- Participants as vertical **lifelines** (top labels + vertical dashed lines)\n- Messages as horizontal arrows between lifelines, top-to-bottom time order\n- Activation boxes (thin filled rects on lifeline) show active processing\n- Group with `\u003Crect>` loop\u002Falt frames with label in top-left corner\n- ViewBox height = 80 + (num_messages × 50)\n\n### Comparison \u002F Feature Matrix\nSide-by-side comparison of approaches, systems, or components.\n- Column headers = systems, row headers = attributes\n- Row height: 40px; column width: min 120px; header row height: 50px\n- Checked cell: tinted background (e.g. `#dcfce7`) + `✓` checkmark; unsupported: `#f9fafb` fill\n- Alternating row fills (`#f9fafb` \u002F `#ffffff`) for readability\n- Max readable columns: 5; beyond that, split into two diagrams\n\n### Timeline \u002F Gantt\nHorizontal time axis showing durations, phases, and milestones.\n- X-axis = time (weeks\u002Fmonths\u002Fquarters); Y-axis = items\u002Ftasks\u002Fphases\n- Bars: rounded rects, colored by category, labeled inside or beside\n- Milestone markers: diamond or filled circle at specific x position with label above\n- ViewBox: `0 0 960 400` typical; wider for many time periods: `0 0 1200 400`\n\n### Mind Map \u002F Concept Map\nRadial layout from central concept.\n- Central node at `cx=480, cy=280`\n- First-level branches: evenly distributed around center (360\u002FN degrees)\n- Second-level branches: branch off first-level at 30-45° offset\n- Use curved `\u003Cpath>` with cubic bezier for branches, not straight lines\n\n### Class Diagram (UML)\nStatic structure showing classes, attributes, methods, and relationships.\n- **Class box**: 3-compartment rect (name \u002F attributes \u002F methods), min width 160px\n  - Top compartment: class name, bold, centered (abstract = *italic*)\n  - Middle: attributes with visibility (`+` public, `-` private, `#` protected)\n  - Bottom: method signatures, same visibility notation\n- **Relationships**:\n  - Inheritance (extends): solid line + hollow triangle arrowhead, child → parent\n  - Implementation (interface): dashed line + hollow triangle, class → interface\n  - Association: solid line + open arrowhead, label with multiplicity (1, 0..*, 1..*)\n  - Aggregation: solid line + hollow diamond on container side\n  - Composition: solid line + filled diamond on container side\n  - Dependency: dashed line + open arrowhead\n- **Interface**: `\u003C\u003Cinterface>>` stereotype above name, or circle\u002Flollipop notation\n- **Enum**: compartment rect with `\u003C\u003Cenumeration>>` stereotype, values in bottom\n- Layout: parent classes top, children below; interfaces to the left\u002Fright of implementors\n- ViewBox: `0 0 960 600` standard; `0 0 960 800` for deep hierarchies\n\n### Use Case Diagram (UML)\nSystem functionality from user perspective.\n- **Actor**: stick figure (circle head + body line) placed outside system boundary\n  - Label below figure, 13-14px\n  - Primary actors on left, secondary\u002Fsupporting on right\n- **Use case**: ellipse with label centered inside, min 140×60px\n  - Keep names verb phrases: \"Create Order\", \"Process Payment\"\n- **System boundary**: large rect with dashed border + system name in top-left\n- **Relationships**:\n  - Include: dashed arrow `\u003C\u003Cinclude>>` from base to included use case\n  - Extend: dashed arrow `\u003C\u003Cextend>>` from extension to base use case\n  - Generalization: solid line + hollow triangle (specialized → general)\n- Layout: system boundary centered, actors outside, use cases inside\n- ViewBox: `0 0 960 600` standard\n\n### State Machine Diagram (UML)\nLifecycle states and transitions of an entity.\n- **State**: rounded rect with state name, min 120×50px\n  - Internal activities: small text `entry\u002F action`, `exit\u002F action`, `do\u002F activity`\n  - **Initial state**: filled black circle (r=8), one outgoing arrow\n  - **Final state**: filled circle (r=8) inside hollow circle (r=12)\n  - **Choice**: small hollow diamond, guard labels on outgoing arrows `[condition]`\n- **Transition**: arrow with optional label `event [guard] \u002F action`\n  - Guard conditions in square brackets\n  - Actions after `\u002F`\n- **Composite\u002Fnested state**: larger rect containing sub-states, with name tab\n- **Fork\u002Fjoin**: thick horizontal or vertical black bar (synchronization)\n- Layout: initial state top-left, final state bottom-right, flow top-to-bottom\n- ViewBox: `0 0 960 600` standard\n\n### ER Diagram (Entity-Relationship)\nDatabase schema and data relationships.\n- **Entity**: rect with entity name in header (bold), attributes below\n  - Primary key attribute: underlined\n  - Foreign key: italic or marked with (FK)\n  - Min width: 160px; attribute font-size: 12px\n- **Relationship**: diamond shape on connecting line\n  - Label inside diamond: \"has\", \"belongs to\", \"enrolls in\"\n  - Cardinality labels near entity: `1`, `N`, `0..1`, `0..*`, `1..*`\n- **Weak entity**: double-bordered rect with double diamond relationship\n- **Associative entity**: diamond + rect hybrid (rect with diamond inside)\n- Line style: solid for identifying relationships, dashed for non-identifying\n- Layout: entities in 2-3 rows, relationships between related entities\n- ViewBox: `0 0 960 600` standard; wider `0 0 1200 600` for many entities\n\n### Network Topology\nPhysical or logical network infrastructure.\n- **Devices**: icon-like rects or rounded rects\n  - Router: circle with cross arrows\n  - Switch: rect with arrow grid\n  - Server: stacked rect (rack icon)\n  - Firewall: brick-pattern rect or shield shape\n  - Load Balancer: horizontal split rect with arrows\n  - Cloud: cloud path (overlapping arcs)\n- **Connections**: lines between device centers\n  - Ethernet\u002Fwired: solid line, label bandwidth\n  - Wireless: dashed line with WiFi symbol\n  - VPN: dashed line with lock icon\n- **Subnets\u002FZones**: dashed rect containers with zone label (DMZ, Internal, External)\n- **Labels**: device hostname + IP below, 12-13px\n- Layout: tiered top-to-bottom (Internet → Edge → Core → Access → Endpoints)\n- ViewBox: `0 0 960 600` standard\n\n## UML Coverage Map\n\nFull mapping of UML 14 diagram types to supported diagram types:\n\n| UML Diagram | Supported As | Notes |\n|-------------|-------------|-------|\n| Class | Class Diagram | Full UML notation |\n| Component | Architecture Diagram | Use colored fills per component type |\n| Deployment | Architecture Diagram | Add node\u002Finstance labels |\n| Package | Architecture Diagram | Use dashed grouping containers |\n| Composite Structure | Architecture Diagram | Nested rects within components |\n| Object | Class Diagram | Instance boxes with underlined name |\n| Use Case | Use Case Diagram | Full actor\u002Fellipse\u002Frelationship |\n| Activity | Flowchart \u002F Process Flow | Add fork\u002Fjoin bars |\n| State Machine | State Machine Diagram | Full UML notation |\n| Sequence | Sequence Diagram | Add alt\u002Fopt\u002Floop frames |\n| Communication | — | Approximate with Sequence (swap axes) |\n| Timing | Timeline | Adapt time axis |\n| Interaction Overview | Flowchart | Combine activity + sequence fragments |\n| ER Diagram | ER Diagram | Chen\u002FCrow's foot notation |\n\n## Shape Vocabulary\n\nMap semantic concepts to consistent shapes across all diagram types:\n\n| Concept | Shape | Notes |\n|---------|-------|-------|\n| User \u002F Human | Circle + body path | Stick figure or avatar |\n| LLM \u002F Model | Rounded rect with brain\u002Fspark icon or gradient fill | Use accent color |\n| Agent \u002F Orchestrator | Hexagon or rounded rect with double border | Signals \"active controller\" |\n| Memory (short-term) | Rounded rect, dashed border | Ephemeral = dashed |\n| Memory (long-term) | Cylinder (database shape) | Persistent = solid cylinder |\n| Vector Store | Cylinder with grid lines inside | Add 3 horizontal lines |\n| Graph DB | Circle cluster (3 overlapping circles) | |\n| Tool \u002F Function | Gear-like rect or rect with wrench icon | |\n| API \u002F Gateway | Hexagon (single border) | |\n| Queue \u002F Stream | Horizontal tube (pipe shape) | |\n| File \u002F Document | Folded-corner rect | |\n| Browser \u002F UI | Rect with 3-dot titlebar | |\n| Decision | Diamond | Flowcharts only |\n| Process \u002F Step | Rounded rect | Standard box |\n| External Service | Rect with cloud icon or dashed border | |\n| Data \u002F Artifact | Parallelogram | I\u002FO in flowcharts |\n\n## Arrow Semantics\n\nAlways assign arrow meaning, not just color:\n\n| Flow Type | Color | Stroke | Dash | Meaning |\n|-----------|-------|--------|------|---------|\n| Primary data flow | blue `#2563eb` | 2px solid | none | Main request\u002Fresponse path |\n| Control \u002F trigger | orange `#ea580c` | 1.5px solid | none | One system triggering another |\n| Memory read | green `#059669` | 1.5px solid | none | Retrieval from store |\n| Memory write | green `#059669` | 1.5px | `5,3` | Write\u002Fstore operation |\n| Async \u002F event | gray `#6b7280` | 1.5px | `4,2` | Non-blocking, event-driven |\n| Embedding \u002F transform | purple `#7c3aed` | 1px solid | none | Data transformation |\n| Feedback \u002F loop | purple `#7c3aed` | 1.5px curved | none | Iterative reasoning loop |\n\nAlways include a **legend** when 2+ arrow types are used.\n\n## Layout Rules & Validation\n\n**Spacing**:\n- Same-layer nodes: 80px horizontal, 120px vertical between layers\n- Canvas margins: 40px minimum, 60px between node edges\n- Snap to 8px grid: horizontal 120px intervals, vertical 120px intervals\n\n**Arrow Labels** (CRITICAL):\n- MUST have background rect: `\u003Crect fill=\"canvas_bg\" opacity=\"0.95\"\u002F>` with 4px horizontal, 2px vertical padding\n- Place mid-arrow, ≤3 words, stagger by 15-20px when multiple arrows converge\n- Maintain 10px safety distance from nodes\n\n**Arrow Routing**:\n- Prefer orthogonal (L-shaped) paths to minimize crossings\n- Anchor arrows on component edges, not geometric centers\n- Route around dense node clusters, use different y-offsets for parallel arrows\n- Jump-over arcs (5px radius) for unavoidable crossings\n\n**Line Overlap Prevention** (CRITICAL - most common bug on Codex):\nWhen two arrows must cross each other, ALWAYS use jump-over arcs to prevent visual overlap:\n- Crossing horizontal arrows: add a small semicircle arc (radius 5px, stroke same color as arrow, fill none) that \"jumps over\" the other line\n- SVG pattern for jump-over: use a white\u002Fmatching-background arc on the lower layer, then draw the upper arc on top\n- Multiple crossings: stagger arc radii (5px, 7px, 9px) so arcs don't overlap each other\n- Never let two arrows' straight-line segments cross without a jump-over arc\n\n**Validation Checklist** (run before finalizing):\n1. **Arrow-Component Collision**: Arrows MUST NOT pass through component interiors (route around with orthogonal paths)\n2. **Text Overflow**: All text MUST fit with 8px padding (estimate: `text.length × 7px ≤ shape_width - 16px`)\n3. **Arrow-Text Alignment**: Arrow endpoints MUST connect to shape edges (not floating); all arrow labels MUST have background rects\n4. **Container Discipline**: Prefer arrows entering and leaving section containers through open gaps between components, not through inner component bodies\n\n## SVG Technical Rules\n\n- ViewBox: `0 0 960 600` default; `0 0 960 800` tall; `0 0 1200 600` wide\n- Fonts: embed via `\u003Cstyle>font-family: ...\u003C\u002Fstyle>` — no external `@import` (breaks rsvg-convert)\n- `\u003Cdefs>`: arrow markers, gradients, filters, clip paths\n- Text: minimum 12px, prefer 13-14px labels, 11px sub-labels, 16-18px titles\n- All arrows: `\u003Cmarker>` with `markerEnd`, sized `markerWidth=\"10\" markerHeight=\"7\"`\n- Drop shadows: `\u003CfeDropShadow>` in `\u003Cfilter>`, apply sparingly (key nodes only)\n- Curved paths: use `M x1,y1 C cx1,cy1 cx2,cy2 x2,y2` cubic bezier for loops\u002Ffeedback arrows\n- Clip content: use `\u003CclipPath>` if text might overflow a node box\n\n## SVG Generation & Error Prevention\n\n**MANDATORY: Python List Method** (ALWAYS use this):\n```python\npython3 \u003C\u003C 'EOF'\nlines = []\nlines.append('\u003Csvg xmlns=\"http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg\" viewBox=\"0 0 960 700\">')\nlines.append('  \u003Cdefs>')\n# ... each line separately\nlines.append('\u003C\u002Fsvg>')\n\nwith open('\u002Fpath\u002Fto\u002Foutput.svg', 'w') as f:\n    f.write('\\n'.join(lines))\nprint(\"SVG generated successfully\")\nEOF\n```\n\n**Why mandatory**: Prevents character truncation, typos, and syntax errors. Each line is independent and easy to verify.\n\n**Pre-Tool-Call Checklist** (CRITICAL - use EVERY time):\n1. ✅ Can I write out the COMPLETE command\u002Fcontent right now?\n2. ✅ Do I have ALL required parameters ready?\n3. ✅ Have I checked for syntax errors in my prepared content?\n\n**If ANY answer is NO**: STOP. Do NOT call the tool. Prepare the content first.\n\n**Error Recovery Protocol**:\n- **First error**: Analyze root cause, apply targeted fix\n- **Second error**: Switch method entirely (Python list → chunked generation)\n- **Third error**: STOP and report to user - do NOT loop endlessly\n- **Never**: Retry the same failing command or call tools with empty parameters\n\n**Validation** (run after generation):\n```bash\nrsvg-convert file.svg -o \u002Ftmp\u002Ftest.png 2>&1 && echo \"✓ Valid\" && rm \u002Ftmp\u002Ftest.png\n```\n\n**If using `generate-from-template.py`**:\n- Prefer `source` \u002F `target` node ids in arrow JSON so the generator can snap to node edges\n- Keep `x1,y1,x2,y2` as hints or fallback coordinates, not the main routing primitive\n- Let the generator choose orthogonal routes; avoid hardcoding center-to-center straight lines unless the path is guaranteed clear\n\n**Common Syntax Errors to Avoid**:\n- ❌ `yt-anchor` → ✅ `y=\"60\" text-anchor=\"middle\"`\n- ❌ `x=\"390` (missing y) → ✅ `x=\"390\" y=\"250\"`\n- ❌ `fill=#fff` → ✅ `fill=\"#ffffff\"`\n- ❌ `marker-end=` → ✅ `marker-end=\"url(#arrow)\"`\n- ❌ `L 29450` → ✅ `L 290,220`\n- ❌ Missing `\u003C\u002Fsvg>` at end\n\n## Output\n\n- **Default**: `.\u002F[derived-name].svg` and `.\u002F[derived-name].png` in current directory\n- **Custom**: user specifies path with `--output \u002Fpath\u002F` or `输出到 \u002Fpath\u002F`\n- **PNG export**: `rsvg-convert -w 1920 file.svg -o file.png` (1920px = 2x retina)\n\n## Styles\n\n| # | Name | Background | Best For |\n|---|------|-----------|----------|\n| 1 | **Flat Icon** (default) | White | Blogs, docs, presentations |\n| 2 | **Dark Terminal** | `#0f0f1a` | GitHub, dev articles |\n| 3 | **Blueprint** | `#0a1628` | Architecture docs |\n| 4 | **Notion Clean** | White, minimal | Notionnce |\n| 5 | **Glassmorphism** | Dark gradient | Product sites, keynotes |\n| 6 | **Claude Official** | Warm cream `#f8f6f3` | Anthropic-style diagrams |\n| 7 | **OpenAI Official** | Pure white `#ffffff` | OpenAI-style diagrams |\n\nLoad `references\u002Fstyle-N.md` for exact color tokens and SVG patterns.\n\n## Style Selection\n\n**Default**: Style 1 (Flat Icon) for most diagrams. Load `references\u002Fstyle-diagram-matrix.md` for detailed style-to-diagram-type recommendations.\n\nThese patterns appear frequently — internalize them:\n\n**RAG Pipeline**: Query → Embed → VectorSearch → Retrieve → Augment → LLM → Response\n**Agentic RAG**: adds Agent loop with Tool use between Query and LLM\n**Agentic Search**: Query → Planner → [Search Tool \u002F Calculator \u002F Code] → Synthesizer → Response\n**Mem0 \u002F Memory Layer**: Input → Memory Manager → [Write: VectorDB + GraphDB] \u002F [Read: Retrieve+Rank] → Context\n**Agent Memory Types**: Sensory (raw input) → Working (context window) → Episodic (past interactions) → Semantic (facts) → Procedural (skills)\n**Multi-Agent**: Orchestrator → [SubAgent A \u002F SubAgent B \u002F SubAgent C] → Aggregator → Output\n**Tool Call Flow**: LLM → Tool Selector → Tool Execution → Result Parser → LLM (loop)\n","# Fireworks Tech Graph\n\nGenerate production-quality SVG technical diagrams exported as PNG via `rsvg-convert`.\n\n## Install Source\n\nInstall this skill from GitHub:\n\n```bash\nnpx skills add yizhiyanhua-ai\u002Ffireworks-tech-graph\n```\n\nPublic package page:\n\n```text\nhttps:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002F@yizhiyanhua-ai\u002Ffireworks-tech-graph\n```\n\nDo not pass `@yizhiyanhua-ai\u002Ffireworks-tech-graph` directly to `skills add`, because the CLI expects a GitHub or local repository source.\n\nUpdate command:\n\n```bash\nnpx skills add yizhiyanhua-ai\u002Ffireworks-tech-graph --force -g -y\n```\n\n## Helper Scripts (Recommended)\n\nFour helper scripts in `scripts\u002F` directory provide stable SVG generation and validation:\n\n### 1. `generate-diagram.sh` - Validate SVG + export PNG\n```bash\n.\u002Fscripts\u002Fgenerate-diagram.sh -t architecture -s 1 -o .\u002Foutput\u002Farch.svg\n```\n- Validates an existing SVG file\n- Exports PNG after validation\n- Example: `.\u002Fscripts\u002Fgenerate-diagram.sh -t architecture -s 1 -o .\u002Foutput\u002Farch.svg`\n\n### 2. `generate-from-template.py` - Create starter SVG from template\n```bash\npython3 .\u002Fscripts\u002Fgenerate-from-template.py architecture .\u002Foutput\u002Farch.svg '{\"title\":\"My Diagram\",\"nodes\":[],\"arrows\":[]}'\n```\n- Loads a built-in SVG template\n- Renders nodes, arrows, and legend entries from JSON input\n- Escapes text content to keep output XML-valid\n\n### 3. `validate-svg.sh` - Validate SVG syntax\n```bash\n.\u002Fscripts\u002Fvalidate-svg.sh \u003Csvg-file>\n```\n- Checks XML syntax\n- Verifies tag balance\n- Validates marker references\n- Checks attribute completeness\n- Validates path data\n\n### 4. `test-all-styles.sh` - Batch test all styles\n```bash\n.\u002Fscripts\u002Ftest-all-styles.sh\n```\n- Tests multiple diagram sizes\n- Validates all generated SVGs\n- Generates test report\n\n**When to use scripts:**\n- Use scripts when generating complex SVGs to avoid syntax errors\n- Scripts provide automatic validation and error reporting\n- Recommended for production diagrams\n\n**When to generate SVG directly:**\n- Simple diagrams with few elements\n- Quick prototypes\n- When you need full control over SVG structure\n\n## Workflow (Always Follow This Order)\n\n1. **Classify** the diagram type (see Diagram Types below)\n2. **Extract structure** — identify layers, nodes, edges, flows, and semantic groups from user description\n3. **Plan layout** — apply the layout rules for the diagram type\n4. **Load style reference** — always load `references\u002Fstyle-1-flat-icon.md` unless user specifies another; load the matching `references\u002Fstyle-N.md` for exact color tokens and SVG patterns\n5. **Map nodes to shapes** — use Shape Vocabulary below\n6. **Check icon needs** — load `references\u002Ficons.md` for known products\n7. **Write SVG** with adaptive strategy (see SVG Generation Strategy below)\n8. **Validate**: Run `rsvg-convert file.svg -o \u002Fdev\u002Fnull 2>&1` to check syntax\n9. **Export PNG**: `rsvg-convert -w 1920 file.svg -o file.png`\n10. **Report** the generated file paths\n\n## Diagram Types & Layout Rules\n\n### Architecture Diagram\nNodes = services\u002Fcomponents. Group into **horizontal layers** (top→bottom or left→right).\n- Typical layers: Client → Gateway\u002FLB → Services → Data\u002FStorage\n- Use `\u003Crect>` dashed containers to group related services in the same layer\n- Arrow direction follows data\u002Frequest flow\n- ViewBox: `0 0 960 600` standard, `0 0 960 800` for tall stacks\n\n### Data Flow Diagram\nEmphasizes **what data moves where**. Focus on data transformation.\n- Label every arrow with the data type (e.g., \"embeddings\", \"query\", \"context\")\n- Use wider arrows (`stroke-width: 2.5`) for primary data paths\n- Dashed arrows for control\u002Ftrigger flows\n- Color arrows by data category (not just Agent\u002FRAG — use semantics)\n\n### Flowchart \u002F Process Flow\nSequential decision\u002Fprocess steps.\n- Top-to-bottom preferred; left-to-right for wide flows\n- Diamond shapes for decisions, rounded rects for processes, parallelograms for I\u002FO\n- Keep node labels short (≤3 words); put detail in sub-labels\n- Align nodes on a grid: x positions snap to 120px intervals, y to 80px\n\n### Agent Architecture Diagram\nShows how an AI agent reasons, uses tools, and manages memory.\nKey conceptual layers to always consider:\n- **Input layer**: User, query, trigger\n- **Agent core**: LLM, reasoning loop, planner\n- **Memory layer**: Short-term (context window), Long-term (vector\u002Fgraph DB), Episodic\n- **Tool layer**: Tool calls, APIs, search, code execution\n- **Output layer**: Response, action, side-effects\nUse cyclic arrows (loop arcs) to show iterative reasoning. Separate memory types visually.\n\n### Memory Architecture Diagram (Mem0, MemGPT-style)\nSpecialized agent diagram focused on memory operations.\n- Show memory **write path** and **read path** separately (different arrow colors)\n- Memory tiers: Working Memory → Short-term → Long-term → External Store\n- Label memory operations: `store()`, `retrieve()`, `forget()`, `consolidate()`\n- Use stacked rects or layered cylinders for storage tiers\n\n### Sequence Diagram\nTime-ordered message exchanges between participants.\n- Participants as vertical **lifelines** (top labels + vertical dashed lines)\n- Messages as horizontal arrows between lifelines, top-to-bottom time order\n- Activation boxes (thin filled rects on lifeline) show active processing\n- Group with `\u003Crect>` loop\u002Falt frames with label in top-left corner\n- ViewBox height = 80 + (num_messages × 50)\n\n### Comparison \u002F Feature Matrix\nSide-by-side comparison of approaches, systems, or components.\n- Column headers = systems, row headers = attributes\n- Row height: 40px; column width: min 120px; header row height: 50px\n- Checked cell: tinted background (e.g. `#dcfce7`) + `✓` checkmark; unsupported: `#f9fafb` fill\n- Alternating row fills (`#f9fafb` \u002F `#ffffff`) for readability\n- Max readable columns: 5; beyond that, split into two diagrams\n\n### Timeline \u002F Gantt\nHorizontal time axis showing durations, phases, and milestones.\n- X-axis = time (weeks\u002Fmonths\u002Fquarters); Y-axis = items\u002Ftasks\u002Fphases\n- Bars: rounded rects, colored by category, labeled inside or beside\n- Milestone markers: diamond or filled circle at specific x position with label above\n- ViewBox: `0 0 960 400` typical; wider for many time periods: `0 0 1200 400`\n\n### Mind Map \u002F Concept Map\nRadial layout from central concept.\n- Central node at `cx=480, cy=280`\n- First-level branches: evenly distributed around center (360\u002FN degrees)\n- Second-level branches: branch off first-level at 30-45° offset\n- Use curved `\u003Cpath>` with cubic bezier for branches, not straight lines\n\n### Class Diagram (UML)\nStatic structure showing classes, attributes, methods, and relationships.\n- **Class box**: 3-compartment rect (name \u002F attributes \u002F methods), min width 160px\n  - Top compartment: class name, bold, centered (abstract = *italic*)\n  - Middle: attributes with visibility (`+` public, `-` private, `#` protected)\n  - Bottom: method signatures, same visibility notation\n- **Relationships**:\n  - Inheritance (extends): solid line + hollow triangle arrowhead, child → parent\n  - Implementation (interface): dashed line + hollow triangle, class → interface\n  - Association: solid line + open arrowhead, label with multiplicity (1, 0..*, 1..*)\n  - Aggregation: solid line + hollow diamond on container side\n  - Composition: solid line + filled diamond on container side\n  - Dependency: dashed line + open arrowhead\n- **Interface**: `\u003C\u003Cinterface>>` stereotype above name, or circle\u002Flollipop notation\n- **Enum**: compartment rect with `\u003C\u003Cenumeration>>` stereotype, values in bottom\n- Layout: parent classes top, children below; interfaces to the left\u002Fright of implementors\n- ViewBox: `0 0 960 600` standard; `0 0 960 800` for deep hierarchies\n\n### Use Case Diagram (UML)\nSystem functionality from user perspective.\n- **Actor**: stick figure (circle head + body line) placed outside system boundary\n  - Label below figure, 13-14px\n  - Primary actors on left, secondary\u002Fsupporting on right\n- **Use case**: ellipse with label centered inside, min 140×60px\n  - Keep names verb phrases: \"Create Order\", \"Process Payment\"\n- **System boundary**: large rect with dashed border + system name in top-left\n- **Relationships**:\n  - Include: dashed arrow `\u003C\u003Cinclude>>` from base to included use case\n  - Extend: dashed arrow `\u003C\u003Cextend>>` from extension to base use case\n  - Generalization: solid line + hollow triangle (specialized → general)\n- Layout: system boundary centered, actors outside, use cases inside\n- ViewBox: `0 0 960 600` standard\n\n### State Machine Diagram (UML)\nLifecycle states and transitions of an entity.\n- **State**: rounded rect with state name, min 120×50px\n  - Internal activities: small text `entry\u002F action`, `exit\u002F action`, `do\u002F activity`\n  - **Initial state**: filled black circle (r=8), one outgoing arrow\n  - **Final state**: filled circle (r=8) inside hollow circle (r=12)\n  - **Choice**: small hollow diamond, guard labels on outgoing arrows `[condition]`\n- **Transition**: arrow with optional label `event [guard] \u002F action`\n  - Guard conditions in square brackets\n  - Actions after `\u002F`\n- **Composite\u002Fnested state**: larger rect containing sub-states, with name tab\n- **Fork\u002Fjoin**: thick horizontal or vertical black bar (synchronization)\n- Layout: initial state top-left, final state bottom-right, flow top-to-bottom\n- ViewBox: `0 0 960 600` standard\n\n### ER Diagram (Entity-Relationship)\nDatabase schema and data relationships.\n- **Entity**: rect with entity name in header (bold), attributes below\n  - Primary key attribute: underlined\n  - Foreign key: italic or marked with (FK)\n  - Min width: 160px; attribute font-size: 12px\n- **Relationship**: diamond shape on connecting line\n  - Label inside diamond: \"has\", \"belongs to\", \"enrolls in\"\n  - Cardinality labels near entity: `1`, `N`, `0..1`, `0..*`, `1..*`\n- **Weak entity**: double-bordered rect with double diamond relationship\n- **Associative entity**: diamond + rect hybrid (rect with diamond inside)\n- Line style: solid for identifying relationships, dashed for non-identifying\n- Layout: entities in 2-3 rows, relationships between related entities\n- ViewBox: `0 0 960 600` standard; wider `0 0 1200 600` for many entities\n\n### Network Topology\nPhysical or logical network infrastructure.\n- **Devices**: icon-like rects or rounded rects\n  - Router: circle with cross arrows\n  - Switch: rect with arrow grid\n  - Server: stacked rect (rack icon)\n  - Firewall: brick-pattern rect or shield shape\n  - Load Balancer: horizontal split rect with arrows\n  - Cloud: cloud path (overlapping arcs)\n- **Connections**: lines between device centers\n  - Ethernet\u002Fwired: solid line, label bandwidth\n  - Wireless: dashed line with WiFi symbol\n  - VPN: dashed line with lock icon\n- **Subnets\u002FZones**: dashed rect containers with zone label (DMZ, Internal, External)\n- **Labels**: device hostname + IP below, 12-13px\n- Layout: tiered top-to-bottom (Internet → Edge → Core → Access → Endpoints)\n- ViewBox: `0 0 960 600` standard\n\n## UML Coverage Map\n\nFull mapping of UML 14 diagram types to supported diagram types:\n\n| UML Diagram | Supported As | Notes |\n|-------------|-------------|-------|\n| Class | Class Diagram | Full UML notation |\n| Component | Architecture Diagram | Use colored fills per component type |\n| Deployment | Architecture Diagram | Add node\u002Finstance labels |\n| Package | Architecture Diagram | Use dashed grouping containers |\n| Composite Structure | Architecture Diagram | Nested rects within components |\n| Object | Class Diagram | Instance boxes with underlined name |\n| Use Case | Use Case Diagram | Full actor\u002Fellipse\u002Frelationship |\n| Activity | Flowchart \u002F Process Flow | Add fork\u002Fjoin bars |\n| State Machine | State Machine Diagram | Full UML notation |\n| Sequence | Sequence Diagram | Add alt\u002Fopt\u002Floop frames |\n| Communication | — | Approximate with Sequence (swap axes) |\n| Timing | Timeline | Adapt time axis |\n| Interaction Overview | Flowchart | Combine activity + sequence fragments |\n| ER Diagram | ER Diagram | Chen\u002FCrow's foot notation |\n\n## Shape Vocabulary\n\nMap semantic concepts to consistent shapes across all diagram types:\n\n| Concept | Shape | Notes |\n|---------|-------|-------|\n| User \u002F Human | Circle + body path | Stick figure or avatar |\n| LLM \u002F Model | Rounded rect with brain\u002Fspark icon or gradient fill | Use accent color |\n| Agent \u002F Orchestrator | Hexagon or rounded rect with double border | Signals \"active controller\" |\n| Memory (short-term) | Rounded rect, dashed border | Ephemeral = dashed |\n| Memory (long-term) | Cylinder (database shape) | Persistent = solid cylinder |\n| Vector Store | Cylinder with grid lines inside | Add 3 horizontal lines |\n| Graph DB | Circle cluster (3 overlapping circles) | |\n| Tool \u002F Function | Gear-like rect or rect with wrench icon | |\n| API \u002F Gateway | Hexagon (single border) | |\n| Queue \u002F Stream | Horizontal tube (pipe shape) | |\n| File \u002F Document | Folded-corner rect | |\n| Browser \u002F UI | Rect with 3-dot titlebar | |\n| Decision | Diamond | Flowcharts only |\n| Process \u002F Step | Rounded rect | Standard box |\n| External Service | Rect with cloud icon or dashed border | |\n| Data \u002F Artifact | Parallelogram | I\u002FO in flowcharts |\n\n## Arrow Semantics\n\nAlways assign arrow meaning, not just color:\n\n| Flow Type | Color | Stroke | Dash | Meaning |\n|-----------|-------|--------|------|---------|\n| Primary data flow | blue `#2563eb` | 2px solid | none | Main request\u002Fresponse path |\n| Control \u002F trigger | orange `#ea580c` | 1.5px solid | none | One system triggering another |\n| Memory read | green `#059669` | 1.5px solid | none | Retrieval from store |\n| Memory write | green `#059669` | 1.5px | `5,3` | Write\u002Fstore operation |\n| Async \u002F event | gray `#6b7280` | 1.5px | `4,2` | Non-blocking, event-driven |\n| Embedding \u002F transform | purple `#7c3aed` | 1px solid | none | Data transformation |\n| Feedback \u002F loop | purple `#7c3aed` | 1.5px curved | none | Iterative reasoning loop |\n\nAlways include a **legend** when 2+ arrow types are used.\n\n## Layout Rules & Validation\n\n**Spacing**:\n- Same-layer nodes: 80px horizontal, 120px vertical between layers\n- Canvas margins: 40px minimum, 60px between node edges\n- Snap to 8px grid: horizontal 120px intervals, vertical 120px intervals\n\n**Arrow Labels** (CRITICAL):\n- MUST have background rect: `\u003Crect fill=\"canvas_bg\" opacity=\"0.95\"\u002F>` with 4px horizontal, 2px vertical padding\n- Place mid-arrow, ≤3 words, stagger by 15-20px when multiple arrows converge\n- Maintain 10px safety distance from nodes\n\n**Arrow Routing**:\n- Prefer orthogonal (L-shaped) paths to minimize crossings\n- Anchor arrows on component edges, not geometric centers\n- Route around dense node clusters, use different y-offsets for parallel arrows\n- Jump-over arcs (5px radius) for unavoidable crossings\n\n**Line Overlap Prevention** (CRITICAL - most common bug on Codex):\nWhen two arrows must cross each other, ALWAYS use jump-over arcs to prevent visual overlap:\n- Crossing horizontal arrows: add a small semicircle arc (radius 5px, stroke same color as arrow, fill none) that \"jumps over\" the other line\n- SVG pattern for jump-over: use a white\u002Fmatching-background arc on the lower layer, then draw the upper arc on top\n- Multiple crossings: stagger arc radii (5px, 7px, 9px) so arcs don't overlap each other\n- Never let two arrows' straight-line segments cross without a jump-over arc\n\n**Validation Checklist** (run before finalizing):\n1. **Arrow-Component Collision**: Arrows MUST NOT pass through component interiors (route around with orthogonal paths)\n2. **Text Overflow**: All text MUST fit with 8px padding (estimate: `text.length × 7px ≤ shape_width - 16px`)\n3. **Arrow-Text Alignment**: Arrow endpoints MUST connect to shape edges (not floating); all arrow labels MUST have background rects\n4. **Container Discipline**: Prefer arrows entering and leaving section containers through open gaps between components, not through inner component bodies\n\n## SVG Technical Rules\n\n- ViewBox: `0 0 960 600` default; `0 0 960 800` tall; `0 0 1200 600` wide\n- Fonts: embed via `\u003Cstyle>font-family: ...\u003C\u002Fstyle>` — no external `@import` (breaks rsvg-convert)\n- `\u003Cdefs>`: arrow markers, gradients, filters, clip paths\n- Text: minimum 12px, prefer 13-14px labels, 11px sub-labels, 16-18px titles\n- All arrows: `\u003Cmarker>` with `markerEnd`, sized `markerWidth=\"10\" markerHeight=\"7\"`\n- Drop shadows: `\u003CfeDropShadow>` in `\u003Cfilter>`, apply sparingly (key nodes only)\n- Curved paths: use `M x1,y1 C cx1,cy1 cx2,cy2 x2,y2` cubic bezier for loops\u002Ffeedback arrows\n- Clip content: use `\u003CclipPath>` if text might overflow a node box\n\n## SVG Generation & Error Prevention\n\n**MANDATORY: Python List Method** (ALWAYS use this):\n```python\npython3 \u003C\u003C 'EOF'\nlines = []\nlines.append('\u003Csvg xmlns=\"http:\u002F\u002Fwww.w3.org\u002F2000\u002Fsvg\" viewBox=\"0 0 960 700\">')\nlines.append('  \u003Cdefs>')\n# ... each line separately\nlines.append('\u003C\u002Fsvg>')\n\nwith open('\u002Fpath\u002Fto\u002Foutput.svg', 'w') as f:\n    f.write('\\n'.join(lines))\nprint(\"SVG generated successfully\")\nEOF\n```\n\n**Why mandatory**: Prevents character truncation, typos, and syntax errors. Each line is independent and easy to verify.\n\n**Pre-Tool-Call Checklist** (CRITICAL - use EVERY time):\n1. ✅ Can I write out the COMPLETE command\u002Fcontent right now?\n2. ✅ Do I have ALL required parameters ready?\n3. ✅ Have I checked for syntax errors in my prepared content?\n\n**If ANY answer is NO**: STOP. Do NOT call the tool. Prepare the content first.\n\n**Error Recovery Protocol**:\n- **First error**: Analyze root cause, apply targeted fix\n- **Second error**: Switch method entirely (Python list → chunked generation)\n- **Third error**: STOP and report to user - do NOT loop endlessly\n- **Never**: Retry the same failing command or call tools with empty parameters\n\n**Validation** (run after generation):\n```bash\nrsvg-convert file.svg -o \u002Ftmp\u002Ftest.png 2>&1 && echo \"✓ Valid\" && rm \u002Ftmp\u002Ftest.png\n```\n\n**If using `generate-from-template.py`**:\n- Prefer `source` \u002F `target` node ids in arrow JSON so the generator can snap to node edges\n- Keep `x1,y1,x2,y2` as hints or fallback coordinates, not the main routing primitive\n- Let the generator choose orthogonal routes; avoid hardcoding center-to-center straight lines unless the path is guaranteed clear\n\n**Common Syntax Errors to Avoid**:\n- ❌ `yt-anchor` → ✅ `y=\"60\" text-anchor=\"middle\"`\n- ❌ `x=\"390` (missing y) → ✅ `x=\"390\" y=\"250\"`\n- ❌ `fill=#fff` → ✅ `fill=\"#ffffff\"`\n- ❌ `marker-end=` → ✅ `marker-end=\"url(#arrow)\"`\n- ❌ `L 29450` → ✅ `L 290,220`\n- ❌ Missing `\u003C\u002Fsvg>` at end\n\n## Output\n\n- **Default**: `.\u002F[derived-name].svg` and `.\u002F[derived-name].png` in current directory\n- **Custom**: user specifies path with `--output \u002Fpath\u002F` or `输出到 \u002Fpath\u002F`\n- **PNG export**: `rsvg-convert -w 1920 file.svg -o file.png` (1920px = 2x retina)\n\n## Styles\n\n| # | Name | Background | Best For |\n|---|------|-----------|----------|\n| 1 | **Flat Icon** (default) | White | Blogs, docs, presentations |\n| 2 | **Dark Terminal** | `#0f0f1a` | GitHub, dev articles |\n| 3 | **Blueprint** | `#0a1628` | Architecture docs |\n| 4 | **Notion Clean** | White, minimal | Notionnce |\n| 5 | **Glassmorphism** | Dark gradient | Product sites, keynotes |\n| 6 | **Claude Official** | Warm cream `#f8f6f3` | Anthropic-style diagrams |\n| 7 | **OpenAI Official** | Pure white `#ffffff` | OpenAI-style diagrams |\n\nLoad `references\u002Fstyle-N.md` for exact color tokens and SVG patterns.\n\n## Style Selection\n\n**Default**: Style 1 (Flat Icon) for most diagrams. Load `references\u002Fstyle-diagram-matrix.md` for detailed style-to-diagram-type recommendations.\n\nThese patterns appear frequently — internalize them:\n\n**RAG Pipeline**: Query → Embed → VectorSearch → Retrieve → Augment → LLM → Response\n**Agentic RAG**: adds Agent loop with Tool use between Query and LLM\n**Agentic Search**: Query → Planner → [Search Tool \u002F Calculator \u002F Code] → Synthesizer → Response\n**Mem0 \u002F Memory Layer**: Input → Memory Manager → [Write: VectorDB + GraphDB] \u002F [Read: Retrieve+Rank] → Context\n**Agent Memory Types**: Sensory (raw input) → Working (context window) → Episodic (past interactions) → Semantic (facts) → Procedural (skills)\n**Multi-Agent**: Orchestrator → [SubAgent A \u002F SubAgent B \u002F SubAgent C] → Aggregator → Output\n**Tool Call Flow**: LLM → Tool Selector → Tool Execution → Result Parser → LLM (loop)\n",{"name":5,"description":7},"main","7850740bd837adb32f0a109ab2af82482196c6f2","skills\u002Ffireworks-tech-graph",1,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills","https:\u002F\u002Fzturnsgo.com","https:\u002F\u002Fgithub.com\u002Fshengdabai","https:\u002F\u002Fzturnsgo.com\u002F","AI × education creator — producer, not consumer. Taught 6,000+ learners; shipping learning tools & daily essays with Claude Code, practicing @xiaolai's way 🥋","2026-11-01 21:28:23",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add shengdabai\u002FTony-Claude-Code-Skills --skill fireworks-tech-graph",{"tool":41,"command":42},"bunx","bunx skills add shengdabai\u002FTony-Claude-Code-Skills --skill fireworks-tech-graph",{"tool":44,"command":45},"pnpm","pnpm dlx skills add shengdabai\u002FTony-Claude-Code-Skills --skill fireworks-tech-graph","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ffireworks-tech-graph\u002FSKILL.md",true,[49,55,59,65,71,75,79,83,87,91,95,99,103,107,111,115,119,123,127,131,135,139,143,147,151,155,161,165,169,173,177,181,185,189,192,196,200,204,208,212],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},".gitignore","OTHER","其他",320,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ffireworks-tech-graph\u002F.gitignore",{"path":56,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":57,"sourceHtmlUrl":58},".npmignore",140,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ffireworks-tech-graph\u002F.npmignore",{"path":60,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":63,"sourceHtmlUrl":64},"agentloop-core.svg","ASSET","资产文件",5967,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ffireworks-tech-graph\u002Fagentloop-core.svg",{"path":66,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":69,"sourceHtmlUrl":70},"agents\u002Fopenai.yaml","REFERENCE","参考文档",235,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ffireworks-tech-graph\u002Fagents\u002Fopenai.yaml",{"path":72,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":73,"sourceHtmlUrl":74},"fixtures\u002Fagent-memory-types-style4.json",4570,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ffireworks-tech-graph\u002Ffixtures\u002Fagent-memory-types-style4.json",{"path":76,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":77,"sourceHtmlUrl":78},"fixtures\u002Fapi-flow-style7.json",3387,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ffireworks-tech-graph\u002Ffixtures\u002Fapi-flow-style7.json",{"path":80,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":81,"sourceHtmlUrl":82},"fixtures\u002Fmem0-style1.json",7996,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ffireworks-tech-graph\u002Ffixtures\u002Fmem0-style1.json",{"path":84,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":85,"sourceHtmlUrl":86},"fixtures\u002Fmicroservices-style3.json",5316,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ffireworks-tech-graph\u002Ffixtures\u002Fmicroservices-style3.json",{"path":88,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":89,"sourceHtmlUrl":90},"fixtures\u002Fmulti-agent-style5.json",4001,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ffireworks-tech-graph\u002Ffixtures\u002Fmulti-agent-style5.json",{"path":92,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":93,"sourceHtmlUrl":94},"fixtures\u002Fsystem-architecture-style6.json",4202,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ffireworks-tech-graph\u002Ffixtures\u002Fsystem-architecture-style6.json",{"path":96,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":97,"sourceHtmlUrl":98},"fixtures\u002Ftool-call-style2.json",4877,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ffireworks-tech-graph\u002Ffixtures\u002Ftool-call-style2.json",{"path":100,"resourceType":100,"resourceTypeDesc":101,"sizeBytes":102,"sourceHtmlUrl":16},"LICENSE","许可证",1090,{"path":104,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":105,"sourceHtmlUrl":106},"package.json",1020,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ffireworks-tech-graph\u002Fpackage.json",{"path":108,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":109,"sourceHtmlUrl":110},"README.md",21511,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ffireworks-tech-graph\u002FREADME.md",{"path":112,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":113,"sourceHtmlUrl":114},"README.zh.md",20296,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ffireworks-tech-graph\u002FREADME.zh.md",{"path":116,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":117,"sourceHtmlUrl":118},"references\u002Ficons.md",10296,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ffireworks-tech-graph\u002Freferences\u002Ficons.md",{"path":120,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":121,"sourceHtmlUrl":122},"references\u002Fstyle-1-flat-icon.md",3047,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ffireworks-tech-graph\u002Freferences\u002Fstyle-1-flat-icon.md",{"path":124,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":125,"sourceHtmlUrl":126},"references\u002Fstyle-2-dark-terminal.md",2788,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ffireworks-tech-graph\u002Freferences\u002Fstyle-2-dark-terminal.md",{"path":128,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":129,"sourceHtmlUrl":130},"references\u002Fstyle-3-blueprint.md",3169,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ffireworks-tech-graph\u002Freferences\u002Fstyle-3-blueprint.md",{"path":132,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":133,"sourceHtmlUrl":134},"references\u002Fstyle-4-notion-clean.md",2652,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ffireworks-tech-graph\u002Freferences\u002Fstyle-4-notion-clean.md",{"path":136,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":137,"sourceHtmlUrl":138},"references\u002Fstyle-5-glassmorphism.md",3574,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ffireworks-tech-graph\u002Freferences\u002Fstyle-5-glassmorphism.md",{"path":140,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":141,"sourceHtmlUrl":142},"references\u002Fstyle-6-claude-official.md",6750,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ffireworks-tech-graph\u002Freferences\u002Fstyle-6-claude-official.md",{"path":144,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":145,"sourceHtmlUrl":146},"references\u002Fstyle-7-openai.md",6640,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ffireworks-tech-graph\u002Freferences\u002Fstyle-7-openai.md",{"path":148,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":149,"sourceHtmlUrl":150},"references\u002Fstyle-diagram-matrix.md",6233,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ffireworks-tech-graph\u002Freferences\u002Fstyle-diagram-matrix.md",{"path":152,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":153,"sourceHtmlUrl":154},"references\u002Fsvg-layout-best-practices.md",3881,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ffireworks-tech-graph\u002Freferences\u002Fsvg-layout-best-practices.md",{"path":156,"resourceType":157,"resourceTypeDesc":158,"sizeBytes":159,"sourceHtmlUrl":160},"scripts\u002Fgenerate-diagram.sh","SCRIPT","脚本",4182,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ffireworks-tech-graph\u002Fscripts\u002Fgenerate-diagram.sh",{"path":162,"resourceType":157,"resourceTypeDesc":158,"sizeBytes":163,"sourceHtmlUrl":164},"scripts\u002Fgenerate-from-template.py",63140,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ffireworks-tech-graph\u002Fscripts\u002Fgenerate-from-template.py",{"path":166,"resourceType":157,"resourceTypeDesc":158,"sizeBytes":167,"sourceHtmlUrl":168},"scripts\u002FREADME.md",6141,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ffireworks-tech-graph\u002Fscripts\u002FREADME.md",{"path":170,"resourceType":157,"resourceTypeDesc":158,"sizeBytes":171,"sourceHtmlUrl":172},"scripts\u002Ftest-all-styles.sh",4072,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ffireworks-tech-graph\u002Fscripts\u002Ftest-all-styles.sh",{"path":174,"resourceType":157,"resourceTypeDesc":158,"sizeBytes":175,"sourceHtmlUrl":176},"scripts\u002Fvalidate-svg.sh",8455,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ffireworks-tech-graph\u002Fscripts\u002Fvalidate-svg.sh",{"path":178,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":179,"sourceHtmlUrl":180},"templates\u002Fagent-architecture.svg",1324,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ffireworks-tech-graph\u002Ftemplates\u002Fagent-architecture.svg",{"path":182,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":183,"sourceHtmlUrl":184},"templates\u002Farchitecture.svg",1055,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ffireworks-tech-graph\u002Ftemplates\u002Farchitecture.svg",{"path":186,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":187,"sourceHtmlUrl":188},"templates\u002Fcomparison-matrix.svg",612,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ffireworks-tech-graph\u002Ftemplates\u002Fcomparison-matrix.svg",{"path":190,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":179,"sourceHtmlUrl":191},"templates\u002Fdata-flow.svg","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ffireworks-tech-graph\u002Ftemplates\u002Fdata-flow.svg",{"path":193,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":194,"sourceHtmlUrl":195},"templates\u002Fer-diagram.svg",1003,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ffireworks-tech-graph\u002Ftemplates\u002Fer-diagram.svg",{"path":197,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":198,"sourceHtmlUrl":199},"templates\u002Fflowchart.svg",860,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ffireworks-tech-graph\u002Ftemplates\u002Fflowchart.svg",{"path":201,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":202,"sourceHtmlUrl":203},"templates\u002Fsequence.svg",856,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ffireworks-tech-graph\u002Ftemplates\u002Fsequence.svg",{"path":205,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":206,"sourceHtmlUrl":207},"templates\u002Fstate-machine.svg",846,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ffireworks-tech-graph\u002Ftemplates\u002Fstate-machine.svg",{"path":209,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":210,"sourceHtmlUrl":211},"templates\u002Ftimeline.svg",832,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ffireworks-tech-graph\u002Ftemplates\u002Ftimeline.svg",{"path":213,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":214,"sourceHtmlUrl":215},"templates\u002Fuse-case.svg",947,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ffireworks-tech-graph\u002Ftemplates\u002Fuse-case.svg",[217,225,233,241,249,256],{"skillNo":218,"name":219,"nameZh":6,"description":220,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":221,"sourceHtmlUrl":222,"categories":223,"keywords":224,"publishedAt":20},"01M73H7XKBHE1ETQDZT94MF9HH","seedance-prompt-en","Write effective prompts for Jimeng Seedance 2.0 multimodal AI video generation. Use when users want to create video prompts using text, images, videos, and audio inputs with the @ reference system. Covers camera movements, effects replication, video extension, editing, music beat-matching, e-commerce ads, short dramas, and educational content.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fseedance-prompt-en\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fseedance-prompt-en\u002FSKILL.md",[],[],{"skillNo":226,"name":227,"nameZh":6,"description":228,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":229,"sourceHtmlUrl":230,"categories":231,"keywords":232,"publishedAt":20},"01M73GRE9998Q1DZWC71N41JWG","onepage-pdf","Convert an HTML page into a single continuous-page PDF (one tall page, no pagination breaks), preserving desktop layout, backgrounds and selectable text. Use when the user asks to turn an HTML file\u002Freport\u002Fproposal into a \"single-page PDF\", \"long PDF\", \"不分页 PDF\", \"单页 PDF\", \"长图式 PDF\", or complains that an HTML-to-PDF export breaks into pages or cuts content. Supports optional string redaction with leak verification.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fonepage-pdf\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fonepage-pdf\u002FSKILL.md",[],[],{"skillNo":234,"name":235,"nameZh":6,"description":236,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":237,"sourceHtmlUrl":238,"categories":239,"keywords":240,"publishedAt":20},"01M73GQG1KZDADVPV3MHAT1J5A","native-feel-cross-platform-desktop","Use when the user is designing, prototyping, or rewriting a desktop app that must run on multiple OSes (macOS + Windows, optionally Linux) AND feel indistinguishable from a native app to its users — fast launch, native windowing, native input handling, native materials. Trigger words include \"cross-platform desktop\", \"Electron alternative\", \"Tauri vs native\", \"WebView wrapper\", \"near-native performance\", \"Raycast architecture\", \"WebKit\u002FWebView2 quirks\", \"WKWebView\", \"system tray app\", \"global hotkey app\", \"launcher app\". Do NOT trigger this skill for pure web apps, pure mobile apps, or for greenfield projects that have no native-feel requirement.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fnative-feel-cross-platform-desktop\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fnative-feel-cross-platform-desktop\u002FSKILL.md",[],[],{"skillNo":242,"name":243,"nameZh":6,"description":244,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":245,"sourceHtmlUrl":246,"categories":247,"keywords":248,"publishedAt":20},"01M73G87PDNSMKG2FHWCYER6N8","gstack","Router for the gstack skill suite. (gstack)","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fgstack\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fgstack\u002FSKILL.md",[],[],{"skillNo":250,"name":251,"nameZh":6,"description":252,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":253,"categories":254,"keywords":255,"publishedAt":20},"01M73G086AXAH9DW1H5G5N3CPB","dbs-video-extract","接收抖音、小红书、微信视频号等短视频链接或分享文案，查询作品／账号数据并提取语音文字稿，按作者和标题归档为 Markdown。用户希望完整解析短视频、取得数据或文字稿时使用；运行前检查 TikHub 与轻抖使用凭证，缺少时用新手能理解的方式引导购买和安全配置。","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fdbs-video-extract\u002FSKILL.md",[],[],{"skillNo":257,"name":258,"nameZh":6,"description":259,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":260,"categories":261,"keywords":262,"publishedAt":20},"01M73G01AQTCKTMDPJP9CQ6MXA","dbs-spread","用传播学与社会心理学中匹配当前内容的理论，解码共鸣机制、受众情绪、有效立场和传播动机。用户要求分析内容为什么能引起共鸣、打中什么情绪或受众还想听什么时使用。","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fdbs-spread\u002FSKILL.md",[],[]]