[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79FD5T7F74S7QJMSQ3ZKQ8M":3,"skill-same:01M79FD5T7F74S7QJMSQ3ZKQ8M":51},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M79FD5T7F74S7QJMSQ3ZKQ8M","react-three-fiber-game",null,"Build React-hosted 3D browser games with React Three Fiber. Use when the user wants pmndrs-based scene composition, shared React state, and 3D HUD integration inside a React app.","zfifteen\u002Fskills-catalog","zfifteen","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F221906715?v=4","01M79CQFXDZM5J5CJTCECPFA66","Dionisio Alberto Lopez III","01M79CQFY4C62PN8A2T5KDAHGA",1,"MIT","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Freact-three-fiber-game\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: react-three-fiber-game\ndescription: Build React-hosted 3D browser games with React Three Fiber. Use when the user wants pmndrs-based scene composition, shared React state, and 3D HUD integration inside a React app.\n---\n\n# React Three Fiber Game\n\n## Overview\n\nUse this skill when the 3D runtime lives inside a React application. This is the default React-native 3D path in the plugin and should be preferred over vanilla Three.js when the app shell, settings, storefront, editor surface, or surrounding product already uses React.\n\nRecommended stack:\n\n- `@react-three\u002Ffiber`\n- `three`\n- `@react-three\u002Fdrei`\n- `@react-three\u002Frapier`\n- `@react-three\u002Fpostprocessing`\n- `@react-three\u002Fa11y` when accessibility-sensitive interaction matters\n- DOM overlays in the normal React tree\n\n## Use This Skill When\n\n- the project already uses React\n- the 3D scene must share state with the rest of the app\n- declarative scene composition is a net gain\n- the team wants pmndrs helpers instead of building every helper layer by hand\n\n## Do Not Use This Skill When\n\n- the app is not React-based\n- the project wants a cleaner imperative runtime with minimal React coordination\n- the problem is asset packaging rather than runtime composition\n\n## Best Fit Scenarios\n\n- 3D configurators and tool-rich browser products\n- React apps with embedded game or scene surfaces\n- 3D menus, editors, or world maps in an existing React app\n- 3D game UIs that depend on shared app state and non-canvas shells\n\n## Core Rules\n\n1. Keep simulation state outside render components.\n   - React components should describe scene composition, not become the source of truth for gameplay rules.\n2. Use React state and scene state deliberately.\n   - Shared UI state can live in app state.\n   - High-frequency simulation should not force the whole app through unnecessary React churn.\n3. Use pmndrs helpers intentionally.\n   - Drei for controls, loaders, helpers, environments, and common scene primitives.\n   - `@react-three\u002Frapier` for physics integration.\n   - `@react-three\u002Fpostprocessing` for optional effects.\n   - `@react-three\u002Fa11y` when the interaction model benefits from accessible scene semantics.\n4. Keep HUD, settings, and menus in DOM by default.\n5. Keep starter scaffolds visually restrained.\n   - Start with one compact objective or status surface and transient prompts.\n   - Keep notes, maps, and multi-step checklists collapsed until opened.\n   - Do not surround the `Canvas` with equally weighted glass cards.\n\n## Architectural Guidance\n\n- Use a dedicated scene root component that owns the `Canvas`.\n- Keep camera rigs and control components isolated from gameplay systems.\n- Keep loader and asset wrappers predictable.\n- Keep DOM overlays and the 3D scene coordinated through explicit state boundaries.\n- If a system needs tight imperative control, isolate it rather than forcing everything into declarative patterns.\n- If the scene is immediately playable, keep the initial overlay budget low and let the world do more of the onboarding.\n\n## Anti-Patterns\n\n- Treating React components as the gameplay state store\n- Pushing heavy per-frame mutation through broad app state\n- Using R3F only because React is available, even when the project needs a cleaner imperative runtime\n- Building HUD or inventory UI inside the 3D scene by default\n- Shipping an initial scaffold with large cards occupying every side of the viewport\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- React Three Fiber stack: `..\u002F..\u002Freferences\u002Freact-three-fiber-stack.md`\n- React starter: `..\u002F..\u002Freferences\u002Freact-three-fiber-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","# React Three Fiber Game\n\n## Overview\n\nUse this skill when the 3D runtime lives inside a React application. This is the default React-native 3D path in the plugin and should be preferred over vanilla Three.js when the app shell, settings, storefront, editor surface, or surrounding product already uses React.\n\nRecommended stack:\n\n- `@react-three\u002Ffiber`\n- `three`\n- `@react-three\u002Fdrei`\n- `@react-three\u002Frapier`\n- `@react-three\u002Fpostprocessing`\n- `@react-three\u002Fa11y` when accessibility-sensitive interaction matters\n- DOM overlays in the normal React tree\n\n## Use This Skill When\n\n- the project already uses React\n- the 3D scene must share state with the rest of the app\n- declarative scene composition is a net gain\n- the team wants pmndrs helpers instead of building every helper layer by hand\n\n## Do Not Use This Skill When\n\n- the app is not React-based\n- the project wants a cleaner imperative runtime with minimal React coordination\n- the problem is asset packaging rather than runtime composition\n\n## Best Fit Scenarios\n\n- 3D configurators and tool-rich browser products\n- React apps with embedded game or scene surfaces\n- 3D menus, editors, or world maps in an existing React app\n- 3D game UIs that depend on shared app state and non-canvas shells\n\n## Core Rules\n\n1. Keep simulation state outside render components.\n   - React components should describe scene composition, not become the source of truth for gameplay rules.\n2. Use React state and scene state deliberately.\n   - Shared UI state can live in app state.\n   - High-frequency simulation should not force the whole app through unnecessary React churn.\n3. Use pmndrs helpers intentionally.\n   - Drei for controls, loaders, helpers, environments, and common scene primitives.\n   - `@react-three\u002Frapier` for physics integration.\n   - `@react-three\u002Fpostprocessing` for optional effects.\n   - `@react-three\u002Fa11y` when the interaction model benefits from accessible scene semantics.\n4. Keep HUD, settings, and menus in DOM by default.\n5. Keep starter scaffolds visually restrained.\n   - Start with one compact objective or status surface and transient prompts.\n   - Keep notes, maps, and multi-step checklists collapsed until opened.\n   - Do not surround the `Canvas` with equally weighted glass cards.\n\n## Architectural Guidance\n\n- Use a dedicated scene root component that owns the `Canvas`.\n- Keep camera rigs and control components isolated from gameplay systems.\n- Keep loader and asset wrappers predictable.\n- Keep DOM overlays and the 3D scene coordinated through explicit state boundaries.\n- If a system needs tight imperative control, isolate it rather than forcing everything into declarative patterns.\n- If the scene is immediately playable, keep the initial overlay budget low and let the world do more of the onboarding.\n\n## Anti-Patterns\n\n- Treating React components as the gameplay state store\n- Pushing heavy per-frame mutation through broad app state\n- Using R3F only because React is available, even when the project needs a cleaner imperative runtime\n- Building HUD or inventory UI inside the 3D scene by default\n- Shipping an initial scaffold with large cards occupying every side of the viewport\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- React Three Fiber stack: `..\u002F..\u002Freferences\u002Freact-three-fiber-stack.md`\n- React starter: `..\u002F..\u002Freferences\u002Freact-three-fiber-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",{"name":5,"description":7},"main","d9535210da9af28aa76bca80de80355197e1b6d6","skills\u002Freact-three-fiber-game","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog","https:\u002F\u002Fgithub.com\u002Fzfifteen","I like to measure things.","2026-07-19 23:41:54",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add zfifteen\u002Fskills-catalog --skill react-three-fiber-game",{"tool":37,"command":38},"bunx","bunx skills add zfifteen\u002Fskills-catalog --skill react-three-fiber-game",{"tool":40,"command":41},"pnpm","pnpm dlx skills add zfifteen\u002Fskills-catalog --skill react-three-fiber-game","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Freact-three-fiber-game\u002FSKILL.md",true,[45],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"agents\u002Fopenai.yaml","REFERENCE","参考文档",239,"https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Freact-three-fiber-game\u002Fagents\u002Fopenai.yaml",[52,59,66,73,82,89],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":19},"01M79GXQ2PWPT2E4CJYHXVJ0YE","Zotero","Use Zotero Desktop from Codex to enable\u002Fprobe the local API, search a local Zotero library, list items\u002Fcollections\u002Ftags, export BibTeX, insert citation keys into LaTeX or Markdown drafts, read indexed full text when requested, and import BibTeX\u002FRIS records into Zotero through the connector server. Use when the user mentions Zotero, citations, references.bib, BibTeX export, local Zotero API, localhost:23119, or adding citations from a Zotero library.","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fzotero\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M79GXN85NETKBE06865CWK6Z","zoom-apps-sdk","Use when using Apps SDK.","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-apps-sdk\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M79GXCYD7FGYS932J9N9RFFY","youtube","Obtain accurate, timestamped YouTube video transcripts (preferring manual captions over auto-generated) as the primary deliverable, then derive summaries, key claims, or notes from that transcript.  Use when the user provides a YouTube URL (or video ID) and wants the transcript, a faithful summary, key claims with attribution, timestamped notes, or \"what does this video actually say\".  The skill is transcript-first: never substitute metadata, title, description, or search snippets for the spoken content.  Triggers: \"youtube transcript\", \"get the transcript of this video\", \"summarize this youtube video\", \"what did they say in https:\u002F\u002Fyoutube.com\u002F...\", \"key claims from this talk\".","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":77,"licenseFileUrl":78,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M79GX8EXHHYM566BKR7MS778","yeet","Publish local changes to GitHub by confirming scope, committing intentionally, pushing the branch, and opening a draft PR through the GitHub app from this plugin, with `gh` used only as a fallback where connector coverage is insufficient.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M79GX2HFJPX84NMRE5VBTYX9","x-post-creator","Create X-ready post threads and co-located story packages from the active conversation or referenced project material. Use when the user says turn this into an X-post, \u002Fx-post, make this into an X thread, or wants plain-language social posts with supporting images saved to docs\u002Fx-posts\u002F[story-name]\u002F.","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fx-post-creator\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M79GWXQT4HBT6QME6QSBZJFA","x-api","Search, read, and write X posts through the local X API MCP server (the same backend used by the Codex x-api skill). Use for searching X\u002Fx.com, reading threads and replies, creating lists, staging\u002Fpublishing posts for @alltheputs, finding high-visibility reply targets for research outreach, ingesting public context, or any request that mentions \u002Fx-api or \"search X\".","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fx-api\u002FSKILL.md",[],[]]