[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-openai-scrollytelling-and-parallax-data-visualization":3,"mdc-kchcfz-key":36,"related-repo-openai-scrollytelling-and-parallax-data-visualization":685,"related-org-openai-scrollytelling-and-parallax-data-visualization":804},{"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},"scrollytelling-and-parallax-data-visualization","design parallax scrollytelling data visualizations","Design and implement parallax scrolling and scrollytelling data visualizations. Use when the user asks for parallax scrolling, scrollytelling, scroll-driven timelines, sticky graphics, Scrollama, ScrollTrigger, ScrollTimeline, view timelines, rich-media timelines, moviescrollers, scroll-scrubbed charts, staged narrative reveals, or interactive visual stories where scrolling changes a data visualization or media scene.",{"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},"Animation","animation",{"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\u002Fscrollytelling-and-parallax-data-visualization","---\nname: scrollytelling-and-parallax-data-visualization\ndescription: Design and implement parallax scrolling and scrollytelling data visualizations. Use when the user asks for parallax scrolling, scrollytelling, scroll-driven timelines, sticky graphics, Scrollama, ScrollTrigger, ScrollTimeline, view timelines, rich-media timelines, moviescrollers, scroll-scrubbed charts, staged narrative reveals, or interactive visual stories where scrolling changes a data visualization or media scene.\n---\n\n# Scrollytelling and Parallax Data Visualization\n\n## Overview\n\nUse this skill when scrolling is part of the explanation, not just navigation. Scrollytelling is an author-led narrative structure in which text, data marks, imagery, video, maps, or camera states change as the reader scrolls. Parallax is one possible scrollytelling technique: layers move at different rates to create depth, reveal scale, or connect foreground evidence to background context.\n\nDefault assumption: preserve native scrolling and make every scene meaningful as a still. Do not use parallax or scroll-scrubbed motion as decoration. Use it only when staged reveal, state change, elapsed time, spatial movement, or rich-media synchronization materially reduces interpretation cost.\n\n## When To Use It\n\n- A timeline, map, chart, 3D scene, video, or illustrated substrate needs staged reveal while the reader scrolls.\n- The story benefits from a linear author-led path before optional reader exploration.\n- A sticky graphic, side-by-side text\u002Fvisual layout, overlay text on media, or scroll-scrubbed transition is being planned or implemented.\n- The user mentions Scrollama, GSAP ScrollTrigger, Motion `useScroll`, CSS `ScrollTimeline`, ViewTimeline, IntersectionObserver, `position: sticky`, parallax layers, moviescroller, or scroll-driven animation.\n\nAvoid scrollytelling when the story is clearer as a static chart, direct-label small multiples, a conventional article with inline figures, or an explicit stepper. Prefer a stepper when the states are discrete and the reader needs direct access, known length, replay, or controlled comparison more than continuous scroll.\n\n## Working Pattern\n\n1. Define the story contract:\n   - one-sentence takeaway\n   - author-led sequence and any reader-controlled exploration\n   - why scrolling is necessary\n   - what the first frame, each key frame, and final frame prove\n2. For fictional, synthetic, or illustrative stories, require a data-rich simulation before storyboarding. Use `..\u002F..\u002Freferences\u002Ffoundations\u002Ffictional-data-story-simulation.md` to define entity, temporal, spatial or physical, event, outcome, and derived comparison layers.\n3. For art-directed, image-supported, composite, or existing-page scrollytelling work, use `..\u002F..\u002Freferences\u002Ffoundations\u002Fmeaning-preserving-visual-design-workflow.md` and `..\u002F..\u002Freferences\u002Ffoundations\u002Fmobile-first-responsive-visualization.md`. Apply those shared references for Codex concept generation, large-screen\u002Fmobile variants, approval or iteration, scene contracts, and implementation deferral.\n4. Choose the scrollytelling technique:\n   - graphic sequence\n   - animated transition\n   - pan and zoom\n   - moviescroller\n   - show-and-play\n   - parallax depth layer\n   - sticky side-by-side or overlay\n   - stacked mobile fallback or mobile-specific stepper\n5. Model scenes as data, not ad hoc scroll math. Each scene declares text, visual state, data layer, media asset, annotation, scroll trigger or progress range, reduced-motion fallback, static key frame, embedded visualization skill owner, visual-density role, interactive discovery affordance, asset-continuity requirement, scroll-controlled media behavior, and any approved concept\u002Fkey-frame contract. Approved key-frame concepts are binding scene contracts: the implementation must preserve their evidence hierarchy, staging, label-safe regions, interaction meaning, and static fallback unless a deviation is approved or recorded as meaning-preserving.\n6. For each embedded visual layer, use `..\u002F..\u002Freferences\u002Ffoundations\u002Fembedded-visualization-self-use.md` to name the primary specialist owner and mini-brief the layer's job, data shape, encoding, interaction, fallback, accessibility, QA check, and delegated or local fresh-pass status before scene composition.\n7. Require every scene to include at least one evidence-bearing visual change: chart transition, map or layer reveal, annotation shift, camera move, particle or flow state, video frame or state, or interactive hotspot. If the scene only adds drama, simplify or add real evidence.\n8. Pick the lightest implementation:\n   - native scroll and `position: sticky` for pinning\n   - IntersectionObserver or Scrollama for step triggers\n   - CSS scroll-driven animations for simple transform or opacity when support and fallback are acceptable\n   - Motion or GSAP ScrollTrigger for complex React choreography, scrubbing, pinning, snapping, or timeline labels\n   - D3\u002FSVG, Canvas2D, WebGL, deck.gl, PixiJS, Three.js, or video only when the visual layer requires it\n9. Protect the browser contract:\n   - do not scrolljack\n   - keep feedback immediate, reversible, and interruptible\n   - preserve standard wheel, touch, scrollbar, and keyboard behavior\n   - avoid surprise autoplay, especially audio\n   - account for mobile browser chrome, changing viewport height, touch momentum, and keyboard-open states\n10. Build accessibility and fallbacks before polish:\n   - honor `prefers-reduced-motion`\n   - provide static key frames, a stacked version, or a stepped fallback\n   - keep focus order and reading order coherent\n   - ensure the main claim survives screenshots and static export\n11. Test performance and interpretation:\n   - profile scroll jank on desktop and mobile\n   - verify no layout thrashing or layout-triggering animation\n   - reserve media dimensions and lazy-load offscreen assets\n   - test fast scroll, reverse scroll, resize, reduced motion, keyboard navigation, and mobile browser chrome changes\n\n## Routing\n\n- Use `..\u002Fvisualization-strategy-and-critique\u002FSKILL.md` first when deciding whether the story should be scrollytelling, a stepper, small multiples, or a static editorial chart.\n- Use `..\u002Freact-and-nextjs-data-visualization\u002FSKILL.md` when the implementation is a React or Next.js story surface, especially with hydration, client-only libraries, dynamic imports, or route-level asset loading.\n- Use `..\u002Fd3-data-visualization\u002FSKILL.md` when SVG data marks, labels, annotations, and scene-state transitions are the core work.\n- Use `..\u002Fcanvas2d-data-visualization\u002FSKILL.md` when dense flat marks or custom hit testing make SVG too heavy.\n- Use `..\u002Fthreejs-data-visualization\u002FSKILL.md` when WebGL, GPU layers, particles, flow, or camera-led 3D are necessary.\n- Use `..\u002Fgeospatial-and-cartographic-visualization\u002FSKILL.md` for map scrollytelling, fly-to sequences, route stories, or pan\u002Fzoom geography.\n- Use `..\u002Faccessibility-and-inclusive-visualization\u002FSKILL.md` when motion sensitivity, keyboard path, screen-reader alternatives, or static fallbacks are central.\n- Use `..\u002Ftesting-data-visualizations\u002FSKILL.md` when validating scroll states, visual regression, render readiness, media loading, or reduced-motion behavior.\n- Use `..\u002F..\u002Freferences\u002Ffoundations\u002Ffictional-data-story-simulation.md` when sparse invented data would otherwise force the scroll story to rely on walls of text, decorative parallax, or generic chart tiles.\n\n## Output Expectations\n\n- State whether scrollytelling is justified and what would be lost in a simpler format.\n- Name the scrollytelling technique and the reader's path through scenes.\n- Provide a scene contract with trigger\u002Fprogress ranges and static fallbacks.\n- For Codex image-generated layout or key-frame concepts, use the shared design workflow for concept images, approval status, approved references, binding semantic design contract, locked and flexible elements, data-bound layers, mobile\u002Flandscape continuation, approved deviations, and concept-to-result fidelity checks.\n- For every embedded visual layer, provide the specialist owner, mini-brief summary, QA check, and whether delegated fresh context, a local fresh specialist pass, or a lightweight exception was used.\n- For fictional stories, provide the simulated-world data richness contract and the specialist mini-brief for every embedded visualization layer.\n- Name the implementation stack and why it is the lightest reliable option.\n- Call out browser behavior explicitly: native scroll, sticky pinning, event listeners, scroll ownership, and keyboard behavior.\n- State reduced-motion behavior, mobile portrait path, optional landscape path, media loading plan, spotty-connection behavior, and performance risks.\n- Include the first-frame, key-frame, final-frame, and screenshot acceptance criteria.\n\n## References\n\n- `.\u002Freferences\u002Fstory-patterns-and-scene-contracts.md`\n- `.\u002Freferences\u002Fimplementation-and-performance.md`\n- `.\u002Freferences\u002Faccessibility-testing-and-review.md`\n- `..\u002F..\u002Freferences\u002Ffoundations\u002Fmeaning-preserving-visual-design-workflow.md`\n- `..\u002F..\u002Freferences\u002Ffoundations\u002Fembedded-visualization-self-use.md`\n- `..\u002F..\u002Freferences\u002Ffoundations\u002Fmobile-first-responsive-visualization.md`\n\n## Representative Prompts\n\n- \"Make a parallax scrolling timeline with maps and video.\"\n- \"Use Scrollama for a data story.\"\n- \"Should this be scrollytelling or a stepper?\"\n- \"Design a scroll-driven visualization that is accessible and performant.\"\n- \"Build a sticky graphic story where the chart changes as the reader scrolls.\"\n- \"Storyboard a moviescroller that advances video frames with scroll progress.\"\n",{"data":37,"body":38},{"name":4,"description":6},{"type":39,"children":40},"root",[41,49,56,62,67,73,123,128,134,349,378,387,410,416,527,533,586,592,646,652],{"type":42,"tag":43,"props":44,"children":45},"element","h1",{"id":4},[46],{"type":47,"value":48},"text","Scrollytelling and Parallax 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 when scrolling is part of the explanation, not just navigation. Scrollytelling is an author-led narrative structure in which text, data marks, imagery, video, maps, or camera states change as the reader scrolls. Parallax is one possible scrollytelling technique: layers move at different rates to create depth, reveal scale, or connect foreground evidence to background context.",{"type":42,"tag":57,"props":63,"children":64},{},[65],{"type":47,"value":66},"Default assumption: preserve native scrolling and make every scene meaningful as a still. Do not use parallax or scroll-scrubbed motion as decoration. Use it only when staged reveal, state change, elapsed time, spatial movement, or rich-media synchronization materially reduces interpretation cost.",{"type":42,"tag":50,"props":68,"children":70},{"id":69},"when-to-use-it",[71],{"type":47,"value":72},"When To Use It",{"type":42,"tag":74,"props":75,"children":76},"ul",{},[77,83,88,93],{"type":42,"tag":78,"props":79,"children":80},"li",{},[81],{"type":47,"value":82},"A timeline, map, chart, 3D scene, video, or illustrated substrate needs staged reveal while the reader scrolls.",{"type":42,"tag":78,"props":84,"children":85},{},[86],{"type":47,"value":87},"The story benefits from a linear author-led path before optional reader exploration.",{"type":42,"tag":78,"props":89,"children":90},{},[91],{"type":47,"value":92},"A sticky graphic, side-by-side text\u002Fvisual layout, overlay text on media, or scroll-scrubbed transition is being planned or implemented.",{"type":42,"tag":78,"props":94,"children":95},{},[96,98,105,107,113,115,121],{"type":47,"value":97},"The user mentions Scrollama, GSAP ScrollTrigger, Motion ",{"type":42,"tag":99,"props":100,"children":102},"code",{"className":101},[],[103],{"type":47,"value":104},"useScroll",{"type":47,"value":106},", CSS ",{"type":42,"tag":99,"props":108,"children":110},{"className":109},[],[111],{"type":47,"value":112},"ScrollTimeline",{"type":47,"value":114},", ViewTimeline, IntersectionObserver, ",{"type":42,"tag":99,"props":116,"children":118},{"className":117},[],[119],{"type":47,"value":120},"position: sticky",{"type":47,"value":122},", parallax layers, moviescroller, or scroll-driven animation.",{"type":42,"tag":57,"props":124,"children":125},{},[126],{"type":47,"value":127},"Avoid scrollytelling when the story is clearer as a static chart, direct-label small multiples, a conventional article with inline figures, or an explicit stepper. Prefer a stepper when the states are discrete and the reader needs direct access, known length, replay, or controlled comparison more than continuous scroll.",{"type":42,"tag":50,"props":129,"children":131},{"id":130},"working-pattern",[132],{"type":47,"value":133},"Working Pattern",{"type":42,"tag":135,"props":136,"children":137},"ol",{},[138,166,179,200,248,253,266,271,311,344],{"type":42,"tag":78,"props":139,"children":140},{},[141,143],{"type":47,"value":142},"Define the story contract:\n",{"type":42,"tag":74,"props":144,"children":145},{},[146,151,156,161],{"type":42,"tag":78,"props":147,"children":148},{},[149],{"type":47,"value":150},"one-sentence takeaway",{"type":42,"tag":78,"props":152,"children":153},{},[154],{"type":47,"value":155},"author-led sequence and any reader-controlled exploration",{"type":42,"tag":78,"props":157,"children":158},{},[159],{"type":47,"value":160},"why scrolling is necessary",{"type":42,"tag":78,"props":162,"children":163},{},[164],{"type":47,"value":165},"what the first frame, each key frame, and final frame prove",{"type":42,"tag":78,"props":167,"children":168},{},[169,171,177],{"type":47,"value":170},"For fictional, synthetic, or illustrative stories, require a data-rich simulation before storyboarding. Use ",{"type":42,"tag":99,"props":172,"children":174},{"className":173},[],[175],{"type":47,"value":176},"..\u002F..\u002Freferences\u002Ffoundations\u002Ffictional-data-story-simulation.md",{"type":47,"value":178}," to define entity, temporal, spatial or physical, event, outcome, and derived comparison layers.",{"type":42,"tag":78,"props":180,"children":181},{},[182,184,190,192,198],{"type":47,"value":183},"For art-directed, image-supported, composite, or existing-page scrollytelling work, use ",{"type":42,"tag":99,"props":185,"children":187},{"className":186},[],[188],{"type":47,"value":189},"..\u002F..\u002Freferences\u002Ffoundations\u002Fmeaning-preserving-visual-design-workflow.md",{"type":47,"value":191}," and ",{"type":42,"tag":99,"props":193,"children":195},{"className":194},[],[196],{"type":47,"value":197},"..\u002F..\u002Freferences\u002Ffoundations\u002Fmobile-first-responsive-visualization.md",{"type":47,"value":199},". Apply those shared references for Codex concept generation, large-screen\u002Fmobile variants, approval or iteration, scene contracts, and implementation deferral.",{"type":42,"tag":78,"props":201,"children":202},{},[203,205],{"type":47,"value":204},"Choose the scrollytelling technique:\n",{"type":42,"tag":74,"props":206,"children":207},{},[208,213,218,223,228,233,238,243],{"type":42,"tag":78,"props":209,"children":210},{},[211],{"type":47,"value":212},"graphic sequence",{"type":42,"tag":78,"props":214,"children":215},{},[216],{"type":47,"value":217},"animated transition",{"type":42,"tag":78,"props":219,"children":220},{},[221],{"type":47,"value":222},"pan and zoom",{"type":42,"tag":78,"props":224,"children":225},{},[226],{"type":47,"value":227},"moviescroller",{"type":42,"tag":78,"props":229,"children":230},{},[231],{"type":47,"value":232},"show-and-play",{"type":42,"tag":78,"props":234,"children":235},{},[236],{"type":47,"value":237},"parallax depth layer",{"type":42,"tag":78,"props":239,"children":240},{},[241],{"type":47,"value":242},"sticky side-by-side or overlay",{"type":42,"tag":78,"props":244,"children":245},{},[246],{"type":47,"value":247},"stacked mobile fallback or mobile-specific stepper",{"type":42,"tag":78,"props":249,"children":250},{},[251],{"type":47,"value":252},"Model scenes as data, not ad hoc scroll math. Each scene declares text, visual state, data layer, media asset, annotation, scroll trigger or progress range, reduced-motion fallback, static key frame, embedded visualization skill owner, visual-density role, interactive discovery affordance, asset-continuity requirement, scroll-controlled media behavior, and any approved concept\u002Fkey-frame contract. Approved key-frame concepts are binding scene contracts: the implementation must preserve their evidence hierarchy, staging, label-safe regions, interaction meaning, and static fallback unless a deviation is approved or recorded as meaning-preserving.",{"type":42,"tag":78,"props":254,"children":255},{},[256,258,264],{"type":47,"value":257},"For each embedded visual layer, use ",{"type":42,"tag":99,"props":259,"children":261},{"className":260},[],[262],{"type":47,"value":263},"..\u002F..\u002Freferences\u002Ffoundations\u002Fembedded-visualization-self-use.md",{"type":47,"value":265}," to name the primary specialist owner and mini-brief the layer's job, data shape, encoding, interaction, fallback, accessibility, QA check, and delegated or local fresh-pass status before scene composition.",{"type":42,"tag":78,"props":267,"children":268},{},[269],{"type":47,"value":270},"Require every scene to include at least one evidence-bearing visual change: chart transition, map or layer reveal, annotation shift, camera move, particle or flow state, video frame or state, or interactive hotspot. If the scene only adds drama, simplify or add real evidence.",{"type":42,"tag":78,"props":272,"children":273},{},[274,276],{"type":47,"value":275},"Pick the lightest implementation:\n",{"type":42,"tag":74,"props":277,"children":278},{},[279,291,296,301,306],{"type":42,"tag":78,"props":280,"children":281},{},[282,284,289],{"type":47,"value":283},"native scroll and ",{"type":42,"tag":99,"props":285,"children":287},{"className":286},[],[288],{"type":47,"value":120},{"type":47,"value":290}," for pinning",{"type":42,"tag":78,"props":292,"children":293},{},[294],{"type":47,"value":295},"IntersectionObserver or Scrollama for step triggers",{"type":42,"tag":78,"props":297,"children":298},{},[299],{"type":47,"value":300},"CSS scroll-driven animations for simple transform or opacity when support and fallback are acceptable",{"type":42,"tag":78,"props":302,"children":303},{},[304],{"type":47,"value":305},"Motion or GSAP ScrollTrigger for complex React choreography, scrubbing, pinning, snapping, or timeline labels",{"type":42,"tag":78,"props":307,"children":308},{},[309],{"type":47,"value":310},"D3\u002FSVG, Canvas2D, WebGL, deck.gl, PixiJS, Three.js, or video only when the visual layer requires it",{"type":42,"tag":78,"props":312,"children":313},{},[314,316],{"type":47,"value":315},"Protect the browser contract:\n",{"type":42,"tag":74,"props":317,"children":318},{},[319,324,329,334,339],{"type":42,"tag":78,"props":320,"children":321},{},[322],{"type":47,"value":323},"do not scrolljack",{"type":42,"tag":78,"props":325,"children":326},{},[327],{"type":47,"value":328},"keep feedback immediate, reversible, and interruptible",{"type":42,"tag":78,"props":330,"children":331},{},[332],{"type":47,"value":333},"preserve standard wheel, touch, scrollbar, and keyboard behavior",{"type":42,"tag":78,"props":335,"children":336},{},[337],{"type":47,"value":338},"avoid surprise autoplay, especially audio",{"type":42,"tag":78,"props":340,"children":341},{},[342],{"type":47,"value":343},"account for mobile browser chrome, changing viewport height, touch momentum, and keyboard-open states",{"type":42,"tag":78,"props":345,"children":346},{},[347],{"type":47,"value":348},"Build accessibility and fallbacks before polish:",{"type":42,"tag":74,"props":350,"children":351},{},[352,363,368,373],{"type":42,"tag":78,"props":353,"children":354},{},[355,357],{"type":47,"value":356},"honor ",{"type":42,"tag":99,"props":358,"children":360},{"className":359},[],[361],{"type":47,"value":362},"prefers-reduced-motion",{"type":42,"tag":78,"props":364,"children":365},{},[366],{"type":47,"value":367},"provide static key frames, a stacked version, or a stepped fallback",{"type":42,"tag":78,"props":369,"children":370},{},[371],{"type":47,"value":372},"keep focus order and reading order coherent",{"type":42,"tag":78,"props":374,"children":375},{},[376],{"type":47,"value":377},"ensure the main claim survives screenshots and static export",{"type":42,"tag":135,"props":379,"children":381},{"start":380},11,[382],{"type":42,"tag":78,"props":383,"children":384},{},[385],{"type":47,"value":386},"Test performance and interpretation:",{"type":42,"tag":74,"props":388,"children":389},{},[390,395,400,405],{"type":42,"tag":78,"props":391,"children":392},{},[393],{"type":47,"value":394},"profile scroll jank on desktop and mobile",{"type":42,"tag":78,"props":396,"children":397},{},[398],{"type":47,"value":399},"verify no layout thrashing or layout-triggering animation",{"type":42,"tag":78,"props":401,"children":402},{},[403],{"type":47,"value":404},"reserve media dimensions and lazy-load offscreen assets",{"type":42,"tag":78,"props":406,"children":407},{},[408],{"type":47,"value":409},"test fast scroll, reverse scroll, resize, reduced motion, keyboard navigation, and mobile browser chrome changes",{"type":42,"tag":50,"props":411,"children":413},{"id":412},"routing",[414],{"type":47,"value":415},"Routing",{"type":42,"tag":74,"props":417,"children":418},{},[419,432,444,456,468,480,492,504,516],{"type":42,"tag":78,"props":420,"children":421},{},[422,424,430],{"type":47,"value":423},"Use ",{"type":42,"tag":99,"props":425,"children":427},{"className":426},[],[428],{"type":47,"value":429},"..\u002Fvisualization-strategy-and-critique\u002FSKILL.md",{"type":47,"value":431}," first when deciding whether the story should be scrollytelling, a stepper, small multiples, or a static editorial chart.",{"type":42,"tag":78,"props":433,"children":434},{},[435,436,442],{"type":47,"value":423},{"type":42,"tag":99,"props":437,"children":439},{"className":438},[],[440],{"type":47,"value":441},"..\u002Freact-and-nextjs-data-visualization\u002FSKILL.md",{"type":47,"value":443}," when the implementation is a React or Next.js story surface, especially with hydration, client-only libraries, dynamic imports, or route-level asset loading.",{"type":42,"tag":78,"props":445,"children":446},{},[447,448,454],{"type":47,"value":423},{"type":42,"tag":99,"props":449,"children":451},{"className":450},[],[452],{"type":47,"value":453},"..\u002Fd3-data-visualization\u002FSKILL.md",{"type":47,"value":455}," when SVG data marks, labels, annotations, and scene-state transitions are the core work.",{"type":42,"tag":78,"props":457,"children":458},{},[459,460,466],{"type":47,"value":423},{"type":42,"tag":99,"props":461,"children":463},{"className":462},[],[464],{"type":47,"value":465},"..\u002Fcanvas2d-data-visualization\u002FSKILL.md",{"type":47,"value":467}," when dense flat marks or custom hit testing make SVG too heavy.",{"type":42,"tag":78,"props":469,"children":470},{},[471,472,478],{"type":47,"value":423},{"type":42,"tag":99,"props":473,"children":475},{"className":474},[],[476],{"type":47,"value":477},"..\u002Fthreejs-data-visualization\u002FSKILL.md",{"type":47,"value":479}," when WebGL, GPU layers, particles, flow, or camera-led 3D are necessary.",{"type":42,"tag":78,"props":481,"children":482},{},[483,484,490],{"type":47,"value":423},{"type":42,"tag":99,"props":485,"children":487},{"className":486},[],[488],{"type":47,"value":489},"..\u002Fgeospatial-and-cartographic-visualization\u002FSKILL.md",{"type":47,"value":491}," for map scrollytelling, fly-to sequences, route stories, or pan\u002Fzoom geography.",{"type":42,"tag":78,"props":493,"children":494},{},[495,496,502],{"type":47,"value":423},{"type":42,"tag":99,"props":497,"children":499},{"className":498},[],[500],{"type":47,"value":501},"..\u002Faccessibility-and-inclusive-visualization\u002FSKILL.md",{"type":47,"value":503}," when motion sensitivity, keyboard path, screen-reader alternatives, or static fallbacks are central.",{"type":42,"tag":78,"props":505,"children":506},{},[507,508,514],{"type":47,"value":423},{"type":42,"tag":99,"props":509,"children":511},{"className":510},[],[512],{"type":47,"value":513},"..\u002Ftesting-data-visualizations\u002FSKILL.md",{"type":47,"value":515}," when validating scroll states, visual regression, render readiness, media loading, or reduced-motion behavior.",{"type":42,"tag":78,"props":517,"children":518},{},[519,520,525],{"type":47,"value":423},{"type":42,"tag":99,"props":521,"children":523},{"className":522},[],[524],{"type":47,"value":176},{"type":47,"value":526}," when sparse invented data would otherwise force the scroll story to rely on walls of text, decorative parallax, or generic chart tiles.",{"type":42,"tag":50,"props":528,"children":530},{"id":529},"output-expectations",[531],{"type":47,"value":532},"Output Expectations",{"type":42,"tag":74,"props":534,"children":535},{},[536,541,546,551,556,561,566,571,576,581],{"type":42,"tag":78,"props":537,"children":538},{},[539],{"type":47,"value":540},"State whether scrollytelling is justified and what would be lost in a simpler format.",{"type":42,"tag":78,"props":542,"children":543},{},[544],{"type":47,"value":545},"Name the scrollytelling technique and the reader's path through scenes.",{"type":42,"tag":78,"props":547,"children":548},{},[549],{"type":47,"value":550},"Provide a scene contract with trigger\u002Fprogress ranges and static fallbacks.",{"type":42,"tag":78,"props":552,"children":553},{},[554],{"type":47,"value":555},"For Codex image-generated layout or key-frame concepts, use the shared design workflow for concept images, approval status, approved references, binding semantic design contract, locked and flexible elements, data-bound layers, mobile\u002Flandscape continuation, approved deviations, and concept-to-result fidelity checks.",{"type":42,"tag":78,"props":557,"children":558},{},[559],{"type":47,"value":560},"For every embedded visual layer, provide the specialist owner, mini-brief summary, QA check, and whether delegated fresh context, a local fresh specialist pass, or a lightweight exception was used.",{"type":42,"tag":78,"props":562,"children":563},{},[564],{"type":47,"value":565},"For fictional stories, provide the simulated-world data richness contract and the specialist mini-brief for every embedded visualization layer.",{"type":42,"tag":78,"props":567,"children":568},{},[569],{"type":47,"value":570},"Name the implementation stack and why it is the lightest reliable option.",{"type":42,"tag":78,"props":572,"children":573},{},[574],{"type":47,"value":575},"Call out browser behavior explicitly: native scroll, sticky pinning, event listeners, scroll ownership, and keyboard behavior.",{"type":42,"tag":78,"props":577,"children":578},{},[579],{"type":47,"value":580},"State reduced-motion behavior, mobile portrait path, optional landscape path, media loading plan, spotty-connection behavior, and performance risks.",{"type":42,"tag":78,"props":582,"children":583},{},[584],{"type":47,"value":585},"Include the first-frame, key-frame, final-frame, and screenshot acceptance criteria.",{"type":42,"tag":50,"props":587,"children":589},{"id":588},"references",[590],{"type":47,"value":591},"References",{"type":42,"tag":74,"props":593,"children":594},{},[595,604,613,622,630,638],{"type":42,"tag":78,"props":596,"children":597},{},[598],{"type":42,"tag":99,"props":599,"children":601},{"className":600},[],[602],{"type":47,"value":603},".\u002Freferences\u002Fstory-patterns-and-scene-contracts.md",{"type":42,"tag":78,"props":605,"children":606},{},[607],{"type":42,"tag":99,"props":608,"children":610},{"className":609},[],[611],{"type":47,"value":612},".\u002Freferences\u002Fimplementation-and-performance.md",{"type":42,"tag":78,"props":614,"children":615},{},[616],{"type":42,"tag":99,"props":617,"children":619},{"className":618},[],[620],{"type":47,"value":621},".\u002Freferences\u002Faccessibility-testing-and-review.md",{"type":42,"tag":78,"props":623,"children":624},{},[625],{"type":42,"tag":99,"props":626,"children":628},{"className":627},[],[629],{"type":47,"value":189},{"type":42,"tag":78,"props":631,"children":632},{},[633],{"type":42,"tag":99,"props":634,"children":636},{"className":635},[],[637],{"type":47,"value":263},{"type":42,"tag":78,"props":639,"children":640},{},[641],{"type":42,"tag":99,"props":642,"children":644},{"className":643},[],[645],{"type":47,"value":197},{"type":42,"tag":50,"props":647,"children":649},{"id":648},"representative-prompts",[650],{"type":47,"value":651},"Representative Prompts",{"type":42,"tag":74,"props":653,"children":654},{},[655,660,665,670,675,680],{"type":42,"tag":78,"props":656,"children":657},{},[658],{"type":47,"value":659},"\"Make a parallax scrolling timeline with maps and video.\"",{"type":42,"tag":78,"props":661,"children":662},{},[663],{"type":47,"value":664},"\"Use Scrollama for a data story.\"",{"type":42,"tag":78,"props":666,"children":667},{},[668],{"type":47,"value":669},"\"Should this be scrollytelling or a stepper?\"",{"type":42,"tag":78,"props":671,"children":672},{},[673],{"type":47,"value":674},"\"Design a scroll-driven visualization that is accessible and performant.\"",{"type":42,"tag":78,"props":676,"children":677},{},[678],{"type":47,"value":679},"\"Build a sticky graphic story where the chart changes as the reader scrolls.\"",{"type":42,"tag":78,"props":681,"children":682},{},[683],{"type":47,"value":684},"\"Storyboard a moviescroller that advances video frames with scroll progress.\"",{"items":686,"total":803},[687,703,719,731,751,771,791],{"slug":688,"name":688,"fn":689,"description":690,"org":691,"tags":692,"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},[693,696,699,700],{"name":694,"slug":695,"type":15},"Accessibility","accessibility",{"name":697,"slug":698,"type":15},"Charts","charts",{"name":13,"slug":14,"type":15},{"name":701,"slug":702,"type":15},"Design","design",{"slug":704,"name":704,"fn":705,"description":706,"org":707,"tags":708,"stars":25,"repoUrl":26,"updatedAt":718},"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},[709,712,715],{"name":710,"slug":711,"type":15},"Agents","agents",{"name":713,"slug":714,"type":15},"Browser Automation","browser-automation",{"name":716,"slug":717,"type":15},"Testing","testing","2026-04-06T18:41:03.44016",{"slug":720,"name":720,"fn":721,"description":722,"org":723,"tags":724,"stars":25,"repoUrl":26,"updatedAt":730},"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},[725,726,729],{"name":713,"slug":714,"type":15},{"name":727,"slug":728,"type":15},"Local Development","local-development",{"name":716,"slug":717,"type":15},"2026-04-06T18:41:17.526867",{"slug":732,"name":732,"fn":733,"description":734,"org":735,"tags":736,"stars":25,"repoUrl":26,"updatedAt":750},"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},[737,738,741,744,747],{"name":710,"slug":711,"type":15},{"name":739,"slug":740,"type":15},"Cloudflare Workers","cloudflare-workers",{"name":742,"slug":743,"type":15},"SDK","sdk",{"name":745,"slug":746,"type":15},"Serverless","serverless",{"name":748,"slug":749,"type":15},"WebSockets","websockets","2026-04-06T18:39:51.717063",{"slug":752,"name":752,"fn":753,"description":754,"org":755,"tags":756,"stars":25,"repoUrl":26,"updatedAt":770},"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},[757,758,761,764,767],{"name":23,"slug":24,"type":15},{"name":759,"slug":760,"type":15},"React","react",{"name":762,"slug":763,"type":15},"shadcn\u002Fui","shadcn-ui",{"name":765,"slug":766,"type":15},"UI Components","ui-components",{"name":768,"slug":769,"type":15},"Vercel","vercel","2026-04-06T18:40:59.619419",{"slug":772,"name":772,"fn":773,"description":774,"org":775,"tags":776,"stars":25,"repoUrl":26,"updatedAt":790},"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},[777,780,783,786,789],{"name":778,"slug":779,"type":15},"AI Infrastructure","ai-infrastructure",{"name":781,"slug":782,"type":15},"Cost Optimization","cost-optimization",{"name":784,"slug":785,"type":15},"LLM","llm",{"name":787,"slug":788,"type":15},"Performance","performance",{"name":768,"slug":769,"type":15},"2026-04-06T18:40:44.377464",{"slug":792,"name":792,"fn":793,"description":794,"org":795,"tags":796,"stars":25,"repoUrl":26,"updatedAt":802},"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},[797,798,801],{"name":781,"slug":782,"type":15},{"name":799,"slug":800,"type":15},"Database","database",{"name":784,"slug":785,"type":15},"2026-04-06T18:41:08.513425",600,{"items":805,"total":1000},[806,827,850,867,883,900,919,931,945,959,971,984],{"slug":807,"name":807,"fn":808,"description":809,"org":810,"tags":811,"stars":824,"repoUrl":825,"updatedAt":826},"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},[812,815,818,821],{"name":813,"slug":814,"type":15},"Documents","documents",{"name":816,"slug":817,"type":15},"Healthcare","healthcare",{"name":819,"slug":820,"type":15},"Insurance","insurance",{"name":822,"slug":823,"type":15},"Regulatory Compliance","regulatory-compliance",28169,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fopenai-agents-python","2026-04-16T05:11:39.180399",{"slug":828,"name":828,"fn":829,"description":830,"org":831,"tags":832,"stars":847,"repoUrl":848,"updatedAt":849},"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},[833,836,838,841,844],{"name":834,"slug":835,"type":15},".NET","dotnet",{"name":837,"slug":828,"type":15},"ASP.NET Core",{"name":839,"slug":840,"type":15},"Blazor","blazor",{"name":842,"slug":843,"type":15},"C#","csharp",{"name":845,"slug":846,"type":15},"Web Development","web-development",23787,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fskills","2026-04-12T05:07:02.819491",{"slug":851,"name":851,"fn":852,"description":853,"org":854,"tags":855,"stars":847,"repoUrl":848,"updatedAt":866},"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},[856,859,862,865],{"name":857,"slug":858,"type":15},"Apps SDK","apps-sdk",{"name":860,"slug":861,"type":15},"ChatGPT","chatgpt",{"name":863,"slug":864,"type":15},"MCP","mcp",{"name":9,"slug":8,"type":15},"2026-04-12T05:07:05.468097",{"slug":868,"name":868,"fn":869,"description":870,"org":871,"tags":872,"stars":847,"repoUrl":848,"updatedAt":882},"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},[873,876,879],{"name":874,"slug":875,"type":15},"API Development","api-development",{"name":877,"slug":878,"type":15},"CLI","cli",{"name":880,"slug":881,"type":15},"Codex","codex","2026-04-12T05:07:04.132762",{"slug":884,"name":884,"fn":885,"description":886,"org":887,"tags":888,"stars":847,"repoUrl":848,"updatedAt":899},"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},[889,892,895,896],{"name":890,"slug":891,"type":15},"Cloudflare","cloudflare",{"name":893,"slug":894,"type":15},"Cloudflare Pages","cloudflare-pages",{"name":739,"slug":740,"type":15},{"name":897,"slug":898,"type":15},"Deployment","deployment","2026-04-12T05:07:14.275118",{"slug":901,"name":901,"fn":902,"description":903,"org":904,"tags":905,"stars":847,"repoUrl":848,"updatedAt":918},"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},[906,909,912,915],{"name":907,"slug":908,"type":15},"Productivity","productivity",{"name":910,"slug":911,"type":15},"Project Management","project-management",{"name":913,"slug":914,"type":15},"Strategy","strategy",{"name":916,"slug":917,"type":15},"Task Management","task-management","2026-05-23T06:17:16.870838",{"slug":920,"name":920,"fn":921,"description":922,"org":923,"tags":924,"stars":847,"repoUrl":848,"updatedAt":930},"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},[925,926,928,929],{"name":701,"slug":702,"type":15},{"name":927,"slug":920,"type":15},"Figma",{"name":23,"slug":24,"type":15},{"name":863,"slug":864,"type":15},"2026-04-12T05:06:47.939943",{"slug":932,"name":932,"fn":933,"description":934,"org":935,"tags":936,"stars":847,"repoUrl":848,"updatedAt":944},"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},[937,938,941,942,943],{"name":701,"slug":702,"type":15},{"name":939,"slug":940,"type":15},"Design System","design-system",{"name":927,"slug":920,"type":15},{"name":23,"slug":24,"type":15},{"name":765,"slug":766,"type":15},"2026-05-10T05:59:52.971881",{"slug":946,"name":946,"fn":947,"description":948,"org":949,"tags":950,"stars":847,"repoUrl":848,"updatedAt":958},"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},[951,952,953,956,957],{"name":701,"slug":702,"type":15},{"name":939,"slug":940,"type":15},{"name":954,"slug":955,"type":15},"Documentation","documentation",{"name":927,"slug":920,"type":15},{"name":23,"slug":24,"type":15},"2026-05-16T06:07:47.821474",{"slug":960,"name":960,"fn":961,"description":962,"org":963,"tags":964,"stars":847,"repoUrl":848,"updatedAt":970},"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},[965,966,967,968,969],{"name":701,"slug":702,"type":15},{"name":927,"slug":920,"type":15},{"name":23,"slug":24,"type":15},{"name":765,"slug":766,"type":15},{"name":845,"slug":846,"type":15},"2026-05-16T06:07:40.583615",{"slug":972,"name":972,"fn":973,"description":974,"org":975,"tags":976,"stars":847,"repoUrl":848,"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},[977,978,979,982],{"name":20,"slug":21,"type":15},{"name":880,"slug":881,"type":15},{"name":980,"slug":981,"type":15},"Creative","creative",{"name":701,"slug":702,"type":15},"2026-05-02T05:31:48.48485",{"slug":985,"name":985,"fn":986,"description":987,"org":988,"tags":989,"stars":847,"repoUrl":848,"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":701,"slug":702,"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]