[{"_1":2,"_317":-5,"_318":-5},"loaderData",{"_3":4,"_8":9,"_23":24},"root",{"_5":-5,"_6":7},"user","countable",false,"routes/_main",{"_5":-5,"_10":11},"recentPosts",[12,17,20],{"_13":14,"_15":16},"slug","claude-code-gitlab-support","title","Claude Code's GitLab Support: What Changed",{"_13":18,"_15":19},"github-copilot-pricing-tiers","GitHub Copilot Pricing: Which Tier Do You Actually Need?",{"_13":21,"_15":22},"claude-code-self-hosted-runner-production","Deploying a Self-Hosted Claude Code Runner to Production","routes/creators.$handle",{"_25":26,"_27":26,"_28":29,"_30":7,"_31":32,"_315":7,"_316":100},"handle","yizhiyanhua-ai","displayName","profileUrl","https://github.com/yizhiyanhua-ai","verified","skills",[33],{"_34":35,"_13":36,"_37":38,"_39":40,"_41":42,"_43":44,"_45":46,"_47":48,"_49":50,"_51":52,"_53":54,"_60":61,"_62":63,"_64":65,"_80":81,"_82":-5,"_83":84,"_85":86,"_87":88,"_89":90,"_91":92,"_93":-5,"_94":95,"_96":26,"_30":7,"_97":7,"_98":86,"_99":100,"_101":86,"_102":86,"_103":104,"_105":106,"_135":136,"_172":173,"_223":224,"_289":290,"_301":302,"_311":312,"_313":314},"id","gh__yizhiyanhua-ai__fireworks-tech-graph__root","fireworks-tech-graph-yizhiyanhua-ai","name","Fireworks Tech Graph","canonicalName","fireworks-tech-graph","tagline","Create and export detailed technical diagrams easily.","description","Create technical diagrams such as software architecture, data flow, flowcharts, sequence diagrams, C4 reviews, cloud deployments, event streams, observability investigations, agent/memory systems, UML, ER, network topology, timelines, and technical concept maps, then export SVG, PNG, focused semantic SVG-to-GIF motion, or offline interactive HTML. Treat direct requests such as \"Generate a GIF\", \"生成 GIF\", or \"制作 GIF\" as motion requests, and use this skill when the user asks to visualize a system or engineering concept. Do not use for photos, raster artwork, or quantitative data charts.","longDescription","Fireworks Tech Graph is a versatile tool designed for generating a wide variety of technical diagrams, including software architecture, data flows, flowcharts, sequence diagrams, and more. This skill supports the creation of geometry-checked SVG files, high-resolution PNGs, and even animated GIFs, making it suitable for visualizing complex engineering concepts. Users can also export interactive HTML files for offline viewing, providing flexibility in how diagrams are presented and shared.\n\nThe skill operates through a set of helper scripts that streamline the diagram creation process. For instance, the `generate-diagram.sh` script validates SVG files and exports them as PNGs, ensuring that the output is both accurate and visually appealing. Users can create starter SVGs from templates using `generate-from-template.py`, which allows for quick setup based on predefined structures. Additionally, the `validate-svg.sh` script checks for syntax errors, ensuring that the diagrams are not only visually correct but also adhere to XML standards.\n\nFireworks Tech Graph is particularly beneficial for software developers, system architects, and technical writers who need to visualize systems or engineering concepts. By following a structured workflow that includes classification, structure extraction, layout planning, and validation, users can produce high-quality diagrams that effectively communicate complex ideas. The skill also supports various diagram styles and semantic contracts, allowing for tailored visual representations that meet specific project requirements.\n\nThis skill is not intended for creating raster artwork or quantitative data charts, making it best suited for users focused on technical diagramming rather than general graphic design. It provides a robust solution for anyone looking to enhance their documentation or presentations with clear and accurate visual aids.","primaryCategory","design","subcategory","graphic-design","secondaryCategories",[],"tags",[55,56,57,58,59],"technical-diagrams","svg-export","png-export","gif-animation","system-visualization","skillType","tool-wrapper","complexity","intermediate","platforms",[66,67,68,69,70,71,72,73,74,75,76,77,78,79],"claude-code","claude-api","codex-cli","cursor","antigravity","github-copilot","windsurf","opencode","cline","roo-code","goose","kiro","continue","trae","delivery","source-link","skillFileUrl","pricing","free","price",0,"thumbnailType","icon","thumbnailIcon","chart-bar","thumbnailColor","blue","thumbnailImageUrl","sellerId","gh__yizhiyanhua-ai","sellerName","featured","downloads","views",1,"rating","reviewCount","status","active","metrics",{"_107":86,"_108":109,"_110":100,"_111":112,"_113":114,"_115":116,"_117":118,"_119":120,"_121":122,"_123":124,"_125":126,"_127":128,"_129":130,"_131":132,"_133":134},"repoOpenIssues","freshnessScore",90,"mirrorCount","skillCountInRepo",2,"qualityScore",100,"daysSinceUpdate",24,"popularityScore",81,"trustScore",65,"repoStars",9813,"repoWatchers",34,"repoContributors",14,"overallScore",87,"repoCreatedAt","2026-04-10T15:07:10Z","repoForks",814,"repoPushedAt","2026-07-17T04:25:22Z","source",{"_137":26,"_138":139,"_140":141,"_146":40,"_147":-5,"_144":148,"_149":150,"_151":7,"_152":153,"_154":155,"_161":162,"_163":164,"_165":166,"_167":168,"_169":170,"_171":170},"owner","repoUrl","https://github.com/yizhiyanhua-ai/fireworks-tech-graph","author",{"_28":29,"_142":143,"_37":26,"_25":26,"_144":145},"avatarUrl","https://github.com/yizhiyanhua-ai.png","type","User","repo","commitSha","github","branch","main","isOfficial","path","","license",{"_37":156,"_157":158,"_159":160},"MIT License","spdxId","MIT","url","https://github.com/yizhiyanhua-ai/fireworks-tech-graph/blob/main/LICENSE","sourceUpdatedAt","2026-07-17T04:24:15.000Z","redistributable",true,"permalink","https://github.com/yizhiyanhua-ai/fireworks-tech-graph/blob/main/SKILL.md","repoFullName","yizhiyanhua-ai/fireworks-tech-graph","lastSyncedAt","2026-08-11T01:22:52.651Z","firstSeenAt","seo",{"_174":175,"_186":187,"_188":189,"_207":-5,"_208":209,"_215":216,"_217":218,"_219":220,"_221":222},"useCases",[176,180,183],{"_15":177,"_178":179},"Generating Software Architecture Diagrams","body","Use the skill to create clear software architecture diagrams that depict system components and their interactions.",{"_15":181,"_178":182},"Visualizing Data Flows","Quickly generate data flow diagrams to illustrate how data moves through a system, aiding in documentation and analysis.",{"_15":184,"_178":185},"Creating Animated GIFs of Diagrams","Export your diagrams as animated GIFs to showcase dynamic processes or transitions in your technical presentations.","whenNotToUse","Avoid using this skill for raster artwork or non-technical visualizations, as it is specifically designed for technical diagramming.","faqs",[190,195,198,201,204],{"_191":192,"_193":194},"q","What types of diagrams can I create with this skill?","a","You can create various technical diagrams including software architecture, data flow diagrams, flowcharts, sequence diagrams, and more.",{"_191":196,"_193":197},"Can I export my diagrams in different formats?","Yes, you can export diagrams as SVG, high-resolution PNG, and animated GIFs, as well as interactive HTML files.",{"_191":199,"_193":200},"Is there a specific workflow I should follow when using this skill?","Yes, follow a structured workflow that includes classifying the diagram type, extracting structure, planning layout, and validating the output.",{"_191":202,"_193":203},"What scripting support does this skill provide?","The skill includes several helper scripts for generating diagrams, validating SVG syntax, and exporting files, which help streamline the diagram creation process.",{"_191":205,"_193":206},"Who is this skill intended for?","This skill is ideal for software developers, system architects, and technical writers who need to visualize complex systems and engineering concepts.","ogImageUrl","keywords",[210,211,212,213,214],"create technical diagrams","export SVG","generate flowcharts","software architecture diagrams","visualize engineering concepts","whenToUse","Use this skill when you need to visualize systems, software architecture, or engineering concepts through diagrams.","metaTitle","Fireworks Tech Graph - Create Technical Diagrams","problemSolved","This skill simplifies the process of creating complex technical diagrams, ensuring accuracy and visual clarity.","metaDescription","Generate and export technical diagrams in SVG, PNG, and GIF formats with Fireworks Tech Graph.","content",{"_225":226,"_227":228,"_272":273,"_282":283,"_284":7,"_285":286,"_287":288},"bundledFiles",11,"fileTree",[229,236,239,242,245,248,251,254,258,262,266,269],{"_152":230,"_231":232,"_144":233,"_234":235},"CHANGELOG.md","size",5596,"file","language","markdown",{"_152":237,"_231":238,"_144":233,"_234":235},"CONTRIBUTING.md",882,{"_152":240,"_231":241,"_144":233},"LICENSE",1090,{"_152":243,"_231":244,"_144":233,"_234":235},"README.md",38529,{"_152":246,"_231":247,"_144":233,"_234":235},"README.zh.md",36221,{"_152":249,"_231":250,"_144":233,"_234":235},"SKILL.md",32478,{"_152":252,"_231":253,"_144":233},"agentloop-core.svg",5967,{"_152":255,"_231":256,"_144":233,"_234":257},"index.html",33509,"html",{"_152":259,"_231":260,"_144":233,"_234":261},"package.json",1473,"json",{"_152":263,"_231":264,"_144":233,"_234":265},"robots.txt",98,"text",{"_152":267,"_231":268,"_144":233},"site.webmanifest",368,{"_152":270,"_231":271,"_144":233},"sitemap.xml",244,"codeExamples",[274,278,280],{"_234":275,"_276":277},"bash","snippet","SKILL_ROOT=\"${CLAUDE_SKILL_DIR:-/absolute/path/from-codex-skill-metadata}\"\n\"$SKILL_ROOT/scripts/generate-diagram.sh\" -t architecture -s 1 -o ./output/arch.svg",{"_234":275,"_276":279},"SKILL_ROOT=\"${CLAUDE_SKILL_DIR:-/absolute/path/from-codex-skill-metadata}\"\nmkdir -p ./output\npython3 \"$SKILL_ROOT/scripts/generate-from-template.py\" architecture ./output/arch.svg '{\"title\":\"My Diagram\",\"nodes\":[],\"arrows\":[]}'",{"_234":275,"_276":281},"SKILL_ROOT=\"${CLAUDE_SKILL_DIR:-/absolute/path/from-codex-skill-metadata}\"\n\"$SKILL_ROOT/scripts/validate-svg.sh\" ","skillMd","# Fireworks Tech Graph\n\nGenerate geometry-checked SVG technical diagrams, high-resolution PNG, validated SVG-to-GIF semantic motion, and sanitized offline interactive HTML.\n\n## Runtime Compatibility\n\nUse this repository unchanged in both Codex and Claude Code. It follows the Agent Skills layout: `SKILL.md` is the shared entry point, bundled resources use relative paths, and `agents/openai.yaml` adds optional Codex UI metadata without affecting Claude Code.\n\nBefore reading a reference or running a script, resolve the directory containing this `SKILL.md` as `SKILL_ROOT`. Do not assume the current working directory is the skill directory, and do not assume a variable set in one shell call persists into the next.\n\n- In Claude Code, use `${CLAUDE_SKILL_DIR}`.\n- In Codex, use the absolute skill directory shown in the loaded skill metadata.\n\nEvery command block below sets `SKILL_ROOT` itself. In Codex, replace `/absolute/path/from-codex-skill-metadata` with the absolute skill directory before running the command.\n\n## Helper Scripts (Recommended)\n\nThe unified `scripts/fireworks.py` CLI and compatibility helpers provide stable rendering, geometry validation, inspection, animation, and export:\n\n### 1. `generate-diagram.sh` - Validate SVG + export PNG\n```bash\nSKILL_ROOT=\"${CLAUDE_SKILL_DIR:-/absolute/path/from-codex-skill-metadata}\"\n\"$SKILL_ROOT/scripts/generate-diagram.sh\" -t architecture -s 1 -o ./output/arch.svg\n```\n- Validates an existing SVG file\n- Exports PNG after validation\n- Example: `\"$SKILL_ROOT/scripts/generate-diagram.sh\" -t architecture -s 1 -o ./output/arch.svg`\n\n### 2. `generate-from-template.py` - Create starter SVG from template\n```bash\nSKILL_ROOT=\"${CLAUDE_SKILL_DIR:-/absolute/path/from-codex-skill-metadata}\"\nmkdir -p ./output\npython3 \"$SKILL_ROOT/scripts/generate-from-template.py\" architecture ./output/arch.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\nSKILL_ROOT=\"${CLAUDE_SKILL_DIR:-/absolute/path/from-codex-skill-metadata}\"\n\"$SKILL_ROOT/scripts/validate-svg.sh\" \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\nSKILL_ROOT=\"${CLAUDE_SKILL_DIR:-/absolute/path/from-codex-skill-metadata}\"\n\"$SKILL_ROOT/scripts/test-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## 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** — load `$SKILL_ROOT/references/composition-quality-contract.md`, then apply the diagram-type layout rules\n4. **Load style reference** — always load `$SKILL_ROOT/references/style-1-flat-icon.md` unless user specifies another; load the matching `$SKILL_ROOT/references/style-N-*.md` for exact color tokens and SVG patterns\n5. **Select semantic contract** — Styles 9–12 default to `c4-review`, `cloud-fabric`, `event-transit`, and `ops-pulse`; use `scripts/fireworks.py validate` before layout so missing or contradictory engineering facts fail closed\n6. **Map nodes to shapes** — use Shape Vocabulary below\n7. **Check icon needs** — load `$SKILL_ROOT/references/icons.md` for known products\n8. **Write SVG** with adaptive strategy (see SVG Generation Strategy below)\n9. **Validate**: Run `\"$SKILL_ROOT/scripts/validate-svg.sh\" file.svg` to check XML, markers, geometry, composition budgets, and renderability\n10. **Export PNG**: Use `cairosvg` (recommended). Load `$SKILL_ROOT/references/png-export.md` when choosing another renderer\n11. **Animate on request** — `让这张图动起来` / `生成 GIF` / `制作 GIF` / `Animate this diagram` / `Generate a GIF` means the latest generated semantic SVG to one GIF with `auto`, 5.75s, 20fps, and 960px width when that SVG satisfies one of the 12 approved motion contracts. Exact source bytes are not pinned, but role/stage/order coverage, route directions, required colors, and geometry fail closed; do not claim arbitrary same-style topologies are supported. Load `$SKILL_ROOT/references/motion-effects.md`, run `fireworks.py animate`, and report SVG/GIF/report paths. GIF is the only motion media format, while the default command also emits `.motion.json`. Styles 1–12 are enabled, and their contracts plus the shared `+2s-settled-flow` timing revision are user-approved; the default keeps frames 38–109 at full opacity and resets on frames 110–114. Every scene begins connector-free and advances its moving primitives toward each target. The 75-vs-115 compatibility gate counts binary-exact frames first, decoded-RGBA-exact frames second, and permits a guarded antialias equivalent only when AE ≤ 128, normalized RMSE ≤ 0.001, every difference component is at most 2px wide or high, and all differences remain on edge or node borders; DOM and signature geometry stay strict-exact. Reject raster animation inputs and non-GIF motion outputs. Explicit 3.75s/75-frame and 2.75s/55-frame timelines remain supported\n12. **Visual review gate** — if your runtime can read images, load the exported PNG back and inspect it. Syntactic validity does not guarantee visual correctness: arrows may cross through component interiors, labels may collide with lifelines or other labels, boxes may overlap, alt-frame text may sit on top of a message, or a legend may cover content. If you see any of these, revise the SVG and re-export, with at most two focused correction passes. Common fixes:\n - Route arrows through gaps between boxes, not through box interiors\n - Move arrow labels 6-8px away from the arrow line (offset-first); add background rects only when offset is insufficient\n - Widen inter-row/inter-column gutters so same-layer arrows have clear corridors\n - Collapse repeated cross-layer arrows into a single \"delegates down\" rail outside the content area\n - Move legend/notes out of any region where arrows or labels land\n - Increase viewBox height/width rather than packing elements tighter\n - If a filtered element (drop-shadow, blur) is missing one side of its border, move it ≥30px away from that viewBox edge, or remove the filter and rely on color/contrast for visual separation\n Report `visual_review: passed` after inspection. If image reading is unavailable, report `visual_review: skipped (image reader unavailable)` — do not guess or claim visual correctness.\n\n## Rule Precedence\n\nUse this order when instructions disagree:\n\n1. The user's explicit content and style request\n2. The selected `$SKILL_ROOT/references/style-N-*.md` visual tokens (palette, typography, corner radius, shadow treatment)\n3. Diagram-type layout rules and semantic flow requirements in this file\n4. Universal defaults and examples\n\nGeometry and validation gates always remain active: style guidance cannot justify unreadable text, missing marker definitions, or arrows crossing component interiors. Tables in this file define semantic defaults; a selected style may override their colors and stroke treatment while preserving the meaning and direction of each flow.\n\n## Diagram Types & Layout Rules\n\n### Architecture Diagram\nNodes = services/components. Group into **horizontal layers** (top→bottom or left→right).\n- Typical layers: Client → Gateway/LB → Services → Data/Storage\n- Use `` dashed containers to group related services in the same layer\n- Arrow direction follows data/request 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/trigger flows\n- Color arrows by data category (not just Agent/RAG — use semantics)\n\n### Flowchart / Process Flow\nSequential decision/process steps.\n- Top-to-bottom preferred; left-to-right for wide flows\n- Diamond shapes for decisions, rounded rects for processes, parallelograms for I/O\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/graph 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 `` loop/alt frames with label in top-left corner\n- ViewBox height = 80 + (num_messages × 50)\n\n### Comparison / 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` / `#ffffff`) for readability\n- Max readable columns: 5; beyond that, split into two diagrams\n\n### Timeline / Gantt\nHorizontal time axis showing durations, phases, and milestones.\n- X-axis = time (weeks/months/quarters); Y-axis = items/tasks/phases\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 / Concept Map\nRadial layout from central concept.\n- Central node at `cx=480, cy=280`\n- First-level branches: evenly distributed around center (360/N degrees)\n- Second-level branches: branch off first-level at 30-45° offset\n- Use curved `` 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 / attributes / 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**: `<>` stereotype above name, or circle/lollipop notation\n- **Enum**: compartment rect with `<>` stereotype, values in bottom\n- Layout: parent classes top, children below; interfaces to the left/right 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/supporting 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 `<>` from base to included use case\n - Extend: dashed arrow `<>` 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/ action`, `exit/ action`, `do/ 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] / action`\n - Guard conditions in square brackets\n - Actions after `/`\n- **Composite/nested state**: larger rect containing sub-states, with name tab\n- **Fork/join**: 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/wired: solid line, label bandwidth\n - Wireless: dashed line with WiFi symbol\n - VPN: dashed line with lock icon\n- **Subnets/Zones**: 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/instance 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/ellipse/relationship |\n| Activity | Flowchart / Process Flow | Add fork/join bars |\n| State Machine | State Machine Diagram | Full UML notation |\n| Sequence | Sequence Diagram | Add alt/opt/loop 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/Crow'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 / Human | Circle + body path | Stick figure or avatar |\n| LLM / Model | Rounded rect with brain/spark icon or gradient fill | Use accent color |\n| Agent / 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 / Function | Gear-like rect or rect with wrench icon | |\n| API / Gateway | Hexagon (single border) | |\n| Queue / Stream | Horizontal tube (pipe shape) | |\n| File / Document | Folded-corner rect | |\n| Browser / UI | Rect with 3-dot titlebar | |\n| Decision | Diamond | Flowcharts only |\n| Process / Step | Rounded rect | Standard box |\n| External Service | Rect with cloud icon or dashed border | |\n| Data / Artifact | Parallelogram | I/O in flowcharts |\n\n## Arrow Semantics\n\nAlways assign arrow meaning, not just color. The values below are defaults; the selected style reference overrides colors and stroke weights while preserving flow semantics:\n\n| Flow Type | Color | Stroke | Dash | Meaning |\n|-----------|-------|--------|------|---------|\n| Primary data flow | blue `#2563eb` | 2px solid | none | Main request/response path |\n| Control / 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/store operation |\n| Async / event | gray `#6b7280` | 1.5px | `4,2` | Non-blocking, event-driven |\n| Embedding / transform | purple `#7c3aed` | 1px solid | none | Data transformation |\n| Feedback / 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- **Offset-first** (default): place label 6-8px above horizontal arrows, or 8px left/right of vertical arrows — do not overlap the arrow line\n- **Background fallback**: add `` only when the offset label still crosses another visual element (another arrow, a node edge, etc.)\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- Compress equivalent bidirectional traffic only when both directions share the same semantics and styling: use one corridor with `marker-start` + `marker-end`, or two visibly offset paths in that corridor\n- Keep read/write, request/response, sync/async, or differently labeled directions as separate arrows; remove redundant bends and duplicate rails without erasing direction or meaning\n\n**Post-Generation Arrow Optimization**:\n\nWhen a user asks to \"优化箭头\" / \"fix arrow routing\" / \"optimize the diagram\" on an already-generated diagram, preserve all nodes, containers, styles, and layout — only modify the `arrows` entries in the JSON data, then re-render with `generate-from-template.py`.\n\nAvailable arrow override fields (in recommended order of use):\n\n| Field | Type | When to Use |\n|-------|------|-------------|\n| `source_port` / `target_port` | `\"left\"` / `\"right\"` / `\"top\"` / `\"bottom\"` | Arrow exits/enters from the wrong edge |\n| `corridor_x` | `[x, ...]` | Hint vertical segments toward this x lane (soft preference) |\n| `corridor_y` | `[y, ...]` | Hint horizontal segments toward this y lane (soft preference) |\n| `route_points` | `[[x1,y1], [x2,y2], ...]` | Exact ordered waypoints; each leg is routed orthogonally and unsafe points are rejected |\n| `routing_padding` | number (default: 24) | *(Advanced)* Adjust obstacle clearance for this arrow |\n| `port_clearance` | number | *(Advanced)* Adjust first-segment offset from node edge |\n| `label_style` | `\"badge\"` / `\"offset\"` | Choose `\"offset\"` when badge backgrounds create visual clutter; keep `\"badge\"` (default) for legacy/high-contrast labels |\n\nFor JSON/template rendering, the default remains `\"badge\"` for backward compatibility. Set `\"label_style\": \"offset\"` on individual arrows when you want offset-first labels without background rects.\n\nOptimization steps:\n1. Read the existing SVG — identify which arrows overlap, cross nodes, or look misaligned\n2. Find those arrows in the JSON data by `source` / `target` pair\n3. Add `source_port` / `target_port` if the exit/entry direction is wrong; add `corridor_x` / `corridor_y` to space parallel arrows apart; use `route_points` only when hints alone cannot resolve the path\n4. Re-run `generate-from-template.py` with the updated JSON and validate with `validate-svg.sh`\n\nExample — spacing two overlapping arrows into separate corridors:\n```json\n{ \"source\": \"nodeA\", \"target\": \"nodeB\", \"corridor_y\": [280] }\n{ \"source\": \"nodeC\", \"target\": \"nodeD\", \"corridor_y\": [320] }\n```\n\n**Line Overlap Prevention** (CRITICAL - common in AI-generated diagrams):\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/matching-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); arrow labels should not overlap arrow lines (use offset positioning or background rects)\n4. **Container Discipline**: Prefer arrows entering and leaving section containers through open gaps between components, not through inner component bodies\n5. **Filter Boundary Safety**: For every element with `filter=\"url(...)\"`, verify `(element_x + element_width + filter_extension) ≤ viewBox_width` AND `element_x ≥ filter_extension`. The default filter region extends 10-20% beyond bbox; staying near viewBox edges causes Chrome/cairosvg to clip the element's edge-side stroke (one side of the border vanishes while other sides render correctly)\n6. **Arrow-Title Collision**: Arrows MUST NOT cross through section/container title text or region labels (font-size ≥ 13px). For smaller annotations (< 13px), prefer routing around but tolerate if layout constraints require it. *(Visual self-review check — not covered by `validate-svg.sh` automated checks)*\n7. **Frame Label–Arrow Alignment** (sequence diagrams): Section/frame label badges MUST be vertically centered with their first message arrow. Compute `badge_y = first_arrow_y - (badge_height / 2)`. When appending new sections to an existing diagram, verify alignment matches the existing sections — this is the most common regression when adding content incrementally. Use variables in Python list generation to enforce the constraint: `sec_y = 840; badge_y = sec_y - 9 # for height=18 badge`\n8. **Marker Integrity**: Every `marker-start`, `marker-mid`, and `marker-end` URL MUST resolve to a `` definition\n9. **Visual Review Status**: Report whether the exported PNG was visually inspected; automated validation does not cover every text, legend, or arrow-arrow collision\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 `` — no external `@import` (cairosvg / rsvg-convert cannot fetch external URLs)\n- ``: arrow markers, gradients, filters, clip paths\n- Text: minimum 12px, prefer 13-14px labels, 11px sub-labels, 16-18px titles\n- All arrows: `` with `markerEnd`, sized `markerWidth=\"10\" markerHeight=\"7\"`\n- Drop shadows: `` in ``, apply sparingly (key nodes only)\n- Curved paths: use `M x1,y1 C cx1,cy1 cx2,cy2 x2,y2` cubic bezier for loops/feedback arrows\n- Clip content: use `` if text might overflow a node box\n- Z-order (drawing order): SVG uses painter's model — later elements cover earlier ones. Recommended layer order (bottom → top): ① canvas background ② dashed containers / region backgrounds ③ arrows and connection lines ④ node shapes (rects, circles) ⑤ text labels and annotations ⑥ legends and overlays. When arrows pass near text, draw arrows BEFORE text so text stays readable. Adjust per diagram needs — this is guidance, not rigid.\n\n## SVG Generation & Error Prevention\n\n**MANDATORY: Python List Method** (ALWAYS use this):\n```python\npython3 << 'EOF'\nlines = []\nlines.append('')\n\nwith open('/path/to/output.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/content 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\npython3 -c \"import xml.etree.ElementTree as ET; ET.parse('file.svg')\" && echo \"✓ Valid XML\"\n# Or use cairosvg as a render-time check:\npython3 -c \"import cairosvg; cairosvg.svg2png(url='file.svg', write_to='/tmp/test.png')\" && echo \"✓ Renders\" && rm /tmp/test.png\n```\n\n**If using `generate-from-template.py`**:\n- Prefer `source` / `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 `` at end\n- ❌ Element with `filter` near viewBox edge — filter region extends 20% (default) or more beyond bbox; if that region exceeds viewBox, Chrome/cairosvg clip the filter rendering AND can drop the element's own stroke on that side. Keep filtered elements at least `max(20% of element size, shadow blur radius × 3)` away from viewBox edges, or omit the filter.\n\n## Output\n\n- **Default**: `./[derived-name].svg` and `./[derived-name].png` in current directory\n- **Custom**: user specifies path with `--output /path/` or `输出到 /path/`\n- **PNG / motion export**: see **SVG → PNG Conversion** below and `$SKILL_ROOT/references/motion-effects.md`\n\n## SVG → PNG Conversion\n\nUse `$SKILL_ROOT/scripts/generate-diagram.sh` by default. Load `$SKILL_ROOT/references/png-export.md` only when selecting a renderer manually, handling CJK/emoji fallback, converting browser-generated SVG, or using the bundled Puppeteer converter.\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 | Notion, Confluence, wikis |\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| 8 | **Dark Luxury** *(AI-authored)* | `#0a0a0a` deep black | Architecture docs, premium editorial — hand-craft SVG from `$SKILL_ROOT/references/style-8-dark-luxury.md` |\n| 9 | **C4 Review Canvas** | Warm paper `#f7f2e8` | C4 reviews and ADRs; enforces one abstraction level |\n| 10 | **Cloud Fabric** | Cloud blue `#edf5fb` | Region/network/workload deployment ownership |\n| 11 | **Event Transit** | Transit paper `#fbf7ee` | Topics, processors, consumer groups, DLQ, state |\n| 12 | **Ops Pulse** | Ops navy `#07111f` | Golden signals, critical paths, correlated traces |\n\nLoad the matching `$SKILL_ROOT/references/style-N-*.md` for exact color tokens and SVG patterns.\n\n## Style Selection\n\n**Default**: Style 1 (Flat Icon) for most diagrams. Load `$SKILL_ROOT/references/style-diagram-matrix.md` for detailed style-to-diagram-type recommendations.\n\nPrompt fingerprints: `C4评审画布/C4 review board` → 9; `多区域云部署/deployment topology` → 10; `事件地铁图/event metro map` → 11; `可靠性脉冲/golden signals trace` → 12; `让这张图动起来/生成 GIF/制作 GIF/animate this diagram/Generate a GIF` → auto motion.\nAuto-select these only with matching domain evidence; otherwise use Styles 1–7 or `semantic_profile: \"generic\"`, and split mixed C4/deployment/event/ops views.\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 / Calculator / Code] → Synthesizer → Response\n**Mem0 / Memory Layer**: Input → Memory Manager → [Write: VectorDB + GraphDB] / [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 / SubAgent B / SubAgent C] → Aggregator → Output\n**Tool Call Flow**: LLM → Tool Selector → Tool Execution → Result Parser → LLM (loop)","skillMdTruncated","frontmatter",{"_37":40,"_43":44},"totalSizeBytes",156455,"runtime",{"_291":164,"_292":7,"_293":-5,"_294":164,"_295":7,"_296":164,"_297":298,"_299":300},"requiresBash","requiresMcp","model","requiresNode","requiresNetwork","requiresPython","allowedTools",[],"dependencies",[],"install",{"_303":304,"_305":168,"_306":139,"_307":308,"_309":310},"cli","npx skills add yizhiyanhua-ai/fireworks-tech-graph","coordinate","browseUrl","downloadUrl","https://github.com/yizhiyanhua-ai/fireworks-tech-graph/archive/refs/heads/main.zip","gitUrl","https://github.com/yizhiyanhua-ai/fireworks-tech-graph.git","createdAt","2026-08-11T01:22:57.811Z","updatedAt","2026-08-14T19:30:07.315Z","hasNext","page","actionData","errors"]