[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-openai-d3-data-visualization":3,"mdc--unhc3d-key":36,"related-org-openai-d3-data-visualization":796,"related-repo-openai-d3-data-visualization":1001},{"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},"d3-data-visualization","build custom data visualizations with D3","Build custom data visualizations with D3. Use when the user needs SVG or DOM-based charts, rich annotation, domain-native contextual backgrounds, data joins, custom scales or interactions, scroll-driven SVG scene states, or precise control over browser visualization behavior.",{"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},"Data Visualization","data-visualization","tag",{"name":17,"slug":18,"type":15},"HTML","html",{"name":20,"slug":21,"type":15},"Charts","charts",{"name":23,"slug":24,"type":15},"Frontend","frontend",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\u002Fd3-data-visualization","---\nname: d3-data-visualization\ndescription: Build custom data visualizations with D3. Use when the user needs SVG or DOM-based charts, rich annotation, domain-native contextual backgrounds, data joins, custom scales or interactions, scroll-driven SVG scene states, or precise control over browser visualization behavior.\n---\n\n# D3 Data Visualization\n\n## Overview\n\nUse this skill for custom browser visualizations where SVG or DOM semantics matter and a declarative grammar no longer fits cleanly. D3 is strongest when the chart needs bespoke scales, marks, layouts, transitions, zooming, brushing, annotations, or vector export.\n\nDefault assumption: use D3 for scales, layouts, geometry, labels, annotation layers, and behavior. Do not turn D3 into the entire application architecture if a framework already owns the surrounding UI.\n\n## Choose D3 When\n\n- the chart needs custom marks or nonstandard layouts\n- SVG quality matters for export, print, or accessibility\n- annotation and labeling are part of the design, not an afterthought\n- the visualization needs custom vector background geometry such as a field, court, track, floor plan, schematic, or other meaningful contextual surface\n- an editorial story needs data-bound generated cutouts, illustrated substrates, scrollytelling\u002Fparallax states, or animated annotation reveals in SVG\n- the mark count is moderate enough for DOM or SVG\n- the interaction model needs zoom, brush, drag, or coordinated views\n- a UML-like, dependency, architecture, state, or flow diagram needs bespoke SVG annotation or product-specific composition after `..\u002Fuml-and-software-architecture-visualization\u002FSKILL.md` has defined the diagram semantics\n- a declarative grammar would become harder to read than the resulting D3 code\n\n## Avoid D3-First DOM Rendering When\n\n- mark counts are so large that DOM throughput becomes the bottleneck\n- animation is continuous and frame budgets are tight\n- the task would be faster to solve with Canvas2D or WebGL\n\n## Working Pattern\n\n1. Build a clean data model first.\n2. Separate:\n   - parsing and normalization\n   - scale construction\n   - derived geometry\n   - rendering\n   - interaction state\n3. Prefer stable keys in joins.\n4. Use D3 for math and behavior, not for hiding weak state management.\n5. Assess how many D3 instances may coexist on the page so DOM, layout, and event costs are evaluated at dashboard scale.\n6. If using a contextual surface, keep source units and render scales explicit, draw the background as a separate layer, and adapt mark placement or layout forces to the domain geometry.\n7. For art-directed stories, keep generated image, substrate, data-mark, label, and annotation layers separate so each can be reviewed and exported.\n8. Keep annotations and interaction overlays explicit.\n9. For SVG output, apply `.\u002Freferences\u002Fsvg-polish-and-crispness.md` before calling the chart finished. Explicitly set font sizes, tick padding, gridline strokes, data stroke widths, icon sizes, label alignment, and zoom-stable stroke behavior.\n10. For browser-facing work, use `..\u002F..\u002Freferences\u002Ffoundations\u002Fmobile-first-responsive-visualization.md` so the D3 layout is recomputed for large-screen and mobile states rather than scaled down from one desktop SVG.\n\n## Editorial Defaults\n\n- Build an explicit label layer. Direct end labels, inline keys, or panel labels should be considered before a detached legend.\n- Build an explicit annotation layer. Callouts should attach to data points, ranges, thresholds, or domain geometry rather than floating as decoration.\n- Keep gridlines, axes, and reference marks quiet. Most ink should be data, labels, or annotation.\n- Default SVG chart polish: 10-12 px axis ticks, 11-13.5 px direct labels, 0.5-1 px non-data strokes, 1.5-2.25 px normal data lines, 2.5-3 px focus lines, short 4-6 px ticks, and no heavy chart border unless it carries meaning.\n- Use D3 axes as geometry generators, then style them. Prefer `.tickSizeOuter(0)`, 6-8 px tick padding, quiet gridlines, removed domains when redundant, and fewer ticks before rotated or tiny labels.\n- Use `shape-rendering: crispEdges` for straight axes, gridlines, and rectangular cells; do not apply it globally to curves, symbols, circles, or diagonal marks.\n- Use `vector-effect: non-scaling-stroke` for zoomable outlines, axes, annotation connectors, map borders, and icons that should keep screen-stable stroke weight.\n- Use custom layout only when the story needs it; do not copy a publication's composition or visual identity.\n- For narrow widths, provide either a simplified mark layout, small-multiple stack, or numbered annotation key below the chart.\n- On mobile, make tap\u002Ffocus the inspection path, enlarge hit areas beyond visible marks, provide drag alternatives, define pinch or zoom ownership, and keep the main chart visible when filters or settings open.\n- Favor inspectable SVG for editorial charts that need export, accessibility, and precise labels. Move dense mark fields to Canvas only when the DOM count justifies it.\n- For scrollytelling or parallax, use `..\u002Fscrollytelling-and-parallax-data-visualization\u002FSKILL.md` for the scroll narrative, then let D3 own scales, derived geometry, data joins, labels, and SVG transitions. Keep each scene valid as a still.\n- For generated imagery, use D3\u002FSVG for labels, anchors, masks, clipping, and data overlays rather than baking numbers into images.\n- For motion, use transitions to reveal sequence, direction, accumulation, comparison, or mechanism. Respect reduced-motion with final-state rendering.\n- For 3D-looking SVG, avoid perspective distortion unless it represents a real multiaxis surface; label axes and provide a flat fallback when needed.\n\n## Core D3 Building Blocks\n\n- `d3-array` for grouping, extent, ticks, and summaries\n- `d3-scale` for position, color, and size mappings\n- `d3-axis` for readable axes\n- `d3-shape` for lines, areas, arcs, and symbol generation\n- `d3-selection` and `d3-transition` for DOM behavior\n- `d3-brush`, `d3-zoom`, and `d3-drag` for direct manipulation\n- `d3-force`, `d3-hierarchy`, `d3-contour`, and other layouts only when their data structure fits\n\n## Integration Rules\n\n- In React or another UI framework, prefer framework-owned structure and D3-owned geometry, scales, and behaviors.\n- For highly custom charts, a small imperative D3 island is fine if the boundary is clear.\n- Keep responsive behavior tied to container measurements, not magic constants.\n- Recompute labels, tick counts, annotation placement, collision rules, and plot height for mobile portrait and optional landscape sizes; do not only resize the outer `viewBox`.\n- Prefer SVG for labels and annotations even in hybrid systems.\n- Keep contextual background layers non-interactive unless they are part of selection, zoom, or hit testing.\n- Move to Canvas or WebGL when DOM count or continuous redraw becomes the limiting factor.\n\n## Output Expectations\n\n- Explain why D3 is the right rendering layer.\n- Keep chart structure semantic and inspectable.\n- Provide export paths for SVG or PNG when needed.\n- Pair interaction with obvious annotation and reset controls.\n- For mobile, state the touch target policy, hover replacement, drag\u002Fpinch ownership, and how the on-screen keyboard or settings panels return the user to the chart.\n- When drawing a contextual surface, state the source geometry and how data marks are positioned, constrained, or biased by it.\n- For image-supported editorial work, state which assets are generated, which layers remain data-bound, and how labels anchor to the substrate.\n- For animation, state the verb, scene states, duration budget, and reduced-motion fallback.\n- For new work, include a technical design section covering simultaneous instance count, DOM and interaction cost, and maintenance tradeoffs versus declarative or Canvas-based alternatives.\n\n## References\n\n- Shared theory:\n  - `..\u002F..\u002Freferences\u002Ffoundations\u002Feditorial-infographic-system.md`\n  - `..\u002F..\u002Freferences\u002Ffoundations\u002Fart-directed-interactive-visual-stories.md`\n  - `..\u002F..\u002Freferences\u002Ffoundations\u002Fperception-color-and-encoding.md`\n  - `..\u002F..\u002Freferences\u002Ffoundations\u002Fmobile-first-responsive-visualization.md`\n  - `..\u002F..\u002Freferences\u002Ffoundations\u002Fdomain-contextual-surfaces.md`\n  - `..\u002F..\u002Freferences\u002Ffoundations\u002Fstorytelling-annotation-and-critique.md`\n  - `..\u002F..\u002Freferences\u002Ffoundations\u002Fimplementation-design-and-tradeoffs.md`\n- Skill references:\n  - `.\u002Freferences\u002Fd3-module-map.md`\n  - `.\u002Freferences\u002Fd3-architecture-patterns.md`\n  - `.\u002Freferences\u002Fd3-interaction-and-annotation.md`\n  - `.\u002Freferences\u002Fd3-pitfalls-and-scale-limits.md`\n  - `.\u002Freferences\u002Fsvg-polish-and-crispness.md`\n  - `..\u002Fuml-and-software-architecture-visualization\u002FSKILL.md`\n  - `..\u002Fscrollytelling-and-parallax-data-visualization\u002FSKILL.md`\n\n## Representative Prompts\n\n- \"Build a D3 slopegraph with direct labels.\"\n- \"Add zoom and brushing to this scatterplot.\"\n- \"Create a publication-quality SVG chart from this dataset.\"\n- \"Draw a domain-accurate soccer pitch behind a player network and bias node positions by role.\"\n- \"Refactor this D3 chart so React owns layout and D3 owns math.\"\n- \"Animate this D3 chart through scrollytelling scene states.\"\n- \"Tell me when this D3 chart should move to Canvas.\"\n",{"data":37,"body":38},{"name":4,"description":6},{"type":39,"children":40},"root",[41,49,56,62,67,73,132,138,156,162,260,266,375,381,499,505,551,557,605,611,752,758],{"type":42,"tag":43,"props":44,"children":45},"element","h1",{"id":4},[46],{"type":47,"value":48},"text","D3 Data Visualization",{"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 for custom browser visualizations where SVG or DOM semantics matter and a declarative grammar no longer fits cleanly. D3 is strongest when the chart needs bespoke scales, marks, layouts, transitions, zooming, brushing, annotations, or vector export.",{"type":42,"tag":57,"props":63,"children":64},{},[65],{"type":47,"value":66},"Default assumption: use D3 for scales, layouts, geometry, labels, annotation layers, and behavior. Do not turn D3 into the entire application architecture if a framework already owns the surrounding UI.",{"type":42,"tag":50,"props":68,"children":70},{"id":69},"choose-d3-when",[71],{"type":47,"value":72},"Choose D3 When",{"type":42,"tag":74,"props":75,"children":76},"ul",{},[77,83,88,93,98,103,108,113,127],{"type":42,"tag":78,"props":79,"children":80},"li",{},[81],{"type":47,"value":82},"the chart needs custom marks or nonstandard layouts",{"type":42,"tag":78,"props":84,"children":85},{},[86],{"type":47,"value":87},"SVG quality matters for export, print, or accessibility",{"type":42,"tag":78,"props":89,"children":90},{},[91],{"type":47,"value":92},"annotation and labeling are part of the design, not an afterthought",{"type":42,"tag":78,"props":94,"children":95},{},[96],{"type":47,"value":97},"the visualization needs custom vector background geometry such as a field, court, track, floor plan, schematic, or other meaningful contextual surface",{"type":42,"tag":78,"props":99,"children":100},{},[101],{"type":47,"value":102},"an editorial story needs data-bound generated cutouts, illustrated substrates, scrollytelling\u002Fparallax states, or animated annotation reveals in SVG",{"type":42,"tag":78,"props":104,"children":105},{},[106],{"type":47,"value":107},"the mark count is moderate enough for DOM or SVG",{"type":42,"tag":78,"props":109,"children":110},{},[111],{"type":47,"value":112},"the interaction model needs zoom, brush, drag, or coordinated views",{"type":42,"tag":78,"props":114,"children":115},{},[116,118,125],{"type":47,"value":117},"a UML-like, dependency, architecture, state, or flow diagram needs bespoke SVG annotation or product-specific composition after ",{"type":42,"tag":119,"props":120,"children":122},"code",{"className":121},[],[123],{"type":47,"value":124},"..\u002Fuml-and-software-architecture-visualization\u002FSKILL.md",{"type":47,"value":126}," has defined the diagram semantics",{"type":42,"tag":78,"props":128,"children":129},{},[130],{"type":47,"value":131},"a declarative grammar would become harder to read than the resulting D3 code",{"type":42,"tag":50,"props":133,"children":135},{"id":134},"avoid-d3-first-dom-rendering-when",[136],{"type":47,"value":137},"Avoid D3-First DOM Rendering When",{"type":42,"tag":74,"props":139,"children":140},{},[141,146,151],{"type":42,"tag":78,"props":142,"children":143},{},[144],{"type":47,"value":145},"mark counts are so large that DOM throughput becomes the bottleneck",{"type":42,"tag":78,"props":147,"children":148},{},[149],{"type":47,"value":150},"animation is continuous and frame budgets are tight",{"type":42,"tag":78,"props":152,"children":153},{},[154],{"type":47,"value":155},"the task would be faster to solve with Canvas2D or WebGL",{"type":42,"tag":50,"props":157,"children":159},{"id":158},"working-pattern",[160],{"type":47,"value":161},"Working Pattern",{"type":42,"tag":163,"props":164,"children":165},"ol",{},[166,171,204,209,214,219,224,229,234,247],{"type":42,"tag":78,"props":167,"children":168},{},[169],{"type":47,"value":170},"Build a clean data model first.",{"type":42,"tag":78,"props":172,"children":173},{},[174,176],{"type":47,"value":175},"Separate:\n",{"type":42,"tag":74,"props":177,"children":178},{},[179,184,189,194,199],{"type":42,"tag":78,"props":180,"children":181},{},[182],{"type":47,"value":183},"parsing and normalization",{"type":42,"tag":78,"props":185,"children":186},{},[187],{"type":47,"value":188},"scale construction",{"type":42,"tag":78,"props":190,"children":191},{},[192],{"type":47,"value":193},"derived geometry",{"type":42,"tag":78,"props":195,"children":196},{},[197],{"type":47,"value":198},"rendering",{"type":42,"tag":78,"props":200,"children":201},{},[202],{"type":47,"value":203},"interaction state",{"type":42,"tag":78,"props":205,"children":206},{},[207],{"type":47,"value":208},"Prefer stable keys in joins.",{"type":42,"tag":78,"props":210,"children":211},{},[212],{"type":47,"value":213},"Use D3 for math and behavior, not for hiding weak state management.",{"type":42,"tag":78,"props":215,"children":216},{},[217],{"type":47,"value":218},"Assess how many D3 instances may coexist on the page so DOM, layout, and event costs are evaluated at dashboard scale.",{"type":42,"tag":78,"props":220,"children":221},{},[222],{"type":47,"value":223},"If using a contextual surface, keep source units and render scales explicit, draw the background as a separate layer, and adapt mark placement or layout forces to the domain geometry.",{"type":42,"tag":78,"props":225,"children":226},{},[227],{"type":47,"value":228},"For art-directed stories, keep generated image, substrate, data-mark, label, and annotation layers separate so each can be reviewed and exported.",{"type":42,"tag":78,"props":230,"children":231},{},[232],{"type":47,"value":233},"Keep annotations and interaction overlays explicit.",{"type":42,"tag":78,"props":235,"children":236},{},[237,239,245],{"type":47,"value":238},"For SVG output, apply ",{"type":42,"tag":119,"props":240,"children":242},{"className":241},[],[243],{"type":47,"value":244},".\u002Freferences\u002Fsvg-polish-and-crispness.md",{"type":47,"value":246}," before calling the chart finished. Explicitly set font sizes, tick padding, gridline strokes, data stroke widths, icon sizes, label alignment, and zoom-stable stroke behavior.",{"type":42,"tag":78,"props":248,"children":249},{},[250,252,258],{"type":47,"value":251},"For browser-facing work, use ",{"type":42,"tag":119,"props":253,"children":255},{"className":254},[],[256],{"type":47,"value":257},"..\u002F..\u002Freferences\u002Ffoundations\u002Fmobile-first-responsive-visualization.md",{"type":47,"value":259}," so the D3 layout is recomputed for large-screen and mobile states rather than scaled down from one desktop SVG.",{"type":42,"tag":50,"props":261,"children":263},{"id":262},"editorial-defaults",[264],{"type":47,"value":265},"Editorial Defaults",{"type":42,"tag":74,"props":267,"children":268},{},[269,274,279,284,289,302,315,327,332,337,342,347,360,365,370],{"type":42,"tag":78,"props":270,"children":271},{},[272],{"type":47,"value":273},"Build an explicit label layer. Direct end labels, inline keys, or panel labels should be considered before a detached legend.",{"type":42,"tag":78,"props":275,"children":276},{},[277],{"type":47,"value":278},"Build an explicit annotation layer. Callouts should attach to data points, ranges, thresholds, or domain geometry rather than floating as decoration.",{"type":42,"tag":78,"props":280,"children":281},{},[282],{"type":47,"value":283},"Keep gridlines, axes, and reference marks quiet. Most ink should be data, labels, or annotation.",{"type":42,"tag":78,"props":285,"children":286},{},[287],{"type":47,"value":288},"Default SVG chart polish: 10-12 px axis ticks, 11-13.5 px direct labels, 0.5-1 px non-data strokes, 1.5-2.25 px normal data lines, 2.5-3 px focus lines, short 4-6 px ticks, and no heavy chart border unless it carries meaning.",{"type":42,"tag":78,"props":290,"children":291},{},[292,294,300],{"type":47,"value":293},"Use D3 axes as geometry generators, then style them. Prefer ",{"type":42,"tag":119,"props":295,"children":297},{"className":296},[],[298],{"type":47,"value":299},".tickSizeOuter(0)",{"type":47,"value":301},", 6-8 px tick padding, quiet gridlines, removed domains when redundant, and fewer ticks before rotated or tiny labels.",{"type":42,"tag":78,"props":303,"children":304},{},[305,307,313],{"type":47,"value":306},"Use ",{"type":42,"tag":119,"props":308,"children":310},{"className":309},[],[311],{"type":47,"value":312},"shape-rendering: crispEdges",{"type":47,"value":314}," for straight axes, gridlines, and rectangular cells; do not apply it globally to curves, symbols, circles, or diagonal marks.",{"type":42,"tag":78,"props":316,"children":317},{},[318,319,325],{"type":47,"value":306},{"type":42,"tag":119,"props":320,"children":322},{"className":321},[],[323],{"type":47,"value":324},"vector-effect: non-scaling-stroke",{"type":47,"value":326}," for zoomable outlines, axes, annotation connectors, map borders, and icons that should keep screen-stable stroke weight.",{"type":42,"tag":78,"props":328,"children":329},{},[330],{"type":47,"value":331},"Use custom layout only when the story needs it; do not copy a publication's composition or visual identity.",{"type":42,"tag":78,"props":333,"children":334},{},[335],{"type":47,"value":336},"For narrow widths, provide either a simplified mark layout, small-multiple stack, or numbered annotation key below the chart.",{"type":42,"tag":78,"props":338,"children":339},{},[340],{"type":47,"value":341},"On mobile, make tap\u002Ffocus the inspection path, enlarge hit areas beyond visible marks, provide drag alternatives, define pinch or zoom ownership, and keep the main chart visible when filters or settings open.",{"type":42,"tag":78,"props":343,"children":344},{},[345],{"type":47,"value":346},"Favor inspectable SVG for editorial charts that need export, accessibility, and precise labels. Move dense mark fields to Canvas only when the DOM count justifies it.",{"type":42,"tag":78,"props":348,"children":349},{},[350,352,358],{"type":47,"value":351},"For scrollytelling or parallax, use ",{"type":42,"tag":119,"props":353,"children":355},{"className":354},[],[356],{"type":47,"value":357},"..\u002Fscrollytelling-and-parallax-data-visualization\u002FSKILL.md",{"type":47,"value":359}," for the scroll narrative, then let D3 own scales, derived geometry, data joins, labels, and SVG transitions. Keep each scene valid as a still.",{"type":42,"tag":78,"props":361,"children":362},{},[363],{"type":47,"value":364},"For generated imagery, use D3\u002FSVG for labels, anchors, masks, clipping, and data overlays rather than baking numbers into images.",{"type":42,"tag":78,"props":366,"children":367},{},[368],{"type":47,"value":369},"For motion, use transitions to reveal sequence, direction, accumulation, comparison, or mechanism. Respect reduced-motion with final-state rendering.",{"type":42,"tag":78,"props":371,"children":372},{},[373],{"type":47,"value":374},"For 3D-looking SVG, avoid perspective distortion unless it represents a real multiaxis surface; label axes and provide a flat fallback when needed.",{"type":42,"tag":50,"props":376,"children":378},{"id":377},"core-d3-building-blocks",[379],{"type":47,"value":380},"Core D3 Building Blocks",{"type":42,"tag":74,"props":382,"children":383},{},[384,395,406,417,428,447,474],{"type":42,"tag":78,"props":385,"children":386},{},[387,393],{"type":42,"tag":119,"props":388,"children":390},{"className":389},[],[391],{"type":47,"value":392},"d3-array",{"type":47,"value":394}," for grouping, extent, ticks, and summaries",{"type":42,"tag":78,"props":396,"children":397},{},[398,404],{"type":42,"tag":119,"props":399,"children":401},{"className":400},[],[402],{"type":47,"value":403},"d3-scale",{"type":47,"value":405}," for position, color, and size mappings",{"type":42,"tag":78,"props":407,"children":408},{},[409,415],{"type":42,"tag":119,"props":410,"children":412},{"className":411},[],[413],{"type":47,"value":414},"d3-axis",{"type":47,"value":416}," for readable axes",{"type":42,"tag":78,"props":418,"children":419},{},[420,426],{"type":42,"tag":119,"props":421,"children":423},{"className":422},[],[424],{"type":47,"value":425},"d3-shape",{"type":47,"value":427}," for lines, areas, arcs, and symbol generation",{"type":42,"tag":78,"props":429,"children":430},{},[431,437,439,445],{"type":42,"tag":119,"props":432,"children":434},{"className":433},[],[435],{"type":47,"value":436},"d3-selection",{"type":47,"value":438}," and ",{"type":42,"tag":119,"props":440,"children":442},{"className":441},[],[443],{"type":47,"value":444},"d3-transition",{"type":47,"value":446}," for DOM behavior",{"type":42,"tag":78,"props":448,"children":449},{},[450,456,458,464,466,472],{"type":42,"tag":119,"props":451,"children":453},{"className":452},[],[454],{"type":47,"value":455},"d3-brush",{"type":47,"value":457},", ",{"type":42,"tag":119,"props":459,"children":461},{"className":460},[],[462],{"type":47,"value":463},"d3-zoom",{"type":47,"value":465},", and ",{"type":42,"tag":119,"props":467,"children":469},{"className":468},[],[470],{"type":47,"value":471},"d3-drag",{"type":47,"value":473}," for direct manipulation",{"type":42,"tag":78,"props":475,"children":476},{},[477,483,484,490,491,497],{"type":42,"tag":119,"props":478,"children":480},{"className":479},[],[481],{"type":47,"value":482},"d3-force",{"type":47,"value":457},{"type":42,"tag":119,"props":485,"children":487},{"className":486},[],[488],{"type":47,"value":489},"d3-hierarchy",{"type":47,"value":457},{"type":42,"tag":119,"props":492,"children":494},{"className":493},[],[495],{"type":47,"value":496},"d3-contour",{"type":47,"value":498},", and other layouts only when their data structure fits",{"type":42,"tag":50,"props":500,"children":502},{"id":501},"integration-rules",[503],{"type":47,"value":504},"Integration Rules",{"type":42,"tag":74,"props":506,"children":507},{},[508,513,518,523,536,541,546],{"type":42,"tag":78,"props":509,"children":510},{},[511],{"type":47,"value":512},"In React or another UI framework, prefer framework-owned structure and D3-owned geometry, scales, and behaviors.",{"type":42,"tag":78,"props":514,"children":515},{},[516],{"type":47,"value":517},"For highly custom charts, a small imperative D3 island is fine if the boundary is clear.",{"type":42,"tag":78,"props":519,"children":520},{},[521],{"type":47,"value":522},"Keep responsive behavior tied to container measurements, not magic constants.",{"type":42,"tag":78,"props":524,"children":525},{},[526,528,534],{"type":47,"value":527},"Recompute labels, tick counts, annotation placement, collision rules, and plot height for mobile portrait and optional landscape sizes; do not only resize the outer ",{"type":42,"tag":119,"props":529,"children":531},{"className":530},[],[532],{"type":47,"value":533},"viewBox",{"type":47,"value":535},".",{"type":42,"tag":78,"props":537,"children":538},{},[539],{"type":47,"value":540},"Prefer SVG for labels and annotations even in hybrid systems.",{"type":42,"tag":78,"props":542,"children":543},{},[544],{"type":47,"value":545},"Keep contextual background layers non-interactive unless they are part of selection, zoom, or hit testing.",{"type":42,"tag":78,"props":547,"children":548},{},[549],{"type":47,"value":550},"Move to Canvas or WebGL when DOM count or continuous redraw becomes the limiting factor.",{"type":42,"tag":50,"props":552,"children":554},{"id":553},"output-expectations",[555],{"type":47,"value":556},"Output Expectations",{"type":42,"tag":74,"props":558,"children":559},{},[560,565,570,575,580,585,590,595,600],{"type":42,"tag":78,"props":561,"children":562},{},[563],{"type":47,"value":564},"Explain why D3 is the right rendering layer.",{"type":42,"tag":78,"props":566,"children":567},{},[568],{"type":47,"value":569},"Keep chart structure semantic and inspectable.",{"type":42,"tag":78,"props":571,"children":572},{},[573],{"type":47,"value":574},"Provide export paths for SVG or PNG when needed.",{"type":42,"tag":78,"props":576,"children":577},{},[578],{"type":47,"value":579},"Pair interaction with obvious annotation and reset controls.",{"type":42,"tag":78,"props":581,"children":582},{},[583],{"type":47,"value":584},"For mobile, state the touch target policy, hover replacement, drag\u002Fpinch ownership, and how the on-screen keyboard or settings panels return the user to the chart.",{"type":42,"tag":78,"props":586,"children":587},{},[588],{"type":47,"value":589},"When drawing a contextual surface, state the source geometry and how data marks are positioned, constrained, or biased by it.",{"type":42,"tag":78,"props":591,"children":592},{},[593],{"type":47,"value":594},"For image-supported editorial work, state which assets are generated, which layers remain data-bound, and how labels anchor to the substrate.",{"type":42,"tag":78,"props":596,"children":597},{},[598],{"type":47,"value":599},"For animation, state the verb, scene states, duration budget, and reduced-motion fallback.",{"type":42,"tag":78,"props":601,"children":602},{},[603],{"type":47,"value":604},"For new work, include a technical design section covering simultaneous instance count, DOM and interaction cost, and maintenance tradeoffs versus declarative or Canvas-based alternatives.",{"type":42,"tag":50,"props":606,"children":608},{"id":607},"references",[609],{"type":47,"value":610},"References",{"type":42,"tag":74,"props":612,"children":613},{},[614,684],{"type":42,"tag":78,"props":615,"children":616},{},[617,619],{"type":47,"value":618},"Shared theory:\n",{"type":42,"tag":74,"props":620,"children":621},{},[622,631,640,649,657,666,675],{"type":42,"tag":78,"props":623,"children":624},{},[625],{"type":42,"tag":119,"props":626,"children":628},{"className":627},[],[629],{"type":47,"value":630},"..\u002F..\u002Freferences\u002Ffoundations\u002Feditorial-infographic-system.md",{"type":42,"tag":78,"props":632,"children":633},{},[634],{"type":42,"tag":119,"props":635,"children":637},{"className":636},[],[638],{"type":47,"value":639},"..\u002F..\u002Freferences\u002Ffoundations\u002Fart-directed-interactive-visual-stories.md",{"type":42,"tag":78,"props":641,"children":642},{},[643],{"type":42,"tag":119,"props":644,"children":646},{"className":645},[],[647],{"type":47,"value":648},"..\u002F..\u002Freferences\u002Ffoundations\u002Fperception-color-and-encoding.md",{"type":42,"tag":78,"props":650,"children":651},{},[652],{"type":42,"tag":119,"props":653,"children":655},{"className":654},[],[656],{"type":47,"value":257},{"type":42,"tag":78,"props":658,"children":659},{},[660],{"type":42,"tag":119,"props":661,"children":663},{"className":662},[],[664],{"type":47,"value":665},"..\u002F..\u002Freferences\u002Ffoundations\u002Fdomain-contextual-surfaces.md",{"type":42,"tag":78,"props":667,"children":668},{},[669],{"type":42,"tag":119,"props":670,"children":672},{"className":671},[],[673],{"type":47,"value":674},"..\u002F..\u002Freferences\u002Ffoundations\u002Fstorytelling-annotation-and-critique.md",{"type":42,"tag":78,"props":676,"children":677},{},[678],{"type":42,"tag":119,"props":679,"children":681},{"className":680},[],[682],{"type":47,"value":683},"..\u002F..\u002Freferences\u002Ffoundations\u002Fimplementation-design-and-tradeoffs.md",{"type":42,"tag":78,"props":685,"children":686},{},[687,689],{"type":47,"value":688},"Skill references:\n",{"type":42,"tag":74,"props":690,"children":691},{},[692,701,710,719,728,736,744],{"type":42,"tag":78,"props":693,"children":694},{},[695],{"type":42,"tag":119,"props":696,"children":698},{"className":697},[],[699],{"type":47,"value":700},".\u002Freferences\u002Fd3-module-map.md",{"type":42,"tag":78,"props":702,"children":703},{},[704],{"type":42,"tag":119,"props":705,"children":707},{"className":706},[],[708],{"type":47,"value":709},".\u002Freferences\u002Fd3-architecture-patterns.md",{"type":42,"tag":78,"props":711,"children":712},{},[713],{"type":42,"tag":119,"props":714,"children":716},{"className":715},[],[717],{"type":47,"value":718},".\u002Freferences\u002Fd3-interaction-and-annotation.md",{"type":42,"tag":78,"props":720,"children":721},{},[722],{"type":42,"tag":119,"props":723,"children":725},{"className":724},[],[726],{"type":47,"value":727},".\u002Freferences\u002Fd3-pitfalls-and-scale-limits.md",{"type":42,"tag":78,"props":729,"children":730},{},[731],{"type":42,"tag":119,"props":732,"children":734},{"className":733},[],[735],{"type":47,"value":244},{"type":42,"tag":78,"props":737,"children":738},{},[739],{"type":42,"tag":119,"props":740,"children":742},{"className":741},[],[743],{"type":47,"value":124},{"type":42,"tag":78,"props":745,"children":746},{},[747],{"type":42,"tag":119,"props":748,"children":750},{"className":749},[],[751],{"type":47,"value":357},{"type":42,"tag":50,"props":753,"children":755},{"id":754},"representative-prompts",[756],{"type":47,"value":757},"Representative Prompts",{"type":42,"tag":74,"props":759,"children":760},{},[761,766,771,776,781,786,791],{"type":42,"tag":78,"props":762,"children":763},{},[764],{"type":47,"value":765},"\"Build a D3 slopegraph with direct labels.\"",{"type":42,"tag":78,"props":767,"children":768},{},[769],{"type":47,"value":770},"\"Add zoom and brushing to this scatterplot.\"",{"type":42,"tag":78,"props":772,"children":773},{},[774],{"type":47,"value":775},"\"Create a publication-quality SVG chart from this dataset.\"",{"type":42,"tag":78,"props":777,"children":778},{},[779],{"type":47,"value":780},"\"Draw a domain-accurate soccer pitch behind a player network and bias node positions by role.\"",{"type":42,"tag":78,"props":782,"children":783},{},[784],{"type":47,"value":785},"\"Refactor this D3 chart so React owns layout and D3 owns math.\"",{"type":42,"tag":78,"props":787,"children":788},{},[789],{"type":47,"value":790},"\"Animate this D3 chart through scrollytelling scene states.\"",{"type":42,"tag":78,"props":792,"children":793},{},[794],{"type":47,"value":795},"\"Tell me when this D3 chart should move to Canvas.\"",{"items":797,"total":1000},[798,819,842,859,875,894,913,927,943,957,969,984],{"slug":799,"name":799,"fn":800,"description":801,"org":802,"tags":803,"stars":816,"repoUrl":817,"updatedAt":818},"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},[804,807,810,813],{"name":805,"slug":806,"type":15},"Documents","documents",{"name":808,"slug":809,"type":15},"Healthcare","healthcare",{"name":811,"slug":812,"type":15},"Insurance","insurance",{"name":814,"slug":815,"type":15},"Regulatory Compliance","regulatory-compliance",28169,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fopenai-agents-python","2026-04-16T05:11:39.180399",{"slug":820,"name":820,"fn":821,"description":822,"org":823,"tags":824,"stars":839,"repoUrl":840,"updatedAt":841},"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},[825,828,830,833,836],{"name":826,"slug":827,"type":15},".NET","dotnet",{"name":829,"slug":820,"type":15},"ASP.NET Core",{"name":831,"slug":832,"type":15},"Blazor","blazor",{"name":834,"slug":835,"type":15},"C#","csharp",{"name":837,"slug":838,"type":15},"Web Development","web-development",23787,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fskills","2026-04-12T05:07:02.819491",{"slug":843,"name":843,"fn":844,"description":845,"org":846,"tags":847,"stars":839,"repoUrl":840,"updatedAt":858},"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},[848,851,854,857],{"name":849,"slug":850,"type":15},"Apps SDK","apps-sdk",{"name":852,"slug":853,"type":15},"ChatGPT","chatgpt",{"name":855,"slug":856,"type":15},"MCP","mcp",{"name":9,"slug":8,"type":15},"2026-04-12T05:07:05.468097",{"slug":860,"name":860,"fn":861,"description":862,"org":863,"tags":864,"stars":839,"repoUrl":840,"updatedAt":874},"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},[865,868,871],{"name":866,"slug":867,"type":15},"API Development","api-development",{"name":869,"slug":870,"type":15},"CLI","cli",{"name":872,"slug":873,"type":15},"Codex","codex","2026-04-12T05:07:04.132762",{"slug":876,"name":876,"fn":877,"description":878,"org":879,"tags":880,"stars":839,"repoUrl":840,"updatedAt":893},"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},[881,884,887,890],{"name":882,"slug":883,"type":15},"Cloudflare","cloudflare",{"name":885,"slug":886,"type":15},"Cloudflare Pages","cloudflare-pages",{"name":888,"slug":889,"type":15},"Cloudflare Workers","cloudflare-workers",{"name":891,"slug":892,"type":15},"Deployment","deployment","2026-04-12T05:07:14.275118",{"slug":895,"name":895,"fn":896,"description":897,"org":898,"tags":899,"stars":839,"repoUrl":840,"updatedAt":912},"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},[900,903,906,909],{"name":901,"slug":902,"type":15},"Productivity","productivity",{"name":904,"slug":905,"type":15},"Project Management","project-management",{"name":907,"slug":908,"type":15},"Strategy","strategy",{"name":910,"slug":911,"type":15},"Task Management","task-management","2026-05-23T06:17:16.870838",{"slug":914,"name":914,"fn":915,"description":916,"org":917,"tags":918,"stars":839,"repoUrl":840,"updatedAt":926},"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},[919,922,924,925],{"name":920,"slug":921,"type":15},"Design","design",{"name":923,"slug":914,"type":15},"Figma",{"name":23,"slug":24,"type":15},{"name":855,"slug":856,"type":15},"2026-04-12T05:06:47.939943",{"slug":928,"name":928,"fn":929,"description":930,"org":931,"tags":932,"stars":839,"repoUrl":840,"updatedAt":942},"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},[933,934,937,938,939],{"name":920,"slug":921,"type":15},{"name":935,"slug":936,"type":15},"Design System","design-system",{"name":923,"slug":914,"type":15},{"name":23,"slug":24,"type":15},{"name":940,"slug":941,"type":15},"UI Components","ui-components","2026-05-10T05:59:52.971881",{"slug":944,"name":944,"fn":945,"description":946,"org":947,"tags":948,"stars":839,"repoUrl":840,"updatedAt":956},"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},[949,950,951,954,955],{"name":920,"slug":921,"type":15},{"name":935,"slug":936,"type":15},{"name":952,"slug":953,"type":15},"Documentation","documentation",{"name":923,"slug":914,"type":15},{"name":23,"slug":24,"type":15},"2026-05-16T06:07:47.821474",{"slug":958,"name":958,"fn":959,"description":960,"org":961,"tags":962,"stars":839,"repoUrl":840,"updatedAt":968},"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},[963,964,965,966,967],{"name":920,"slug":921,"type":15},{"name":923,"slug":914,"type":15},{"name":23,"slug":24,"type":15},{"name":940,"slug":941,"type":15},{"name":837,"slug":838,"type":15},"2026-05-16T06:07:40.583615",{"slug":970,"name":970,"fn":971,"description":972,"org":973,"tags":974,"stars":839,"repoUrl":840,"updatedAt":983},"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},[975,978,979,982],{"name":976,"slug":977,"type":15},"Animation","animation",{"name":872,"slug":873,"type":15},{"name":980,"slug":981,"type":15},"Creative","creative",{"name":920,"slug":921,"type":15},"2026-05-02T05:31:48.48485",{"slug":985,"name":985,"fn":986,"description":987,"org":988,"tags":989,"stars":839,"repoUrl":840,"updatedAt":999},"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},[990,991,992,995,998],{"name":980,"slug":981,"type":15},{"name":920,"slug":921,"type":15},{"name":993,"slug":994,"type":15},"Image Generation","image-generation",{"name":996,"slug":997,"type":15},"Images","images",{"name":9,"slug":8,"type":15},"2026-05-15T06:23:24.312127",675,{"items":1002,"total":1111},[1003,1015,1031,1043,1061,1079,1099],{"slug":1004,"name":1004,"fn":1005,"description":1006,"org":1007,"tags":1008,"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},[1009,1012,1013,1014],{"name":1010,"slug":1011,"type":15},"Accessibility","accessibility",{"name":20,"slug":21,"type":15},{"name":13,"slug":14,"type":15},{"name":920,"slug":921,"type":15},{"slug":1016,"name":1016,"fn":1017,"description":1018,"org":1019,"tags":1020,"stars":25,"repoUrl":26,"updatedAt":1030},"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},[1021,1024,1027],{"name":1022,"slug":1023,"type":15},"Agents","agents",{"name":1025,"slug":1026,"type":15},"Browser Automation","browser-automation",{"name":1028,"slug":1029,"type":15},"Testing","testing","2026-04-06T18:41:03.44016",{"slug":1032,"name":1032,"fn":1033,"description":1034,"org":1035,"tags":1036,"stars":25,"repoUrl":26,"updatedAt":1042},"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},[1037,1038,1041],{"name":1025,"slug":1026,"type":15},{"name":1039,"slug":1040,"type":15},"Local Development","local-development",{"name":1028,"slug":1029,"type":15},"2026-04-06T18:41:17.526867",{"slug":1044,"name":1044,"fn":1045,"description":1046,"org":1047,"tags":1048,"stars":25,"repoUrl":26,"updatedAt":1060},"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},[1049,1050,1051,1054,1057],{"name":1022,"slug":1023,"type":15},{"name":888,"slug":889,"type":15},{"name":1052,"slug":1053,"type":15},"SDK","sdk",{"name":1055,"slug":1056,"type":15},"Serverless","serverless",{"name":1058,"slug":1059,"type":15},"WebSockets","websockets","2026-04-06T18:39:51.717063",{"slug":1062,"name":1062,"fn":1063,"description":1064,"org":1065,"tags":1066,"stars":25,"repoUrl":26,"updatedAt":1078},"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},[1067,1068,1071,1074,1075],{"name":23,"slug":24,"type":15},{"name":1069,"slug":1070,"type":15},"React","react",{"name":1072,"slug":1073,"type":15},"shadcn\u002Fui","shadcn-ui",{"name":940,"slug":941,"type":15},{"name":1076,"slug":1077,"type":15},"Vercel","vercel","2026-04-06T18:40:59.619419",{"slug":1080,"name":1080,"fn":1081,"description":1082,"org":1083,"tags":1084,"stars":25,"repoUrl":26,"updatedAt":1098},"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},[1085,1088,1091,1094,1097],{"name":1086,"slug":1087,"type":15},"AI Infrastructure","ai-infrastructure",{"name":1089,"slug":1090,"type":15},"Cost Optimization","cost-optimization",{"name":1092,"slug":1093,"type":15},"LLM","llm",{"name":1095,"slug":1096,"type":15},"Performance","performance",{"name":1076,"slug":1077,"type":15},"2026-04-06T18:40:44.377464",{"slug":1100,"name":1100,"fn":1101,"description":1102,"org":1103,"tags":1104,"stars":25,"repoUrl":26,"updatedAt":1110},"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},[1105,1106,1109],{"name":1089,"slug":1090,"type":15},{"name":1107,"slug":1108,"type":15},"Database","database",{"name":1092,"slug":1093,"type":15},"2026-04-06T18:41:08.513425",600]