[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-openai-three-webgl-game":3,"mdc-c707e3-key":36,"related-repo-openai-three-webgl-game":732,"related-org-openai-three-webgl-game":854},{"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},"three-webgl-game","implement browser games with Three.js","Implement browser-game runtimes with plain Three.js. Use when the user wants imperative scene control in TypeScript or Vite with GLB assets, loaders, physics, and low-level WebGL debugging.",{"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},"Game Development","game-development","tag",{"name":17,"slug":18,"type":15},"TypeScript","typescript",{"name":20,"slug":21,"type":15},"Engineering","engineering",{"name":23,"slug":24,"type":15},"Frontend","frontend",3992,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fplugins","2026-04-06T18:42:23.035358",null,465,[],{"repoUrl":26,"stars":25,"forks":29,"topics":32,"description":33},[],"OpenAI Plugins","https:\u002F\u002Fgithub.com\u002Fopenai\u002Fplugins\u002Ftree\u002FHEAD\u002Fplugins\u002Fgame-studio\u002Fskills\u002Fthree-webgl-game","---\nname: three-webgl-game\ndescription: Implement browser-game runtimes with plain Three.js. Use when the user wants imperative scene control in TypeScript or Vite with GLB assets, loaders, physics, and low-level WebGL debugging.\n---\n\n# Three WebGL Game\n\n## Overview\n\nUse this skill for the default non-React 3D path in the plugin. This is not generic WebGL advice. It is an opinionated stack for browser 3D work:\n\n- `three`\n- TypeScript\n- Vite\n- GLB or glTF 2.0 assets\n- Three.js loaders such as `GLTFLoader`, `DRACOLoader`, and `KTX2Loader`\n- Rapier JS for physics\n- SpectorJS for GPU and frame debugging\n- DOM overlays for HUD, menus, and settings\n\nUse this skill when the project wants direct scene, camera, renderer, and game-loop control. If the app already lives in React, route to `..\u002Freact-three-fiber-game\u002FSKILL.md` instead.\n\n## Use This Skill When\n\n- the app is plain TypeScript or Vite rather than React-first\n- the project wants direct imperative control over the render loop\n- the user asks for Three.js specifically\n- the runtime needs engine-like control over scene, camera, loaders, and physics\n\n## Do Not Use This Skill When\n\n- the 3D scene lives inside an existing React app\n- the main problem is shipped-asset optimization rather than runtime code\n- the user explicitly chose Babylon.js or PlayCanvas\n\n## Core Rules\n\n1. Keep simulation state outside Three.js objects.\n   - Game rules, AI, quest state, timers, and progression should not live inside meshes or materials.\n2. Treat the render graph as an adapter.\n   - Scene graph, cameras, materials, loaders, and post-processing are view concerns layered over simulation state.\n3. Keep camera behavior explicit.\n   - Orbit, follow, chase, rail, and first-person styles each need their own control boundary.\n4. Keep UI out of WebGL unless the presentation absolutely depends on it.\n   - Menus, HUD, inventories, and settings should default to DOM.\n5. Use GLB or glTF 2.0 as the default shipping model format.\n   - Do not build the runtime around DCC-native formats.\n6. Use Rapier instead of ad hoc collision code when the game has meaningful 3D physics or collision response.\n7. Keep the first playable view low-chrome.\n   - Default to one compact objective or status cluster plus transient prompts.\n   - Long notes, lore, and controls references should be collapsed until asked for.\n   - Do not frame the scene with multiple equal-weight cards during normal play.\n\n## Initial Scaffold UX\n\nFor exploration, traversal, and character-control prototypes, start with a sparse shell:\n\n- one edge-aligned objective chip\n- one transient controls hint\n- one optional compact status strip\n\nOnly add larger UI surfaces when the game loop truly requires them. Journal, quest log, codex, map, and settings surfaces should open on demand, not occupy the viewport by default.\n\n## Recommended Structure\n\nUse the module shape in `..\u002F..\u002Freferences\u002Fthree-webgl-architecture.md`, then keep these boundaries clean:\n\n- `simulation\u002F`: rules, progression, state, and AI\n- `render\u002Fapp\u002F`: renderer, scene, camera, resize, context lifecycle\n- `render\u002Floaders\u002F`: GLTF, Draco, KTX2, texture, and environment loading\n- `render\u002Fobjects\u002F`: mesh instantiation and disposal\n- `render\u002Fmaterials\u002F`: material setup and shader boundaries\n- `physics\u002F`: Rapier world, bodies, colliders, and simulation bridge\n- `ui\u002F`: DOM overlays and menus\n- `diagnostics\u002F`: debug toggles, perf probes, and capture hooks\n\n## Good Fit Scenarios\n\n- Exploration demos\n- Lightweight 3D combat prototypes\n- Vehicle or traversal prototypes\n- Scene-driven product or world showcases with gameplay\n- Material, lighting, or post-process-led experiences\n- 3D games where camera movement and depth readability are central\n\n## Loaders, Assets, and Post-Processing\n\n- Start with `GLTFLoader` for shipped 3D content.\n- Add `DRACOLoader` or Meshopt-compatible optimization as part of the asset pipeline, not as a random runtime patch.\n- Use `KTX2Loader` for compressed textures when the asset pipeline provides them.\n- Prefer built-in Three.js render and post-processing utilities first. Add heavier abstraction only when the project actually needs it.\n- Keep post-processing optional and measurable. Bloom and color effects should not hide gameplay readability.\n\n## Shader and Material Guidance\n\n- Start with standard Three.js materials and correct lighting before reaching for custom shaders.\n- Use custom shaders only when the visual target genuinely needs them.\n- Keep shader parameters driven by game state, not by incidental scene mutations.\n- If a material stack gets complex, isolate it behind material factories instead of scattering shader setup across scene code.\n\n## Browser Safety\n\n- Handle resize explicitly.\n- Expect WebGL context loss and recovery.\n- Keep a fallback or degraded mode in mind for fragile GPU paths.\n- Watch texture size, geometry count, draw-call growth, and post-processing cost.\n- Use SpectorJS when the scene behaves incorrectly or frame cost is unclear.\n\n## Scope Warning\n\nDo not claim that this plugin offers equal 3D depth to the Phaser track. It supports serious 3D implementation, but the plugin is still 2D-first overall.\n\n## References\n\n- Shared architecture: `..\u002Fweb-game-foundations\u002FSKILL.md`\n- Frontend direction: `..\u002Fgame-ui-frontend\u002FSKILL.md`\n- 3D HUD layout patterns: `..\u002F..\u002Freferences\u002Fthree-hud-layout-patterns.md`\n- Three.js ecosystem: `..\u002F..\u002Freferences\u002Fthreejs-stack.md`\n- Three.js structure: `..\u002F..\u002Freferences\u002Fthree-webgl-architecture.md`\n- Vanilla starter: `..\u002F..\u002Freferences\u002Fthreejs-vanilla-starter.md`\n- GLB loader starter: `..\u002F..\u002Freferences\u002Fgltf-loading-starter.md`\n- Rapier starter: `..\u002F..\u002Freferences\u002Frapier-integration-starter.md`\n- 3D asset pipeline: `..\u002F..\u002Freferences\u002Fweb-3d-asset-pipeline.md`\n- WebGL debugging and perf: `..\u002F..\u002Freferences\u002Fwebgl-debugging-and-performance.md`\n",{"data":37,"body":38},{"name":4,"description":6},{"type":39,"children":40},"root",[41,49,56,62,133,146,152,175,181,199,205,302,308,313,331,336,342,355,446,452,485,491,540,546,569,575,603,609,614,620],{"type":42,"tag":43,"props":44,"children":45},"element","h1",{"id":4},[46],{"type":47,"value":48},"text","Three WebGL Game",{"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 the default non-React 3D path in the plugin. This is not generic WebGL advice. It is an opinionated stack for browser 3D work:",{"type":42,"tag":63,"props":64,"children":65},"ul",{},[66,77,81,86,91,118,123,128],{"type":42,"tag":67,"props":68,"children":69},"li",{},[70],{"type":42,"tag":71,"props":72,"children":74},"code",{"className":73},[],[75],{"type":47,"value":76},"three",{"type":42,"tag":67,"props":78,"children":79},{},[80],{"type":47,"value":17},{"type":42,"tag":67,"props":82,"children":83},{},[84],{"type":47,"value":85},"Vite",{"type":42,"tag":67,"props":87,"children":88},{},[89],{"type":47,"value":90},"GLB or glTF 2.0 assets",{"type":42,"tag":67,"props":92,"children":93},{},[94,96,102,104,110,112],{"type":47,"value":95},"Three.js loaders such as ",{"type":42,"tag":71,"props":97,"children":99},{"className":98},[],[100],{"type":47,"value":101},"GLTFLoader",{"type":47,"value":103},", ",{"type":42,"tag":71,"props":105,"children":107},{"className":106},[],[108],{"type":47,"value":109},"DRACOLoader",{"type":47,"value":111},", and ",{"type":42,"tag":71,"props":113,"children":115},{"className":114},[],[116],{"type":47,"value":117},"KTX2Loader",{"type":42,"tag":67,"props":119,"children":120},{},[121],{"type":47,"value":122},"Rapier JS for physics",{"type":42,"tag":67,"props":124,"children":125},{},[126],{"type":47,"value":127},"SpectorJS for GPU and frame debugging",{"type":42,"tag":67,"props":129,"children":130},{},[131],{"type":47,"value":132},"DOM overlays for HUD, menus, and settings",{"type":42,"tag":57,"props":134,"children":135},{},[136,138,144],{"type":47,"value":137},"Use this skill when the project wants direct scene, camera, renderer, and game-loop control. If the app already lives in React, route to ",{"type":42,"tag":71,"props":139,"children":141},{"className":140},[],[142],{"type":47,"value":143},"..\u002Freact-three-fiber-game\u002FSKILL.md",{"type":47,"value":145}," instead.",{"type":42,"tag":50,"props":147,"children":149},{"id":148},"use-this-skill-when",[150],{"type":47,"value":151},"Use This Skill When",{"type":42,"tag":63,"props":153,"children":154},{},[155,160,165,170],{"type":42,"tag":67,"props":156,"children":157},{},[158],{"type":47,"value":159},"the app is plain TypeScript or Vite rather than React-first",{"type":42,"tag":67,"props":161,"children":162},{},[163],{"type":47,"value":164},"the project wants direct imperative control over the render loop",{"type":42,"tag":67,"props":166,"children":167},{},[168],{"type":47,"value":169},"the user asks for Three.js specifically",{"type":42,"tag":67,"props":171,"children":172},{},[173],{"type":47,"value":174},"the runtime needs engine-like control over scene, camera, loaders, and physics",{"type":42,"tag":50,"props":176,"children":178},{"id":177},"do-not-use-this-skill-when",[179],{"type":47,"value":180},"Do Not Use This Skill When",{"type":42,"tag":63,"props":182,"children":183},{},[184,189,194],{"type":42,"tag":67,"props":185,"children":186},{},[187],{"type":47,"value":188},"the 3D scene lives inside an existing React app",{"type":42,"tag":67,"props":190,"children":191},{},[192],{"type":47,"value":193},"the main problem is shipped-asset optimization rather than runtime code",{"type":42,"tag":67,"props":195,"children":196},{},[197],{"type":47,"value":198},"the user explicitly chose Babylon.js or PlayCanvas",{"type":42,"tag":50,"props":200,"children":202},{"id":201},"core-rules",[203],{"type":47,"value":204},"Core Rules",{"type":42,"tag":206,"props":207,"children":208},"ol",{},[209,222,235,248,261,274,279],{"type":42,"tag":67,"props":210,"children":211},{},[212,214],{"type":47,"value":213},"Keep simulation state outside Three.js objects.\n",{"type":42,"tag":63,"props":215,"children":216},{},[217],{"type":42,"tag":67,"props":218,"children":219},{},[220],{"type":47,"value":221},"Game rules, AI, quest state, timers, and progression should not live inside meshes or materials.",{"type":42,"tag":67,"props":223,"children":224},{},[225,227],{"type":47,"value":226},"Treat the render graph as an adapter.\n",{"type":42,"tag":63,"props":228,"children":229},{},[230],{"type":42,"tag":67,"props":231,"children":232},{},[233],{"type":47,"value":234},"Scene graph, cameras, materials, loaders, and post-processing are view concerns layered over simulation state.",{"type":42,"tag":67,"props":236,"children":237},{},[238,240],{"type":47,"value":239},"Keep camera behavior explicit.\n",{"type":42,"tag":63,"props":241,"children":242},{},[243],{"type":42,"tag":67,"props":244,"children":245},{},[246],{"type":47,"value":247},"Orbit, follow, chase, rail, and first-person styles each need their own control boundary.",{"type":42,"tag":67,"props":249,"children":250},{},[251,253],{"type":47,"value":252},"Keep UI out of WebGL unless the presentation absolutely depends on it.\n",{"type":42,"tag":63,"props":254,"children":255},{},[256],{"type":42,"tag":67,"props":257,"children":258},{},[259],{"type":47,"value":260},"Menus, HUD, inventories, and settings should default to DOM.",{"type":42,"tag":67,"props":262,"children":263},{},[264,266],{"type":47,"value":265},"Use GLB or glTF 2.0 as the default shipping model format.\n",{"type":42,"tag":63,"props":267,"children":268},{},[269],{"type":42,"tag":67,"props":270,"children":271},{},[272],{"type":47,"value":273},"Do not build the runtime around DCC-native formats.",{"type":42,"tag":67,"props":275,"children":276},{},[277],{"type":47,"value":278},"Use Rapier instead of ad hoc collision code when the game has meaningful 3D physics or collision response.",{"type":42,"tag":67,"props":280,"children":281},{},[282,284],{"type":47,"value":283},"Keep the first playable view low-chrome.\n",{"type":42,"tag":63,"props":285,"children":286},{},[287,292,297],{"type":42,"tag":67,"props":288,"children":289},{},[290],{"type":47,"value":291},"Default to one compact objective or status cluster plus transient prompts.",{"type":42,"tag":67,"props":293,"children":294},{},[295],{"type":47,"value":296},"Long notes, lore, and controls references should be collapsed until asked for.",{"type":42,"tag":67,"props":298,"children":299},{},[300],{"type":47,"value":301},"Do not frame the scene with multiple equal-weight cards during normal play.",{"type":42,"tag":50,"props":303,"children":305},{"id":304},"initial-scaffold-ux",[306],{"type":47,"value":307},"Initial Scaffold UX",{"type":42,"tag":57,"props":309,"children":310},{},[311],{"type":47,"value":312},"For exploration, traversal, and character-control prototypes, start with a sparse shell:",{"type":42,"tag":63,"props":314,"children":315},{},[316,321,326],{"type":42,"tag":67,"props":317,"children":318},{},[319],{"type":47,"value":320},"one edge-aligned objective chip",{"type":42,"tag":67,"props":322,"children":323},{},[324],{"type":47,"value":325},"one transient controls hint",{"type":42,"tag":67,"props":327,"children":328},{},[329],{"type":47,"value":330},"one optional compact status strip",{"type":42,"tag":57,"props":332,"children":333},{},[334],{"type":47,"value":335},"Only add larger UI surfaces when the game loop truly requires them. Journal, quest log, codex, map, and settings surfaces should open on demand, not occupy the viewport by default.",{"type":42,"tag":50,"props":337,"children":339},{"id":338},"recommended-structure",[340],{"type":47,"value":341},"Recommended Structure",{"type":42,"tag":57,"props":343,"children":344},{},[345,347,353],{"type":47,"value":346},"Use the module shape in ",{"type":42,"tag":71,"props":348,"children":350},{"className":349},[],[351],{"type":47,"value":352},"..\u002F..\u002Freferences\u002Fthree-webgl-architecture.md",{"type":47,"value":354},", then keep these boundaries clean:",{"type":42,"tag":63,"props":356,"children":357},{},[358,369,380,391,402,413,424,435],{"type":42,"tag":67,"props":359,"children":360},{},[361,367],{"type":42,"tag":71,"props":362,"children":364},{"className":363},[],[365],{"type":47,"value":366},"simulation\u002F",{"type":47,"value":368},": rules, progression, state, and AI",{"type":42,"tag":67,"props":370,"children":371},{},[372,378],{"type":42,"tag":71,"props":373,"children":375},{"className":374},[],[376],{"type":47,"value":377},"render\u002Fapp\u002F",{"type":47,"value":379},": renderer, scene, camera, resize, context lifecycle",{"type":42,"tag":67,"props":381,"children":382},{},[383,389],{"type":42,"tag":71,"props":384,"children":386},{"className":385},[],[387],{"type":47,"value":388},"render\u002Floaders\u002F",{"type":47,"value":390},": GLTF, Draco, KTX2, texture, and environment loading",{"type":42,"tag":67,"props":392,"children":393},{},[394,400],{"type":42,"tag":71,"props":395,"children":397},{"className":396},[],[398],{"type":47,"value":399},"render\u002Fobjects\u002F",{"type":47,"value":401},": mesh instantiation and disposal",{"type":42,"tag":67,"props":403,"children":404},{},[405,411],{"type":42,"tag":71,"props":406,"children":408},{"className":407},[],[409],{"type":47,"value":410},"render\u002Fmaterials\u002F",{"type":47,"value":412},": material setup and shader boundaries",{"type":42,"tag":67,"props":414,"children":415},{},[416,422],{"type":42,"tag":71,"props":417,"children":419},{"className":418},[],[420],{"type":47,"value":421},"physics\u002F",{"type":47,"value":423},": Rapier world, bodies, colliders, and simulation bridge",{"type":42,"tag":67,"props":425,"children":426},{},[427,433],{"type":42,"tag":71,"props":428,"children":430},{"className":429},[],[431],{"type":47,"value":432},"ui\u002F",{"type":47,"value":434},": DOM overlays and menus",{"type":42,"tag":67,"props":436,"children":437},{},[438,444],{"type":42,"tag":71,"props":439,"children":441},{"className":440},[],[442],{"type":47,"value":443},"diagnostics\u002F",{"type":47,"value":445},": debug toggles, perf probes, and capture hooks",{"type":42,"tag":50,"props":447,"children":449},{"id":448},"good-fit-scenarios",[450],{"type":47,"value":451},"Good Fit Scenarios",{"type":42,"tag":63,"props":453,"children":454},{},[455,460,465,470,475,480],{"type":42,"tag":67,"props":456,"children":457},{},[458],{"type":47,"value":459},"Exploration demos",{"type":42,"tag":67,"props":461,"children":462},{},[463],{"type":47,"value":464},"Lightweight 3D combat prototypes",{"type":42,"tag":67,"props":466,"children":467},{},[468],{"type":47,"value":469},"Vehicle or traversal prototypes",{"type":42,"tag":67,"props":471,"children":472},{},[473],{"type":47,"value":474},"Scene-driven product or world showcases with gameplay",{"type":42,"tag":67,"props":476,"children":477},{},[478],{"type":47,"value":479},"Material, lighting, or post-process-led experiences",{"type":42,"tag":67,"props":481,"children":482},{},[483],{"type":47,"value":484},"3D games where camera movement and depth readability are central",{"type":42,"tag":50,"props":486,"children":488},{"id":487},"loaders-assets-and-post-processing",[489],{"type":47,"value":490},"Loaders, Assets, and Post-Processing",{"type":42,"tag":63,"props":492,"children":493},{},[494,506,518,530,535],{"type":42,"tag":67,"props":495,"children":496},{},[497,499,504],{"type":47,"value":498},"Start with ",{"type":42,"tag":71,"props":500,"children":502},{"className":501},[],[503],{"type":47,"value":101},{"type":47,"value":505}," for shipped 3D content.",{"type":42,"tag":67,"props":507,"children":508},{},[509,511,516],{"type":47,"value":510},"Add ",{"type":42,"tag":71,"props":512,"children":514},{"className":513},[],[515],{"type":47,"value":109},{"type":47,"value":517}," or Meshopt-compatible optimization as part of the asset pipeline, not as a random runtime patch.",{"type":42,"tag":67,"props":519,"children":520},{},[521,523,528],{"type":47,"value":522},"Use ",{"type":42,"tag":71,"props":524,"children":526},{"className":525},[],[527],{"type":47,"value":117},{"type":47,"value":529}," for compressed textures when the asset pipeline provides them.",{"type":42,"tag":67,"props":531,"children":532},{},[533],{"type":47,"value":534},"Prefer built-in Three.js render and post-processing utilities first. Add heavier abstraction only when the project actually needs it.",{"type":42,"tag":67,"props":536,"children":537},{},[538],{"type":47,"value":539},"Keep post-processing optional and measurable. Bloom and color effects should not hide gameplay readability.",{"type":42,"tag":50,"props":541,"children":543},{"id":542},"shader-and-material-guidance",[544],{"type":47,"value":545},"Shader and Material Guidance",{"type":42,"tag":63,"props":547,"children":548},{},[549,554,559,564],{"type":42,"tag":67,"props":550,"children":551},{},[552],{"type":47,"value":553},"Start with standard Three.js materials and correct lighting before reaching for custom shaders.",{"type":42,"tag":67,"props":555,"children":556},{},[557],{"type":47,"value":558},"Use custom shaders only when the visual target genuinely needs them.",{"type":42,"tag":67,"props":560,"children":561},{},[562],{"type":47,"value":563},"Keep shader parameters driven by game state, not by incidental scene mutations.",{"type":42,"tag":67,"props":565,"children":566},{},[567],{"type":47,"value":568},"If a material stack gets complex, isolate it behind material factories instead of scattering shader setup across scene code.",{"type":42,"tag":50,"props":570,"children":572},{"id":571},"browser-safety",[573],{"type":47,"value":574},"Browser Safety",{"type":42,"tag":63,"props":576,"children":577},{},[578,583,588,593,598],{"type":42,"tag":67,"props":579,"children":580},{},[581],{"type":47,"value":582},"Handle resize explicitly.",{"type":42,"tag":67,"props":584,"children":585},{},[586],{"type":47,"value":587},"Expect WebGL context loss and recovery.",{"type":42,"tag":67,"props":589,"children":590},{},[591],{"type":47,"value":592},"Keep a fallback or degraded mode in mind for fragile GPU paths.",{"type":42,"tag":67,"props":594,"children":595},{},[596],{"type":47,"value":597},"Watch texture size, geometry count, draw-call growth, and post-processing cost.",{"type":42,"tag":67,"props":599,"children":600},{},[601],{"type":47,"value":602},"Use SpectorJS when the scene behaves incorrectly or frame cost is unclear.",{"type":42,"tag":50,"props":604,"children":606},{"id":605},"scope-warning",[607],{"type":47,"value":608},"Scope Warning",{"type":42,"tag":57,"props":610,"children":611},{},[612],{"type":47,"value":613},"Do not claim that this plugin offers equal 3D depth to the Phaser track. It supports serious 3D implementation, but the plugin is still 2D-first overall.",{"type":42,"tag":50,"props":615,"children":617},{"id":616},"references",[618],{"type":47,"value":619},"References",{"type":42,"tag":63,"props":621,"children":622},{},[623,634,645,656,667,677,688,699,710,721],{"type":42,"tag":67,"props":624,"children":625},{},[626,628],{"type":47,"value":627},"Shared architecture: ",{"type":42,"tag":71,"props":629,"children":631},{"className":630},[],[632],{"type":47,"value":633},"..\u002Fweb-game-foundations\u002FSKILL.md",{"type":42,"tag":67,"props":635,"children":636},{},[637,639],{"type":47,"value":638},"Frontend direction: ",{"type":42,"tag":71,"props":640,"children":642},{"className":641},[],[643],{"type":47,"value":644},"..\u002Fgame-ui-frontend\u002FSKILL.md",{"type":42,"tag":67,"props":646,"children":647},{},[648,650],{"type":47,"value":649},"3D HUD layout patterns: ",{"type":42,"tag":71,"props":651,"children":653},{"className":652},[],[654],{"type":47,"value":655},"..\u002F..\u002Freferences\u002Fthree-hud-layout-patterns.md",{"type":42,"tag":67,"props":657,"children":658},{},[659,661],{"type":47,"value":660},"Three.js ecosystem: ",{"type":42,"tag":71,"props":662,"children":664},{"className":663},[],[665],{"type":47,"value":666},"..\u002F..\u002Freferences\u002Fthreejs-stack.md",{"type":42,"tag":67,"props":668,"children":669},{},[670,672],{"type":47,"value":671},"Three.js structure: ",{"type":42,"tag":71,"props":673,"children":675},{"className":674},[],[676],{"type":47,"value":352},{"type":42,"tag":67,"props":678,"children":679},{},[680,682],{"type":47,"value":681},"Vanilla starter: ",{"type":42,"tag":71,"props":683,"children":685},{"className":684},[],[686],{"type":47,"value":687},"..\u002F..\u002Freferences\u002Fthreejs-vanilla-starter.md",{"type":42,"tag":67,"props":689,"children":690},{},[691,693],{"type":47,"value":692},"GLB loader starter: ",{"type":42,"tag":71,"props":694,"children":696},{"className":695},[],[697],{"type":47,"value":698},"..\u002F..\u002Freferences\u002Fgltf-loading-starter.md",{"type":42,"tag":67,"props":700,"children":701},{},[702,704],{"type":47,"value":703},"Rapier starter: ",{"type":42,"tag":71,"props":705,"children":707},{"className":706},[],[708],{"type":47,"value":709},"..\u002F..\u002Freferences\u002Frapier-integration-starter.md",{"type":42,"tag":67,"props":711,"children":712},{},[713,715],{"type":47,"value":714},"3D asset pipeline: ",{"type":42,"tag":71,"props":716,"children":718},{"className":717},[],[719],{"type":47,"value":720},"..\u002F..\u002Freferences\u002Fweb-3d-asset-pipeline.md",{"type":42,"tag":67,"props":722,"children":723},{},[724,726],{"type":47,"value":725},"WebGL debugging and perf: ",{"type":42,"tag":71,"props":727,"children":729},{"className":728},[],[730],{"type":47,"value":731},"..\u002F..\u002Freferences\u002Fwebgl-debugging-and-performance.md",{"items":733,"total":853},[734,753,769,781,801,821,841],{"slug":735,"name":735,"fn":736,"description":737,"org":738,"tags":739,"stars":25,"repoUrl":26,"updatedAt":752},"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},[740,743,746,749],{"name":741,"slug":742,"type":15},"Accessibility","accessibility",{"name":744,"slug":745,"type":15},"Charts","charts",{"name":747,"slug":748,"type":15},"Data Visualization","data-visualization",{"name":750,"slug":751,"type":15},"Design","design","2026-06-30T19:00:57.102",{"slug":754,"name":754,"fn":755,"description":756,"org":757,"tags":758,"stars":25,"repoUrl":26,"updatedAt":768},"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},[759,762,765],{"name":760,"slug":761,"type":15},"Agents","agents",{"name":763,"slug":764,"type":15},"Browser Automation","browser-automation",{"name":766,"slug":767,"type":15},"Testing","testing","2026-04-06T18:41:03.44016",{"slug":770,"name":770,"fn":771,"description":772,"org":773,"tags":774,"stars":25,"repoUrl":26,"updatedAt":780},"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},[775,776,779],{"name":763,"slug":764,"type":15},{"name":777,"slug":778,"type":15},"Local Development","local-development",{"name":766,"slug":767,"type":15},"2026-04-06T18:41:17.526867",{"slug":782,"name":782,"fn":783,"description":784,"org":785,"tags":786,"stars":25,"repoUrl":26,"updatedAt":800},"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},[787,788,791,794,797],{"name":760,"slug":761,"type":15},{"name":789,"slug":790,"type":15},"Cloudflare Workers","cloudflare-workers",{"name":792,"slug":793,"type":15},"SDK","sdk",{"name":795,"slug":796,"type":15},"Serverless","serverless",{"name":798,"slug":799,"type":15},"WebSockets","websockets","2026-04-06T18:39:51.717063",{"slug":802,"name":802,"fn":803,"description":804,"org":805,"tags":806,"stars":25,"repoUrl":26,"updatedAt":820},"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},[807,808,811,814,817],{"name":23,"slug":24,"type":15},{"name":809,"slug":810,"type":15},"React","react",{"name":812,"slug":813,"type":15},"shadcn\u002Fui","shadcn-ui",{"name":815,"slug":816,"type":15},"UI Components","ui-components",{"name":818,"slug":819,"type":15},"Vercel","vercel","2026-04-06T18:40:59.619419",{"slug":822,"name":822,"fn":823,"description":824,"org":825,"tags":826,"stars":25,"repoUrl":26,"updatedAt":840},"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},[827,830,833,836,839],{"name":828,"slug":829,"type":15},"AI Infrastructure","ai-infrastructure",{"name":831,"slug":832,"type":15},"Cost Optimization","cost-optimization",{"name":834,"slug":835,"type":15},"LLM","llm",{"name":837,"slug":838,"type":15},"Performance","performance",{"name":818,"slug":819,"type":15},"2026-04-06T18:40:44.377464",{"slug":842,"name":842,"fn":843,"description":844,"org":845,"tags":846,"stars":25,"repoUrl":26,"updatedAt":852},"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},[847,848,851],{"name":831,"slug":832,"type":15},{"name":849,"slug":850,"type":15},"Database","database",{"name":834,"slug":835,"type":15},"2026-04-06T18:41:08.513425",600,{"items":855,"total":1052},[856,877,900,917,933,950,969,981,995,1009,1021,1036],{"slug":857,"name":857,"fn":858,"description":859,"org":860,"tags":861,"stars":874,"repoUrl":875,"updatedAt":876},"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},[862,865,868,871],{"name":863,"slug":864,"type":15},"Documents","documents",{"name":866,"slug":867,"type":15},"Healthcare","healthcare",{"name":869,"slug":870,"type":15},"Insurance","insurance",{"name":872,"slug":873,"type":15},"Regulatory Compliance","regulatory-compliance",28169,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fopenai-agents-python","2026-04-16T05:11:39.180399",{"slug":878,"name":878,"fn":879,"description":880,"org":881,"tags":882,"stars":897,"repoUrl":898,"updatedAt":899},"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},[883,886,888,891,894],{"name":884,"slug":885,"type":15},".NET","dotnet",{"name":887,"slug":878,"type":15},"ASP.NET Core",{"name":889,"slug":890,"type":15},"Blazor","blazor",{"name":892,"slug":893,"type":15},"C#","csharp",{"name":895,"slug":896,"type":15},"Web Development","web-development",23787,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fskills","2026-04-12T05:07:02.819491",{"slug":901,"name":901,"fn":902,"description":903,"org":904,"tags":905,"stars":897,"repoUrl":898,"updatedAt":916},"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},[906,909,912,915],{"name":907,"slug":908,"type":15},"Apps SDK","apps-sdk",{"name":910,"slug":911,"type":15},"ChatGPT","chatgpt",{"name":913,"slug":914,"type":15},"MCP","mcp",{"name":9,"slug":8,"type":15},"2026-04-12T05:07:05.468097",{"slug":918,"name":918,"fn":919,"description":920,"org":921,"tags":922,"stars":897,"repoUrl":898,"updatedAt":932},"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},[923,926,929],{"name":924,"slug":925,"type":15},"API Development","api-development",{"name":927,"slug":928,"type":15},"CLI","cli",{"name":930,"slug":931,"type":15},"Codex","codex","2026-04-12T05:07:04.132762",{"slug":934,"name":934,"fn":935,"description":936,"org":937,"tags":938,"stars":897,"repoUrl":898,"updatedAt":949},"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},[939,942,945,946],{"name":940,"slug":941,"type":15},"Cloudflare","cloudflare",{"name":943,"slug":944,"type":15},"Cloudflare Pages","cloudflare-pages",{"name":789,"slug":790,"type":15},{"name":947,"slug":948,"type":15},"Deployment","deployment","2026-04-12T05:07:14.275118",{"slug":951,"name":951,"fn":952,"description":953,"org":954,"tags":955,"stars":897,"repoUrl":898,"updatedAt":968},"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},[956,959,962,965],{"name":957,"slug":958,"type":15},"Productivity","productivity",{"name":960,"slug":961,"type":15},"Project Management","project-management",{"name":963,"slug":964,"type":15},"Strategy","strategy",{"name":966,"slug":967,"type":15},"Task Management","task-management","2026-05-23T06:17:16.870838",{"slug":970,"name":970,"fn":971,"description":972,"org":973,"tags":974,"stars":897,"repoUrl":898,"updatedAt":980},"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},[975,976,978,979],{"name":750,"slug":751,"type":15},{"name":977,"slug":970,"type":15},"Figma",{"name":23,"slug":24,"type":15},{"name":913,"slug":914,"type":15},"2026-04-12T05:06:47.939943",{"slug":982,"name":982,"fn":983,"description":984,"org":985,"tags":986,"stars":897,"repoUrl":898,"updatedAt":994},"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},[987,988,991,992,993],{"name":750,"slug":751,"type":15},{"name":989,"slug":990,"type":15},"Design System","design-system",{"name":977,"slug":970,"type":15},{"name":23,"slug":24,"type":15},{"name":815,"slug":816,"type":15},"2026-05-10T05:59:52.971881",{"slug":996,"name":996,"fn":997,"description":998,"org":999,"tags":1000,"stars":897,"repoUrl":898,"updatedAt":1008},"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},[1001,1002,1003,1006,1007],{"name":750,"slug":751,"type":15},{"name":989,"slug":990,"type":15},{"name":1004,"slug":1005,"type":15},"Documentation","documentation",{"name":977,"slug":970,"type":15},{"name":23,"slug":24,"type":15},"2026-05-16T06:07:47.821474",{"slug":1010,"name":1010,"fn":1011,"description":1012,"org":1013,"tags":1014,"stars":897,"repoUrl":898,"updatedAt":1020},"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},[1015,1016,1017,1018,1019],{"name":750,"slug":751,"type":15},{"name":977,"slug":970,"type":15},{"name":23,"slug":24,"type":15},{"name":815,"slug":816,"type":15},{"name":895,"slug":896,"type":15},"2026-05-16T06:07:40.583615",{"slug":1022,"name":1022,"fn":1023,"description":1024,"org":1025,"tags":1026,"stars":897,"repoUrl":898,"updatedAt":1035},"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},[1027,1030,1031,1034],{"name":1028,"slug":1029,"type":15},"Animation","animation",{"name":930,"slug":931,"type":15},{"name":1032,"slug":1033,"type":15},"Creative","creative",{"name":750,"slug":751,"type":15},"2026-05-02T05:31:48.48485",{"slug":1037,"name":1037,"fn":1038,"description":1039,"org":1040,"tags":1041,"stars":897,"repoUrl":898,"updatedAt":1051},"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},[1042,1043,1044,1047,1050],{"name":1032,"slug":1033,"type":15},{"name":750,"slug":751,"type":15},{"name":1045,"slug":1046,"type":15},"Image Generation","image-generation",{"name":1048,"slug":1049,"type":15},"Images","images",{"name":9,"slug":8,"type":15},"2026-05-15T06:23:24.312127",675]