[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-openai-node-link-and-diagram-layout":3,"mdc-8rg0mu-key":36,"related-repo-openai-node-link-and-diagram-layout":902,"related-org-openai-node-link-and-diagram-layout":1021},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":11,"stars":25,"repoUrl":26,"updatedAt":27,"license":28,"forks":29,"topics":30,"repo":31,"sourceUrl":34,"mdContent":35},"node-link-and-diagram-layout","apply automatic layouts to node-link diagrams","Choose and apply automatic layout strategies for node-link diagrams and connected-node visuals. Use when the user asks how to auto-arrange nodes, reduce line crossings, route edges, avoid overlaps, stabilize layout, or choose graph-layout algorithms for network diagrams, dependency graphs, database schema diagrams, ERDs, state machines, decision trees, flow diagrams, box-and-line editors, or other line-connected nodes.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},"openai","OpenAI","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Fopenai.png",[12,16,19,22],{"name":13,"slug":14,"type":15},"Visualization","visualization","tag",{"name":17,"slug":18,"type":15},"Diagrams","diagrams",{"name":20,"slug":21,"type":15},"UI Components","ui-components",{"name":23,"slug":24,"type":15},"Design","design",3992,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fplugins","2026-06-30T19:00:57.102",null,465,[],{"repoUrl":26,"stars":25,"forks":29,"topics":32,"description":33},[],"OpenAI Plugins","https:\u002F\u002Fgithub.com\u002Fopenai\u002Fplugins\u002Ftree\u002FHEAD\u002Fplugins\u002Fbuild-web-data-visualization\u002Fskills\u002Fnode-link-and-diagram-layout","---\nname: node-link-and-diagram-layout\ndescription: Choose and apply automatic layout strategies for node-link diagrams and connected-node visuals. Use when the user asks how to auto-arrange nodes, reduce line crossings, route edges, avoid overlaps, stabilize layout, or choose graph-layout algorithms for network diagrams, dependency graphs, database schema diagrams, ERDs, state machines, decision trees, flow diagrams, box-and-line editors, or other line-connected nodes.\n---\n\n# Node-Link and Diagram Layout\n\n## Overview\n\nUse this skill when the main problem is not which notation to use, but how to place connected nodes so the diagram stays readable. The job is to classify the graph family, choose a layout algorithm that matches the reading task, separate node placement from edge routing and overlap removal, and recommend a stack that can preserve those constraints in production.\n\nDefault assumption: the best automatic layout is the one that reinforces the intended reading path with the fewest crossings, bends, overlaps, and surprise placements. Do not treat force-directed layout as a generic answer for all diagrams. Trees, DAGs, port-constrained block diagrams, ERDs, and undirected exploration graphs usually need different algorithms.\n\nFor browser-facing node-link views, mobile layout is a graph-reading constraint, not only a CSS breakpoint. Use `..\u002F..\u002Freferences\u002Ffoundations\u002Fmobile-first-responsive-visualization.md` when choosing portrait focus views, optional landscape inspection, touch\u002Fpan\u002Fzoom ownership, and settings placement.\n\nFor operational graph workspaces, use `..\u002F..\u002Freferences\u002Ffoundations\u002Foperational-visualization-workspaces.md` so layout decisions account for outlines, inspectors, command bars, selected neighborhoods, URL state, mobile panels, and repeated navigation.\n\n## Core Workflow\n\n1. Classify the graph structure before choosing a renderer:\n   - rooted tree or forest\n   - directed acyclic graph\n   - cyclic directed graph with a dominant flow\n   - general undirected graph\n   - radial or hub-and-spoke structure\n   - clustered or compound graph\n   - port-constrained block diagram\n   - table-like schema or ERD\n   - nearly planar topology where crossing count dominates readability\n2. Identify the primary reading task:\n   - parent-child depth\n   - top-to-bottom or left-to-right flow\n   - reachability and dependency tracing\n   - cluster discovery\n   - cycle inspection\n   - shortest path or neighborhood exploration\n   - table relationship tracing\n   - stable editing with minimal layout drift\n3. Record geometry constraints up front:\n   - real node widths and heights, not point nodes\n   - labels that must fit without scaling below readability\n   - ports, handles, side constraints, or fixed connection order\n   - nested groups, lanes, clusters, or compounds\n   - whether some nodes are pinned or semi-pinned\n4. Choose the layout family that matches the structure:\n   - tidy tree layout for rooted ordered trees and decision trees\n   - layered or Sugiyama-style layout for directional processes, state machines, dependency maps, class hierarchies, ERDs, and most UML-like flow diagrams\n   - stress majorization or force-directed layout for undirected relational exploration where cluster shape matters more than global direction\n   - radial or concentric layout when distance from a root is the main story\n   - circular layout when cycle structure is the evidence\n   - planarization-driven layout when the graph is non-planar but low crossing count is the main objective\n5. Choose edge routing separately from node placement:\n   - straight or polyline when the graph is sparse and directional flow is already clear\n   - orthogonal when tables, ports, block diagrams, lanes, or circuit-like reading dominate\n   - spline routing when static aesthetics matter more than precise traceability and there is enough whitespace\n6. Treat overlap removal, label placement, and packing as explicit phases:\n   - remove node overlap after layout if the engine starts from point nodes\n   - reserve gutters for connector-dense tables and schemas\n   - keep edge labels out of node bodies and above selected paths\n   - pack connected components only after the component layouts are individually legible\n7. Prefer stability when users will edit, compare revisions, or recognize repeated diagrams:\n   - preserve node order when the source model has meaningful order\n   - preserve port order when connectors are semantically ordered\n   - use interactive or constraint-aware layered modes instead of re-randomizing\n8. Validate the result with readability criteria instead of trusting the engine:\n   - crossings are low enough for the task\n   - bends are limited and meaningful\n   - nodes and labels do not overlap\n   - directionality is obvious\n   - edge tracing is possible without visual hunting\n   - the layout stays readable on narrow widths or falls back to scrolling, filtering, or faceting\n   - mobile portrait starts on the most important region instead of shrinking the entire graph\n   - mobile landscape is offered when a wide graph, timeline, or schema materially improves tracing\n   - operational shells keep filters, outline trees, selected nodes, and inspectors synchronized without stealing space from the graph\n\n## Algorithm Defaults\n\n- Rooted ordered trees and decision trees:\n  - Prefer Reingold-Tilford style tidy trees and Buchheim's linear-time refinement.\n  - Use radial tree variants only when depth from a root matters more than label density.\n  - Do not use generic force layout for decision trees unless the tree metaphor itself is intentionally abandoned.\n- State machines, dependency graphs, workflow diagrams, class hierarchies, ERDs, and most UML-like directional diagrams:\n  - Prefer layered layout derived from Sugiyama.\n  - Use cycle breaking, layer assignment, crossing minimization, node placement, and edge routing as separate concerns.\n  - For table schemas, state diagrams, and block diagrams with connector semantics, prefer port-aware layered layout with orthogonal routing.\n- General undirected networks:\n  - Prefer stress majorization or force-directed placement when cluster shape, neighborhood, or approximate graph distance is the point.\n  - Prefer multilevel force methods for larger graphs.\n  - Avoid force layout when users need strict rank order, deterministic business flow, or table-like schemas.\n- Large topology where the graph is dense and not meaningfully hierarchical:\n  - Use multilevel force approaches, filtering, clustering, matrix fallbacks, or multiple coordinated views before cramming everything into one node-link view.\n- Nearly planar but non-planar graphs:\n  - Consider planarization pipelines when crossing count matters more than preserving a strict hierarchy.\n  - Treat this as an advanced fallback, not a default for ordinary UML-like diagrams.\n\n## Stack Defaults\n\n- Graphviz `dot`: best default for static layered layouts in documentation or build-time generation.\n- Graphviz `neato`: good default for modest undirected graphs when stress majorization is appropriate.\n- Graphviz `fdp` and `sfdp`: good for force-directed and multilevel force layouts, especially for larger undirected networks.\n- Graphviz `twopi` and `circo`: use when radial or circular structure is truly the reading model.\n- ELK Layered: best default for interactive products that need layered layout with ports, compounds, labels, orthogonal routing, or layout constraints.\n- React Flow plus ELK or Dagre: good for node editors when React owns the interaction layer and the actual layout engine remains external.\n- Cytoscape.js: good when graph analysis, graph algorithms, and multiple layout modes matter as much as the rendering.\n- Bespoke SVG, Canvas, or WebGL: use only when the visual composition or scale requires it after the algorithm family is already decided.\n\n## Anti-Patterns\n\n- Using force-directed layout for ERDs, state machines, or business workflows that have a clear direction.\n- Treating overlap removal as a substitute for choosing the right layout family.\n- Ignoring real node dimensions and then trying to fix collisions at the end.\n- Letting connectors run under schema tables, lane headers, or large node labels.\n- Relying on a single dense node-link view when a matrix, tree, outline, focus view, or filtered subgraph would explain the structure better.\n- Re-running unstable layout from scratch after every small edit in an interactive tool.\n- Shrinking text below readable size instead of using an intrinsic canvas and scrollable viewport.\n- Letting mobile controls or legends appear before the graph while the actual topology starts below the fold.\n- Requiring pixel-perfect taps on dense nodes without search, step-through, or enlarged hit regions.\n\n## Reference Guide\n\n- Read `references\u002Falgorithm-selection.md` first for graph-family to algorithm-family mapping.\n- Read `references\u002Flayered-tree-force-and-radial-layouts.md` when choosing among tree, layered, force, radial, circular, and multilevel approaches.\n- Read `references\u002Frouting-overlap-and-quality.md` for orthogonal routing, planarization, overlap removal, port constraints, and readability criteria.\n\n## Output Expectations\n\n- State the graph family and why it was classified that way.\n- State the recommended layout family and one fallback.\n- State the routing style, overlap strategy, and stability strategy.\n- Call out whether ports, order constraints, fixed nodes, or compounds require a layout engine with stronger constraint support.\n- For product work, recommend a concrete stack and make clear which part owns semantics, layout, and rendering.\n- If the graph is too dense for a clean node-link view, say so and recommend filtering, faceting, clustering, matrix views, or overview-plus-detail.\n- For mobile, state the portrait focus strategy, landscape need if any, touch target\u002Fhit-area policy, search or step-through path, and pan\u002Fzoom\u002Fbrowser gesture ownership.\n- For operational graph workspaces, state the shell, default selected or focused neighborhood, outline\u002Finspector synchronization, URL state, and empty-surface clear-selection behavior.\n- If the problem is really notation selection, route to the UML or strategy skill instead of over-solving layout alone.\n\n## Adjacent Skills\n\n- `..\u002Fdata-visualization\u002FSKILL.md`\n- `..\u002Fuml-and-software-architecture-visualization\u002FSKILL.md`\n- `..\u002Ftypescript-data-visualization-engineering\u002FSKILL.md`\n- `..\u002Freact-and-nextjs-data-visualization\u002FSKILL.md`\n- `..\u002Fd3-data-visualization\u002FSKILL.md`\n- `..\u002Fcanvas2d-data-visualization\u002FSKILL.md`\n- `..\u002Fthreejs-data-visualization\u002FSKILL.md`\n- `..\u002Ftesting-data-visualizations\u002FSKILL.md`\n- `..\u002F..\u002Freferences\u002Ffoundations\u002Fmobile-first-responsive-visualization.md`\n- `..\u002F..\u002Freferences\u002Ffoundations\u002Foperational-visualization-workspaces.md`\n\n## Representative Prompts\n\n- \"How should I auto-arrange this network diagram so the lines stop crossing so much?\"\n- \"What layout algorithm should I use for a database schema diagram?\"\n- \"Choose between ELK, Graphviz, Dagre, force layout, and a custom approach for this state machine.\"\n- \"Make this dependency graph readable without overlapping boxes and labels.\"\n- \"How do I route edges for an ERD so foreign keys do not run under the tables?\"\n- \"What should I use for a decision tree, a DAG, and an undirected network?\"\n- \"We need stable auto-layout in a React node editor.\"\n",{"data":37,"body":38},{"name":4,"description":6},{"type":39,"children":40},"root",[41,49,56,62,67,81,94,100,405,411,514,520,607,613,661,667,707,713,761,767,858,864],{"type":42,"tag":43,"props":44,"children":45},"element","h1",{"id":4},[46],{"type":47,"value":48},"text","Node-Link and Diagram Layout",{"type":42,"tag":50,"props":51,"children":53},"h2",{"id":52},"overview",[54],{"type":47,"value":55},"Overview",{"type":42,"tag":57,"props":58,"children":59},"p",{},[60],{"type":47,"value":61},"Use this skill when the main problem is not which notation to use, but how to place connected nodes so the diagram stays readable. The job is to classify the graph family, choose a layout algorithm that matches the reading task, separate node placement from edge routing and overlap removal, and recommend a stack that can preserve those constraints in production.",{"type":42,"tag":57,"props":63,"children":64},{},[65],{"type":47,"value":66},"Default assumption: the best automatic layout is the one that reinforces the intended reading path with the fewest crossings, bends, overlaps, and surprise placements. Do not treat force-directed layout as a generic answer for all diagrams. Trees, DAGs, port-constrained block diagrams, ERDs, and undirected exploration graphs usually need different algorithms.",{"type":42,"tag":57,"props":68,"children":69},{},[70,72,79],{"type":47,"value":71},"For browser-facing node-link views, mobile layout is a graph-reading constraint, not only a CSS breakpoint. Use ",{"type":42,"tag":73,"props":74,"children":76},"code",{"className":75},[],[77],{"type":47,"value":78},"..\u002F..\u002Freferences\u002Ffoundations\u002Fmobile-first-responsive-visualization.md",{"type":47,"value":80}," when choosing portrait focus views, optional landscape inspection, touch\u002Fpan\u002Fzoom ownership, and settings placement.",{"type":42,"tag":57,"props":82,"children":83},{},[84,86,92],{"type":47,"value":85},"For operational graph workspaces, use ",{"type":42,"tag":73,"props":87,"children":89},{"className":88},[],[90],{"type":47,"value":91},"..\u002F..\u002Freferences\u002Ffoundations\u002Foperational-visualization-workspaces.md",{"type":47,"value":93}," so layout decisions account for outlines, inspectors, command bars, selected neighborhoods, URL state, mobile panels, and repeated navigation.",{"type":42,"tag":50,"props":95,"children":97},{"id":96},"core-workflow",[98],{"type":47,"value":99},"Core Workflow",{"type":42,"tag":101,"props":102,"children":103},"ol",{},[104,159,207,240,278,301,329,352],{"type":42,"tag":105,"props":106,"children":107},"li",{},[108,110],{"type":47,"value":109},"Classify the graph structure before choosing a renderer:\n",{"type":42,"tag":111,"props":112,"children":113},"ul",{},[114,119,124,129,134,139,144,149,154],{"type":42,"tag":105,"props":115,"children":116},{},[117],{"type":47,"value":118},"rooted tree or forest",{"type":42,"tag":105,"props":120,"children":121},{},[122],{"type":47,"value":123},"directed acyclic graph",{"type":42,"tag":105,"props":125,"children":126},{},[127],{"type":47,"value":128},"cyclic directed graph with a dominant flow",{"type":42,"tag":105,"props":130,"children":131},{},[132],{"type":47,"value":133},"general undirected graph",{"type":42,"tag":105,"props":135,"children":136},{},[137],{"type":47,"value":138},"radial or hub-and-spoke structure",{"type":42,"tag":105,"props":140,"children":141},{},[142],{"type":47,"value":143},"clustered or compound graph",{"type":42,"tag":105,"props":145,"children":146},{},[147],{"type":47,"value":148},"port-constrained block diagram",{"type":42,"tag":105,"props":150,"children":151},{},[152],{"type":47,"value":153},"table-like schema or ERD",{"type":42,"tag":105,"props":155,"children":156},{},[157],{"type":47,"value":158},"nearly planar topology where crossing count dominates readability",{"type":42,"tag":105,"props":160,"children":161},{},[162,164],{"type":47,"value":163},"Identify the primary reading task:\n",{"type":42,"tag":111,"props":165,"children":166},{},[167,172,177,182,187,192,197,202],{"type":42,"tag":105,"props":168,"children":169},{},[170],{"type":47,"value":171},"parent-child depth",{"type":42,"tag":105,"props":173,"children":174},{},[175],{"type":47,"value":176},"top-to-bottom or left-to-right flow",{"type":42,"tag":105,"props":178,"children":179},{},[180],{"type":47,"value":181},"reachability and dependency tracing",{"type":42,"tag":105,"props":183,"children":184},{},[185],{"type":47,"value":186},"cluster discovery",{"type":42,"tag":105,"props":188,"children":189},{},[190],{"type":47,"value":191},"cycle inspection",{"type":42,"tag":105,"props":193,"children":194},{},[195],{"type":47,"value":196},"shortest path or neighborhood exploration",{"type":42,"tag":105,"props":198,"children":199},{},[200],{"type":47,"value":201},"table relationship tracing",{"type":42,"tag":105,"props":203,"children":204},{},[205],{"type":47,"value":206},"stable editing with minimal layout drift",{"type":42,"tag":105,"props":208,"children":209},{},[210,212],{"type":47,"value":211},"Record geometry constraints up front:\n",{"type":42,"tag":111,"props":213,"children":214},{},[215,220,225,230,235],{"type":42,"tag":105,"props":216,"children":217},{},[218],{"type":47,"value":219},"real node widths and heights, not point nodes",{"type":42,"tag":105,"props":221,"children":222},{},[223],{"type":47,"value":224},"labels that must fit without scaling below readability",{"type":42,"tag":105,"props":226,"children":227},{},[228],{"type":47,"value":229},"ports, handles, side constraints, or fixed connection order",{"type":42,"tag":105,"props":231,"children":232},{},[233],{"type":47,"value":234},"nested groups, lanes, clusters, or compounds",{"type":42,"tag":105,"props":236,"children":237},{},[238],{"type":47,"value":239},"whether some nodes are pinned or semi-pinned",{"type":42,"tag":105,"props":241,"children":242},{},[243,245],{"type":47,"value":244},"Choose the layout family that matches the structure:\n",{"type":42,"tag":111,"props":246,"children":247},{},[248,253,258,263,268,273],{"type":42,"tag":105,"props":249,"children":250},{},[251],{"type":47,"value":252},"tidy tree layout for rooted ordered trees and decision trees",{"type":42,"tag":105,"props":254,"children":255},{},[256],{"type":47,"value":257},"layered or Sugiyama-style layout for directional processes, state machines, dependency maps, class hierarchies, ERDs, and most UML-like flow diagrams",{"type":42,"tag":105,"props":259,"children":260},{},[261],{"type":47,"value":262},"stress majorization or force-directed layout for undirected relational exploration where cluster shape matters more than global direction",{"type":42,"tag":105,"props":264,"children":265},{},[266],{"type":47,"value":267},"radial or concentric layout when distance from a root is the main story",{"type":42,"tag":105,"props":269,"children":270},{},[271],{"type":47,"value":272},"circular layout when cycle structure is the evidence",{"type":42,"tag":105,"props":274,"children":275},{},[276],{"type":47,"value":277},"planarization-driven layout when the graph is non-planar but low crossing count is the main objective",{"type":42,"tag":105,"props":279,"children":280},{},[281,283],{"type":47,"value":282},"Choose edge routing separately from node placement:\n",{"type":42,"tag":111,"props":284,"children":285},{},[286,291,296],{"type":42,"tag":105,"props":287,"children":288},{},[289],{"type":47,"value":290},"straight or polyline when the graph is sparse and directional flow is already clear",{"type":42,"tag":105,"props":292,"children":293},{},[294],{"type":47,"value":295},"orthogonal when tables, ports, block diagrams, lanes, or circuit-like reading dominate",{"type":42,"tag":105,"props":297,"children":298},{},[299],{"type":47,"value":300},"spline routing when static aesthetics matter more than precise traceability and there is enough whitespace",{"type":42,"tag":105,"props":302,"children":303},{},[304,306],{"type":47,"value":305},"Treat overlap removal, label placement, and packing as explicit phases:\n",{"type":42,"tag":111,"props":307,"children":308},{},[309,314,319,324],{"type":42,"tag":105,"props":310,"children":311},{},[312],{"type":47,"value":313},"remove node overlap after layout if the engine starts from point nodes",{"type":42,"tag":105,"props":315,"children":316},{},[317],{"type":47,"value":318},"reserve gutters for connector-dense tables and schemas",{"type":42,"tag":105,"props":320,"children":321},{},[322],{"type":47,"value":323},"keep edge labels out of node bodies and above selected paths",{"type":42,"tag":105,"props":325,"children":326},{},[327],{"type":47,"value":328},"pack connected components only after the component layouts are individually legible",{"type":42,"tag":105,"props":330,"children":331},{},[332,334],{"type":47,"value":333},"Prefer stability when users will edit, compare revisions, or recognize repeated diagrams:\n",{"type":42,"tag":111,"props":335,"children":336},{},[337,342,347],{"type":42,"tag":105,"props":338,"children":339},{},[340],{"type":47,"value":341},"preserve node order when the source model has meaningful order",{"type":42,"tag":105,"props":343,"children":344},{},[345],{"type":47,"value":346},"preserve port order when connectors are semantically ordered",{"type":42,"tag":105,"props":348,"children":349},{},[350],{"type":47,"value":351},"use interactive or constraint-aware layered modes instead of re-randomizing",{"type":42,"tag":105,"props":353,"children":354},{},[355,357],{"type":47,"value":356},"Validate the result with readability criteria instead of trusting the engine:\n",{"type":42,"tag":111,"props":358,"children":359},{},[360,365,370,375,380,385,390,395,400],{"type":42,"tag":105,"props":361,"children":362},{},[363],{"type":47,"value":364},"crossings are low enough for the task",{"type":42,"tag":105,"props":366,"children":367},{},[368],{"type":47,"value":369},"bends are limited and meaningful",{"type":42,"tag":105,"props":371,"children":372},{},[373],{"type":47,"value":374},"nodes and labels do not overlap",{"type":42,"tag":105,"props":376,"children":377},{},[378],{"type":47,"value":379},"directionality is obvious",{"type":42,"tag":105,"props":381,"children":382},{},[383],{"type":47,"value":384},"edge tracing is possible without visual hunting",{"type":42,"tag":105,"props":386,"children":387},{},[388],{"type":47,"value":389},"the layout stays readable on narrow widths or falls back to scrolling, filtering, or faceting",{"type":42,"tag":105,"props":391,"children":392},{},[393],{"type":47,"value":394},"mobile portrait starts on the most important region instead of shrinking the entire graph",{"type":42,"tag":105,"props":396,"children":397},{},[398],{"type":47,"value":399},"mobile landscape is offered when a wide graph, timeline, or schema materially improves tracing",{"type":42,"tag":105,"props":401,"children":402},{},[403],{"type":47,"value":404},"operational shells keep filters, outline trees, selected nodes, and inspectors synchronized without stealing space from the graph",{"type":42,"tag":50,"props":406,"children":408},{"id":407},"algorithm-defaults",[409],{"type":47,"value":410},"Algorithm Defaults",{"type":42,"tag":111,"props":412,"children":413},{},[414,437,460,483,496],{"type":42,"tag":105,"props":415,"children":416},{},[417,419],{"type":47,"value":418},"Rooted ordered trees and decision trees:\n",{"type":42,"tag":111,"props":420,"children":421},{},[422,427,432],{"type":42,"tag":105,"props":423,"children":424},{},[425],{"type":47,"value":426},"Prefer Reingold-Tilford style tidy trees and Buchheim's linear-time refinement.",{"type":42,"tag":105,"props":428,"children":429},{},[430],{"type":47,"value":431},"Use radial tree variants only when depth from a root matters more than label density.",{"type":42,"tag":105,"props":433,"children":434},{},[435],{"type":47,"value":436},"Do not use generic force layout for decision trees unless the tree metaphor itself is intentionally abandoned.",{"type":42,"tag":105,"props":438,"children":439},{},[440,442],{"type":47,"value":441},"State machines, dependency graphs, workflow diagrams, class hierarchies, ERDs, and most UML-like directional diagrams:\n",{"type":42,"tag":111,"props":443,"children":444},{},[445,450,455],{"type":42,"tag":105,"props":446,"children":447},{},[448],{"type":47,"value":449},"Prefer layered layout derived from Sugiyama.",{"type":42,"tag":105,"props":451,"children":452},{},[453],{"type":47,"value":454},"Use cycle breaking, layer assignment, crossing minimization, node placement, and edge routing as separate concerns.",{"type":42,"tag":105,"props":456,"children":457},{},[458],{"type":47,"value":459},"For table schemas, state diagrams, and block diagrams with connector semantics, prefer port-aware layered layout with orthogonal routing.",{"type":42,"tag":105,"props":461,"children":462},{},[463,465],{"type":47,"value":464},"General undirected networks:\n",{"type":42,"tag":111,"props":466,"children":467},{},[468,473,478],{"type":42,"tag":105,"props":469,"children":470},{},[471],{"type":47,"value":472},"Prefer stress majorization or force-directed placement when cluster shape, neighborhood, or approximate graph distance is the point.",{"type":42,"tag":105,"props":474,"children":475},{},[476],{"type":47,"value":477},"Prefer multilevel force methods for larger graphs.",{"type":42,"tag":105,"props":479,"children":480},{},[481],{"type":47,"value":482},"Avoid force layout when users need strict rank order, deterministic business flow, or table-like schemas.",{"type":42,"tag":105,"props":484,"children":485},{},[486,488],{"type":47,"value":487},"Large topology where the graph is dense and not meaningfully hierarchical:\n",{"type":42,"tag":111,"props":489,"children":490},{},[491],{"type":42,"tag":105,"props":492,"children":493},{},[494],{"type":47,"value":495},"Use multilevel force approaches, filtering, clustering, matrix fallbacks, or multiple coordinated views before cramming everything into one node-link view.",{"type":42,"tag":105,"props":497,"children":498},{},[499,501],{"type":47,"value":500},"Nearly planar but non-planar graphs:\n",{"type":42,"tag":111,"props":502,"children":503},{},[504,509],{"type":42,"tag":105,"props":505,"children":506},{},[507],{"type":47,"value":508},"Consider planarization pipelines when crossing count matters more than preserving a strict hierarchy.",{"type":42,"tag":105,"props":510,"children":511},{},[512],{"type":47,"value":513},"Treat this as an advanced fallback, not a default for ordinary UML-like diagrams.",{"type":42,"tag":50,"props":515,"children":517},{"id":516},"stack-defaults",[518],{"type":47,"value":519},"Stack Defaults",{"type":42,"tag":111,"props":521,"children":522},{},[523,536,548,568,587,592,597,602],{"type":42,"tag":105,"props":524,"children":525},{},[526,528,534],{"type":47,"value":527},"Graphviz ",{"type":42,"tag":73,"props":529,"children":531},{"className":530},[],[532],{"type":47,"value":533},"dot",{"type":47,"value":535},": best default for static layered layouts in documentation or build-time generation.",{"type":42,"tag":105,"props":537,"children":538},{},[539,540,546],{"type":47,"value":527},{"type":42,"tag":73,"props":541,"children":543},{"className":542},[],[544],{"type":47,"value":545},"neato",{"type":47,"value":547},": good default for modest undirected graphs when stress majorization is appropriate.",{"type":42,"tag":105,"props":549,"children":550},{},[551,552,558,560,566],{"type":47,"value":527},{"type":42,"tag":73,"props":553,"children":555},{"className":554},[],[556],{"type":47,"value":557},"fdp",{"type":47,"value":559}," and ",{"type":42,"tag":73,"props":561,"children":563},{"className":562},[],[564],{"type":47,"value":565},"sfdp",{"type":47,"value":567},": good for force-directed and multilevel force layouts, especially for larger undirected networks.",{"type":42,"tag":105,"props":569,"children":570},{},[571,572,578,579,585],{"type":47,"value":527},{"type":42,"tag":73,"props":573,"children":575},{"className":574},[],[576],{"type":47,"value":577},"twopi",{"type":47,"value":559},{"type":42,"tag":73,"props":580,"children":582},{"className":581},[],[583],{"type":47,"value":584},"circo",{"type":47,"value":586},": use when radial or circular structure is truly the reading model.",{"type":42,"tag":105,"props":588,"children":589},{},[590],{"type":47,"value":591},"ELK Layered: best default for interactive products that need layered layout with ports, compounds, labels, orthogonal routing, or layout constraints.",{"type":42,"tag":105,"props":593,"children":594},{},[595],{"type":47,"value":596},"React Flow plus ELK or Dagre: good for node editors when React owns the interaction layer and the actual layout engine remains external.",{"type":42,"tag":105,"props":598,"children":599},{},[600],{"type":47,"value":601},"Cytoscape.js: good when graph analysis, graph algorithms, and multiple layout modes matter as much as the rendering.",{"type":42,"tag":105,"props":603,"children":604},{},[605],{"type":47,"value":606},"Bespoke SVG, Canvas, or WebGL: use only when the visual composition or scale requires it after the algorithm family is already decided.",{"type":42,"tag":50,"props":608,"children":610},{"id":609},"anti-patterns",[611],{"type":47,"value":612},"Anti-Patterns",{"type":42,"tag":111,"props":614,"children":615},{},[616,621,626,631,636,641,646,651,656],{"type":42,"tag":105,"props":617,"children":618},{},[619],{"type":47,"value":620},"Using force-directed layout for ERDs, state machines, or business workflows that have a clear direction.",{"type":42,"tag":105,"props":622,"children":623},{},[624],{"type":47,"value":625},"Treating overlap removal as a substitute for choosing the right layout family.",{"type":42,"tag":105,"props":627,"children":628},{},[629],{"type":47,"value":630},"Ignoring real node dimensions and then trying to fix collisions at the end.",{"type":42,"tag":105,"props":632,"children":633},{},[634],{"type":47,"value":635},"Letting connectors run under schema tables, lane headers, or large node labels.",{"type":42,"tag":105,"props":637,"children":638},{},[639],{"type":47,"value":640},"Relying on a single dense node-link view when a matrix, tree, outline, focus view, or filtered subgraph would explain the structure better.",{"type":42,"tag":105,"props":642,"children":643},{},[644],{"type":47,"value":645},"Re-running unstable layout from scratch after every small edit in an interactive tool.",{"type":42,"tag":105,"props":647,"children":648},{},[649],{"type":47,"value":650},"Shrinking text below readable size instead of using an intrinsic canvas and scrollable viewport.",{"type":42,"tag":105,"props":652,"children":653},{},[654],{"type":47,"value":655},"Letting mobile controls or legends appear before the graph while the actual topology starts below the fold.",{"type":42,"tag":105,"props":657,"children":658},{},[659],{"type":47,"value":660},"Requiring pixel-perfect taps on dense nodes without search, step-through, or enlarged hit regions.",{"type":42,"tag":50,"props":662,"children":664},{"id":663},"reference-guide",[665],{"type":47,"value":666},"Reference Guide",{"type":42,"tag":111,"props":668,"children":669},{},[670,683,695],{"type":42,"tag":105,"props":671,"children":672},{},[673,675,681],{"type":47,"value":674},"Read ",{"type":42,"tag":73,"props":676,"children":678},{"className":677},[],[679],{"type":47,"value":680},"references\u002Falgorithm-selection.md",{"type":47,"value":682}," first for graph-family to algorithm-family mapping.",{"type":42,"tag":105,"props":684,"children":685},{},[686,687,693],{"type":47,"value":674},{"type":42,"tag":73,"props":688,"children":690},{"className":689},[],[691],{"type":47,"value":692},"references\u002Flayered-tree-force-and-radial-layouts.md",{"type":47,"value":694}," when choosing among tree, layered, force, radial, circular, and multilevel approaches.",{"type":42,"tag":105,"props":696,"children":697},{},[698,699,705],{"type":47,"value":674},{"type":42,"tag":73,"props":700,"children":702},{"className":701},[],[703],{"type":47,"value":704},"references\u002Frouting-overlap-and-quality.md",{"type":47,"value":706}," for orthogonal routing, planarization, overlap removal, port constraints, and readability criteria.",{"type":42,"tag":50,"props":708,"children":710},{"id":709},"output-expectations",[711],{"type":47,"value":712},"Output Expectations",{"type":42,"tag":111,"props":714,"children":715},{},[716,721,726,731,736,741,746,751,756],{"type":42,"tag":105,"props":717,"children":718},{},[719],{"type":47,"value":720},"State the graph family and why it was classified that way.",{"type":42,"tag":105,"props":722,"children":723},{},[724],{"type":47,"value":725},"State the recommended layout family and one fallback.",{"type":42,"tag":105,"props":727,"children":728},{},[729],{"type":47,"value":730},"State the routing style, overlap strategy, and stability strategy.",{"type":42,"tag":105,"props":732,"children":733},{},[734],{"type":47,"value":735},"Call out whether ports, order constraints, fixed nodes, or compounds require a layout engine with stronger constraint support.",{"type":42,"tag":105,"props":737,"children":738},{},[739],{"type":47,"value":740},"For product work, recommend a concrete stack and make clear which part owns semantics, layout, and rendering.",{"type":42,"tag":105,"props":742,"children":743},{},[744],{"type":47,"value":745},"If the graph is too dense for a clean node-link view, say so and recommend filtering, faceting, clustering, matrix views, or overview-plus-detail.",{"type":42,"tag":105,"props":747,"children":748},{},[749],{"type":47,"value":750},"For mobile, state the portrait focus strategy, landscape need if any, touch target\u002Fhit-area policy, search or step-through path, and pan\u002Fzoom\u002Fbrowser gesture ownership.",{"type":42,"tag":105,"props":752,"children":753},{},[754],{"type":47,"value":755},"For operational graph workspaces, state the shell, default selected or focused neighborhood, outline\u002Finspector synchronization, URL state, and empty-surface clear-selection behavior.",{"type":42,"tag":105,"props":757,"children":758},{},[759],{"type":47,"value":760},"If the problem is really notation selection, route to the UML or strategy skill instead of over-solving layout alone.",{"type":42,"tag":50,"props":762,"children":764},{"id":763},"adjacent-skills",[765],{"type":47,"value":766},"Adjacent Skills",{"type":42,"tag":111,"props":768,"children":769},{},[770,779,788,797,806,815,824,833,842,850],{"type":42,"tag":105,"props":771,"children":772},{},[773],{"type":42,"tag":73,"props":774,"children":776},{"className":775},[],[777],{"type":47,"value":778},"..\u002Fdata-visualization\u002FSKILL.md",{"type":42,"tag":105,"props":780,"children":781},{},[782],{"type":42,"tag":73,"props":783,"children":785},{"className":784},[],[786],{"type":47,"value":787},"..\u002Fuml-and-software-architecture-visualization\u002FSKILL.md",{"type":42,"tag":105,"props":789,"children":790},{},[791],{"type":42,"tag":73,"props":792,"children":794},{"className":793},[],[795],{"type":47,"value":796},"..\u002Ftypescript-data-visualization-engineering\u002FSKILL.md",{"type":42,"tag":105,"props":798,"children":799},{},[800],{"type":42,"tag":73,"props":801,"children":803},{"className":802},[],[804],{"type":47,"value":805},"..\u002Freact-and-nextjs-data-visualization\u002FSKILL.md",{"type":42,"tag":105,"props":807,"children":808},{},[809],{"type":42,"tag":73,"props":810,"children":812},{"className":811},[],[813],{"type":47,"value":814},"..\u002Fd3-data-visualization\u002FSKILL.md",{"type":42,"tag":105,"props":816,"children":817},{},[818],{"type":42,"tag":73,"props":819,"children":821},{"className":820},[],[822],{"type":47,"value":823},"..\u002Fcanvas2d-data-visualization\u002FSKILL.md",{"type":42,"tag":105,"props":825,"children":826},{},[827],{"type":42,"tag":73,"props":828,"children":830},{"className":829},[],[831],{"type":47,"value":832},"..\u002Fthreejs-data-visualization\u002FSKILL.md",{"type":42,"tag":105,"props":834,"children":835},{},[836],{"type":42,"tag":73,"props":837,"children":839},{"className":838},[],[840],{"type":47,"value":841},"..\u002Ftesting-data-visualizations\u002FSKILL.md",{"type":42,"tag":105,"props":843,"children":844},{},[845],{"type":42,"tag":73,"props":846,"children":848},{"className":847},[],[849],{"type":47,"value":78},{"type":42,"tag":105,"props":851,"children":852},{},[853],{"type":42,"tag":73,"props":854,"children":856},{"className":855},[],[857],{"type":47,"value":91},{"type":42,"tag":50,"props":859,"children":861},{"id":860},"representative-prompts",[862],{"type":47,"value":863},"Representative Prompts",{"type":42,"tag":111,"props":865,"children":866},{},[867,872,877,882,887,892,897],{"type":42,"tag":105,"props":868,"children":869},{},[870],{"type":47,"value":871},"\"How should I auto-arrange this network diagram so the lines stop crossing so much?\"",{"type":42,"tag":105,"props":873,"children":874},{},[875],{"type":47,"value":876},"\"What layout algorithm should I use for a database schema diagram?\"",{"type":42,"tag":105,"props":878,"children":879},{},[880],{"type":47,"value":881},"\"Choose between ELK, Graphviz, Dagre, force layout, and a custom approach for this state machine.\"",{"type":42,"tag":105,"props":883,"children":884},{},[885],{"type":47,"value":886},"\"Make this dependency graph readable without overlapping boxes and labels.\"",{"type":42,"tag":105,"props":888,"children":889},{},[890],{"type":47,"value":891},"\"How do I route edges for an ERD so foreign keys do not run under the tables?\"",{"type":42,"tag":105,"props":893,"children":894},{},[895],{"type":47,"value":896},"\"What should I use for a decision tree, a DAG, and an undirected network?\"",{"type":42,"tag":105,"props":898,"children":899},{},[900],{"type":47,"value":901},"\"We need stable auto-layout in a React node editor.\"",{"items":903,"total":1020},[904,920,936,948,968,988,1008],{"slug":905,"name":905,"fn":906,"description":907,"org":908,"tags":909,"stars":25,"repoUrl":26,"updatedAt":27},"accessibility-and-inclusive-visualization","make data visualizations accessible","Make data visualizations accessible and inclusive. Use when the user needs chart or diagram accessibility guidance, text alternatives for complex visuals, color and contrast review, keyboard support, reduced-motion behavior for animation or parallax, or an accessibility QA workflow for exported figures, UML-like diagrams, and dashboards.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[910,913,916,919],{"name":911,"slug":912,"type":15},"Accessibility","accessibility",{"name":914,"slug":915,"type":15},"Charts","charts",{"name":917,"slug":918,"type":15},"Data Visualization","data-visualization",{"name":23,"slug":24,"type":15},{"slug":921,"name":921,"fn":922,"description":923,"org":924,"tags":925,"stars":25,"repoUrl":26,"updatedAt":935},"agent-browser","automate browser interactions for agents","Browser automation CLI for AI agents. Use when the user needs to interact with websites, verify dev server output, test web apps, navigate pages, fill forms, click buttons, take screenshots, extract data, or automate any browser task. Also triggers when a dev server starts so you can verify it visually.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[926,929,932],{"name":927,"slug":928,"type":15},"Agents","agents",{"name":930,"slug":931,"type":15},"Browser Automation","browser-automation",{"name":933,"slug":934,"type":15},"Testing","testing","2026-04-06T18:41:03.44016",{"slug":937,"name":937,"fn":938,"description":939,"org":940,"tags":941,"stars":25,"repoUrl":26,"updatedAt":947},"agent-browser-verify","verify dev server output with automated browser","Automated browser verification for dev servers. Triggers when a dev server starts to run a visual gut-check with agent-browser — verifies the page loads, checks for console errors, validates key UI elements, and reports pass\u002Ffail before continuing.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[942,943,946],{"name":930,"slug":931,"type":15},{"name":944,"slug":945,"type":15},"Local Development","local-development",{"name":933,"slug":934,"type":15},"2026-04-06T18:41:17.526867",{"slug":949,"name":949,"fn":950,"description":951,"org":952,"tags":953,"stars":25,"repoUrl":26,"updatedAt":967},"agents-sdk","build AI agents on Cloudflare Workers","Build AI agents on Cloudflare Workers using the Agents SDK. Load when creating stateful agents, durable workflows, real-time WebSocket apps, scheduled tasks, MCP servers, or chat applications. Covers Agent class, state management, callable RPC, Workflows integration, and React hooks. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[954,955,958,961,964],{"name":927,"slug":928,"type":15},{"name":956,"slug":957,"type":15},"Cloudflare Workers","cloudflare-workers",{"name":959,"slug":960,"type":15},"SDK","sdk",{"name":962,"slug":963,"type":15},"Serverless","serverless",{"name":965,"slug":966,"type":15},"WebSockets","websockets","2026-04-06T18:39:51.717063",{"slug":969,"name":969,"fn":970,"description":971,"org":972,"tags":973,"stars":25,"repoUrl":26,"updatedAt":987},"ai-elements","build chat UIs with AI Elements","AI Elements component library guidance — pre-built React components for AI interfaces built on shadcn\u002Fui. Use when building chat UIs, message displays, tool call rendering, streaming responses, reasoning panels, or any AI-native interface with the AI SDK.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[974,977,980,983,984],{"name":975,"slug":976,"type":15},"Frontend","frontend",{"name":978,"slug":979,"type":15},"React","react",{"name":981,"slug":982,"type":15},"shadcn\u002Fui","shadcn-ui",{"name":20,"slug":21,"type":15},{"name":985,"slug":986,"type":15},"Vercel","vercel","2026-04-06T18:40:59.619419",{"slug":989,"name":989,"fn":990,"description":991,"org":992,"tags":993,"stars":25,"repoUrl":26,"updatedAt":1007},"ai-gateway","configure Vercel AI Gateway","Vercel AI Gateway expert guidance. Use when configuring model routing, provider failover, cost tracking, or managing multiple AI providers through a unified API.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[994,997,1000,1003,1006],{"name":995,"slug":996,"type":15},"AI Infrastructure","ai-infrastructure",{"name":998,"slug":999,"type":15},"Cost Optimization","cost-optimization",{"name":1001,"slug":1002,"type":15},"LLM","llm",{"name":1004,"slug":1005,"type":15},"Performance","performance",{"name":985,"slug":986,"type":15},"2026-04-06T18:40:44.377464",{"slug":1009,"name":1009,"fn":1010,"description":1011,"org":1012,"tags":1013,"stars":25,"repoUrl":26,"updatedAt":1019},"ai-generation-persistence","implement persistence patterns for AI generations","AI generation persistence patterns — unique IDs, addressable URLs, database storage, and cost tracking for every LLM generation",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1014,1015,1018],{"name":998,"slug":999,"type":15},{"name":1016,"slug":1017,"type":15},"Database","database",{"name":1001,"slug":1002,"type":15},"2026-04-06T18:41:08.513425",600,{"items":1022,"total":1219},[1023,1044,1067,1084,1100,1117,1136,1148,1162,1176,1188,1203],{"slug":1024,"name":1024,"fn":1025,"description":1026,"org":1027,"tags":1028,"stars":1041,"repoUrl":1042,"updatedAt":1043},"prior-auth-packet-builder","build healthcare prior authorization packets","Build a concise prior authorization packet from local case files and payer policy docs.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1029,1032,1035,1038],{"name":1030,"slug":1031,"type":15},"Documents","documents",{"name":1033,"slug":1034,"type":15},"Healthcare","healthcare",{"name":1036,"slug":1037,"type":15},"Insurance","insurance",{"name":1039,"slug":1040,"type":15},"Regulatory Compliance","regulatory-compliance",28169,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fopenai-agents-python","2026-04-16T05:11:39.180399",{"slug":1045,"name":1045,"fn":1046,"description":1047,"org":1048,"tags":1049,"stars":1064,"repoUrl":1065,"updatedAt":1066},"aspnet-core","build ASP.NET Core web applications","Build, review, refactor, or architect ASP.NET Core web applications using current official guidance for .NET web development. Use when working on Blazor Web Apps, Razor Pages, MVC, Minimal APIs, controller-based Web APIs, SignalR, gRPC, middleware, dependency injection, configuration, authentication, authorization, testing, performance, deployment, or ASP.NET Core upgrades.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1050,1053,1055,1058,1061],{"name":1051,"slug":1052,"type":15},".NET","dotnet",{"name":1054,"slug":1045,"type":15},"ASP.NET Core",{"name":1056,"slug":1057,"type":15},"Blazor","blazor",{"name":1059,"slug":1060,"type":15},"C#","csharp",{"name":1062,"slug":1063,"type":15},"Web Development","web-development",23787,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fskills","2026-04-12T05:07:02.819491",{"slug":1068,"name":1068,"fn":1069,"description":1070,"org":1071,"tags":1072,"stars":1064,"repoUrl":1065,"updatedAt":1083},"chatgpt-apps","build ChatGPT Apps SDK applications","Build, scaffold, refactor, and troubleshoot ChatGPT Apps SDK applications that combine an MCP server and widget UI. Use when Codex needs to design tools, register UI resources, wire the MCP Apps bridge or ChatGPT compatibility APIs, apply Apps SDK metadata or CSP or domain settings, or produce a docs-aligned project scaffold. Prefer a docs-first workflow by invoking the openai-docs skill or OpenAI developer docs MCP tools before generating code.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1073,1076,1079,1082],{"name":1074,"slug":1075,"type":15},"Apps SDK","apps-sdk",{"name":1077,"slug":1078,"type":15},"ChatGPT","chatgpt",{"name":1080,"slug":1081,"type":15},"MCP","mcp",{"name":9,"slug":8,"type":15},"2026-04-12T05:07:05.468097",{"slug":1085,"name":1085,"fn":1086,"description":1087,"org":1088,"tags":1089,"stars":1064,"repoUrl":1065,"updatedAt":1099},"cli-creator","build CLIs from API docs","Build a composable CLI for Codex from API docs, an OpenAPI spec, existing curl examples, an SDK, a web app, an admin tool, or a local script. Use when the user wants Codex to create a command-line tool that can run from any repo, expose composable read\u002Fwrite commands, return stable JSON, manage auth, and pair with a companion skill.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1090,1093,1096],{"name":1091,"slug":1092,"type":15},"API Development","api-development",{"name":1094,"slug":1095,"type":15},"CLI","cli",{"name":1097,"slug":1098,"type":15},"Codex","codex","2026-04-12T05:07:04.132762",{"slug":1101,"name":1101,"fn":1102,"description":1103,"org":1104,"tags":1105,"stars":1064,"repoUrl":1065,"updatedAt":1116},"cloudflare-deploy","deploy projects to Cloudflare","Deploy applications and infrastructure to Cloudflare using Workers, Pages, and related platform services. Use when the user asks to deploy, host, publish, or set up a project on Cloudflare.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1106,1109,1112,1113],{"name":1107,"slug":1108,"type":15},"Cloudflare","cloudflare",{"name":1110,"slug":1111,"type":15},"Cloudflare Pages","cloudflare-pages",{"name":956,"slug":957,"type":15},{"name":1114,"slug":1115,"type":15},"Deployment","deployment","2026-04-12T05:07:14.275118",{"slug":1118,"name":1118,"fn":1119,"description":1120,"org":1121,"tags":1122,"stars":1064,"repoUrl":1065,"updatedAt":1135},"define-goal","define and set measurable project goals","Help the user define a concrete, measurable goal before starting work, especially when they ask to use the goal tool, create a goal, set an objective, clarify success criteria, or turn a fuzzy intention into a quantitative outcome. Use this skill for goal creation and goal refinement only; it does not manage durable snapshots, decision logs, or long-running execution artifacts.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1123,1126,1129,1132],{"name":1124,"slug":1125,"type":15},"Productivity","productivity",{"name":1127,"slug":1128,"type":15},"Project Management","project-management",{"name":1130,"slug":1131,"type":15},"Strategy","strategy",{"name":1133,"slug":1134,"type":15},"Task Management","task-management","2026-05-23T06:17:16.870838",{"slug":1137,"name":1137,"fn":1138,"description":1139,"org":1140,"tags":1141,"stars":1064,"repoUrl":1065,"updatedAt":1147},"figma","translate Figma designs into code","Use the Figma MCP server to fetch design context, screenshots, variables, and assets from Figma, and to translate Figma nodes into production code. Trigger when a task involves Figma URLs, node IDs, design-to-code implementation, or Figma MCP setup and troubleshooting.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1142,1143,1145,1146],{"name":23,"slug":24,"type":15},{"name":1144,"slug":1137,"type":15},"Figma",{"name":975,"slug":976,"type":15},{"name":1080,"slug":1081,"type":15},"2026-04-12T05:06:47.939943",{"slug":1149,"name":1149,"fn":1150,"description":1151,"org":1152,"tags":1153,"stars":1064,"repoUrl":1065,"updatedAt":1161},"figma-code-connect-components","connect Figma designs to code components","Connects Figma design components to code components using Code Connect mapping tools. Use when user says \"code connect\", \"connect this component to code\", \"map this component\", \"link component to code\", \"create code connect mapping\", or wants to establish mappings between Figma designs and code implementations. For canvas writes via `use_figma`, use `figma-use`.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1154,1155,1158,1159,1160],{"name":23,"slug":24,"type":15},{"name":1156,"slug":1157,"type":15},"Design System","design-system",{"name":1144,"slug":1137,"type":15},{"name":975,"slug":976,"type":15},{"name":20,"slug":21,"type":15},"2026-05-10T05:59:52.971881",{"slug":1163,"name":1163,"fn":1164,"description":1165,"org":1166,"tags":1167,"stars":1064,"repoUrl":1065,"updatedAt":1175},"figma-create-design-system-rules","generate design system rules from Figma","Generates custom design system rules for the user's codebase. Use when user says \"create design system rules\", \"generate rules for my project\", \"set up design rules\", \"customize design system guidelines\", or wants to establish project-specific conventions for Figma-to-code workflows. Requires Figma MCP server connection.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1168,1169,1170,1173,1174],{"name":23,"slug":24,"type":15},{"name":1156,"slug":1157,"type":15},{"name":1171,"slug":1172,"type":15},"Documentation","documentation",{"name":1144,"slug":1137,"type":15},{"name":975,"slug":976,"type":15},"2026-05-16T06:07:47.821474",{"slug":1177,"name":1177,"fn":1178,"description":1179,"org":1180,"tags":1181,"stars":1064,"repoUrl":1065,"updatedAt":1187},"figma-implement-design","translate Figma designs into application code","Translates Figma designs into production-ready application code with 1:1 visual fidelity. Use when implementing UI code from Figma files, when user mentions \"implement design\", \"generate code\", \"implement component\", provides Figma URLs, or asks to build components matching Figma specs. For Figma canvas writes via `use_figma`, use `figma-use`.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1182,1183,1184,1185,1186],{"name":23,"slug":24,"type":15},{"name":1144,"slug":1137,"type":15},{"name":975,"slug":976,"type":15},{"name":20,"slug":21,"type":15},{"name":1062,"slug":1063,"type":15},"2026-05-16T06:07:40.583615",{"slug":1189,"name":1189,"fn":1190,"description":1191,"org":1192,"tags":1193,"stars":1064,"repoUrl":1065,"updatedAt":1202},"hatch-pet","create animated pets for Codex","Create, repair, validate, visually QA, and package Codex-compatible animated pets and pet spritesheets from character art, generated images, company or prospect brand cues, or visual references. Use when a user wants a lightweight-worker Codex pet workflow, a non-pixel custom pet style, a prospect or company mascot pet, or a full 8x9 animated pet atlas with transparent unused cells, QA contact sheets, and pet.json packaging. This skill composes the installed $imagegen system skill for visual generation and uses bundled scripts for deterministic spritesheet assembly.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1194,1197,1198,1201],{"name":1195,"slug":1196,"type":15},"Animation","animation",{"name":1097,"slug":1098,"type":15},{"name":1199,"slug":1200,"type":15},"Creative","creative",{"name":23,"slug":24,"type":15},"2026-05-02T05:31:48.48485",{"slug":1204,"name":1204,"fn":1205,"description":1206,"org":1207,"tags":1208,"stars":1064,"repoUrl":1065,"updatedAt":1218},"imagegen","generate and edit raster images","Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output should be a bitmap asset rather than repo-native code or vector. Do not use when the task is better handled by editing existing SVG\u002Fvector\u002Fcode-native assets, extending an established icon or logo system, or building the visual directly in HTML\u002FCSS\u002Fcanvas.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[1209,1210,1211,1214,1217],{"name":1199,"slug":1200,"type":15},{"name":23,"slug":24,"type":15},{"name":1212,"slug":1213,"type":15},"Image Generation","image-generation",{"name":1215,"slug":1216,"type":15},"Images","images",{"name":9,"slug":8,"type":15},"2026-05-15T06:23:24.312127",675]