Agent skill · practicalswan
figma-generate-diagram
MANDATORY prerequisite — load this skill BEFORE every `generate_diagram` tool call. NEVER call `generate_diagram` directly without loading this skill first. Trigger whenever the user asks to create, generate, draw, render, sketch, or build a diagram — flowchart, architecture diagram, sequence diagram, ERD or entity-relationship diagram, state diagram or state machine, gantt chart, or timeline. Also trigger when the user mentions Mermaid syntax or wants a system architecture, decision tree, dependency graph, API call flow, auth handshake, schema, or pipeline visualized in FigJam. Routes to type-specific guidance, sets universal Mermaid constraints, and tells you when to use a different diagram type or skip the tool entirely (mindmaps, pie charts, class diagrams, etc.).
What it needs
About 7k tokens when loaded.
What this skill does
generate-diagram You MUST load this skill before every generatediagram tool call. Skipping it causes preventable rendering failures and low-quality output. generatediagram takes Mermaid.js syntax and produces an editable FigJam diagram. This skill routes you to the right per-type guidance and sets universal constraints. Step 1: Is generatediagram the right tool? Supported diagram types flowchart, sequenceDiagram, stateDiagram / stateDiagram-v2, gantt, erDiagram. Unsupported — don't call the tool If the user wants any of these, tell them directly that generatediagram doesn't support it instead of calling the tool and failing: Pie chart, mindmap, venn diagram, class diagram, journey, timeline, quadrant, C4, git graph, requirement diagram When to push the user to edit in Figma The tool cannot: Change fonts on an existing diagram Move individual shapes Edit a diagram node-by-node after generation If the user asks for any of those on an existing diagram, recommend they open the diagram in Figma and edit there. For content-level changes, it's usually faster to regenerate. Step 2: Pick the diagram type Lightweight routing — use the first match. User wants… Type Next step --- --- --- Services + datastores + queues + integrations Architecture flowchart Read references/architecture.md Decision tree, process flow, pipeline, dependency graph, user journey Flowchart Read references/flowchart.md Interactions between parties over time (API calls, auth, messaging) Sequence diagram Read references/sequence.md Data model, tables, keys, cardinality ER diagram Read references/erd.md Named states with transitions between them State diagram Read references/state.md Project schedule with dates, milestones Gantt chart Read references/gantt.md If a flowchart is requested and it describes software infrastructure (services, datastores, queues, external integrations), route to architecture.md — not flowchart.md. When in doubt, ask the user. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills practicalswan/figma-generate-diagram