r3f-component-plan
Purpose
Translate a planned GLB delivery into the exact public surface a React Three Fiber component should expose, so the web engineer's contract is locked before code is written.
Quick start
- enumerate the props the consumer needs (color, animation name, scale, onLoaded)
- decide ref shape (forwardRef, imperative methods)
- decide Suspense boundary location
- decide useGLTF caching + cleanup strategy
- decide animation hook contract (auto-play, manual control)
When to use
- the GLB will ship to a web app using React Three Fiber
- before the web team writes the component
- when "I'll just import the GLB" needs more rigor (multiple clips, prop overrides, lazy loading)
When not to use
- consumers using vanilla Three.js (different API) → use
../glb-web-handoff/SKILL.md (different API)
- consumers using Babylon / model-viewer (different stack) → use
../glb-animation-handoff/SKILL.md (different stack)
- the GLB is rendered server-side (e.g. AR pre-render); no React component needed → use
../plain-language-response/SKILL.md (Delegates out-of-scope requests to plain-language-response)
Trigger phrases
- "how should the React component look"
- "what props should I expose"
- "ref shape for the model"
- "we use react-three-fiber"
Prerequisites / readiness
- GLB delivery contract known (clips, materials, variants)
- target React/Three.js/R3F versions known (or assume current stable)
- consumer team's preferred state-management style noted (Zustand / context / props)
Input schema
Required inputs
| Input |
Why it is required |
GLB delivery contract (from glb-web-handoff) |
Defines available variants, nodes, and delivery constraints |
Animation contract (from glb-animation-handoff) |
Defines clip names, triggers, loop/chain rules, and blend durations |
R3F version (8 vs 9) |
Hook signatures change between R3F 8 and R3F 9 and require explicit caveats |
| Use case (hero / configurator / interactive view) |
Determines Suspense placement, fallback behavior, and instance policy |
| Customization scope |
Determines which props and ref methods are exposed |
Optional inputs
| Input |
Use |
Performance budget (from mobile-glb-budget) |
Informs useGLTF shared caching vs per-instance policy within pinned ceilings |
| Existing consumer state pattern |
Aligns prop and callback shapes with the consumer team's state flow |
Assumptions to confirm
- Animation clip contracts are already locked via
glb-animation-handoff.
- Memory and asset ceilings are already pinned via
mobile-glb-budget.
- Target R3F major version (8 or 9) is identified, or caveats for both are documented.
Output schema
Primary output
A locked React Three Fiber component shape spec (no generated component implementation code) containing:
- Props table (name, type, default, purpose)
- Ref interface (imperative methods exposed, or explicit "none")
- Suspense placement (inside vs outside component boundary)
useGLTF caching policy (shared vs per-instance)
- Animation hook contract (aligned with
glb-animation-handoff)
- Cleanup contract (unmount behavior)
- Error / fallback contract (what renders if GLB load fails)
- Minimal usage example (consumer call-site shape only, not component implementation code)
Secondary output
- R3F version compatibility caveats (specifically R3F 8 vs 9 hook signature differences)
- explicit boundary notes referencing
glb-animation-handoff, mobile-glb-budget, and glb-web-handoff
Evidence / caveat output
Runtime status: Not Run | Attempted | Produced | Verified | Failed
Artifact status: Not Produced | Produced | Verified | Failed
Evidence used: <links, paths, logs, or "none">
Limitations: <known gaps>
Default is Runtime status: Not Run and Artifact status: Not Produced. Truth states are downgrade-only and never upgraded by this skill, as web runtime belongs to the consumer team.
Required laws
../../laws/evidence-before-done.md
../../laws/non-blender-user-language.md
../../laws/no-arbitrary-python-interface.md
../../laws/official-runtime-only.md
Official runtime boundary
This skill produces planning specs only. It does not generate component code, run a web app, or claim that the resulting component will perform correctly without measured load tests. Web-side implementation is owned by the consumer team.
If runtime is involved, refer to ../../docs/runtime-stack-strategy.md for the 2-path + CLI appendix model. R3F lives entirely on the web side and does not interact with Blender at runtime.
Operating procedure
- Read the upstream animation contract (
glb-animation-handoff) and performance ceilings (mobile-glb-budget).
- Enumerate consumer customization points into the props table (name, type, default, purpose).
- Define the ref interface for imperative controls (or mark "none required").
- Specify Suspense boundary placement and the error / fallback contract.
- Specify the
useGLTF caching policy and the unmount cleanup contract.
- Specify the animation hook contract matching
glb-animation-handoff triggers and add R3F 8/9 hook signature caveats.
- Provide a minimal call-site usage example (never generate the component implementation code).
- Record truth states (
Runtime status: Not Run, Artifact status: Not Produced default; downgrade-only) and hand off to glb-web-handoff (and plain-language-response for final user wording).
Decision tree
Animation clips present but uncontracted?
→ Hand off to glb-animation-handoff first
Performance or memory ceilings unpinned?
→ Hand off to mobile-glb-budget first
Multiple instances vs single instance?
→ Document useGLTF caching policy (shared cache vs per-instance) and unmount cleanup contract
Interactive animation triggers required?
→ Expose declarative trigger props and/or ref interface aligned with glb-animation-handoff
R3F version 8 vs 9 unknown?
→ Document hook signature caveats for both R3F 8 and R3F 9
GLB load or network failure possible?
→ Lock explicit Suspense placement + error boundary / fallback contract
Playbooks
Playbook A: Hero single instance
- Props table: transform props (
scale, position, rotation) and onLoaded callback.
- Ref interface: none required (or root reference only).
- Suspense placement: around component boundary with explicit placeholder fallback.
useGLTF caching policy: standard single-instance cache policy with explicit unmount cleanup contract.
- Animation hook contract: auto-play idle clip per
glb-animation-handoff.
- Error / fallback contract: fallback visual if asset fetch fails.
Playbook B: Interactive configurator
- Props table:
variant, colorOverride, animationName, onVariantChange, onError.
- Ref interface:
playAction(name), setVariant(name).
- Suspense placement: section-level boundary with loading fallback.
useGLTF caching policy: shared cache policy aligned with mobile-glb-budget ceilings and explicit unmount cleanup.
- Animation hook contract: controlled transitions per
glb-animation-handoff with R3F 8/9 hook signature caveats.
- Error / fallback contract: error boundary fallback prop.
Playbook C: Multi-instance product grid item
- Props table:
src, instanceId, activeClip, onSelect.
- Ref interface:
playAction(name), stopAction().
- Suspense placement: grid or card boundary with lightweight fallback contract.
useGLTF caching policy: shared asset cache policy paired with explicit unmount cleanup contract, bounded by mobile-glb-budget.
- Error / fallback contract: per-card fallback state on load error.
Mode handling
Text-only mode
Produce the complete R3F component shape spec and minimal call-site usage example; do not generate component implementation code. Set Runtime status: Not Run and Artifact status: Not Produced.
Runtime-ready mode
Web runtime belongs to the consumer team, not BlendOps. Keep Runtime status: Not Run and Artifact status: Not Produced as the planning default; truth states are downgrade-only and never upgraded by this skill.
Blocked runtime mode
If the consumer R3F version or upstream contracts are incomplete, document R3F 8/9 hook signature caveats, keep truth states at Runtime status: Not Run and Artifact status: Not Produced (or downgrade to Failed if blocked), and name required upstream handoffs.
Validation checklist
Pass / Warn / Fail rubric
| Verdict |
Criteria |
| Pass |
Complete component shape spec (props, ref, Suspense, useGLTF cache policy, animation hook contract, cleanup, error/fallback, minimal usage example), R3F 8/9 caveats noted, truth states downgrade-only, handoffs named. |
| Warn |
Spec present but Suspense placement, cleanup policy, or R3F 8/9 version caveats are incomplete. |
| Fail |
Generates component implementation code, claims runtime performance, upgrades truth states, invents R3F runtime internals as BlendOps facts, blurs color/material/animation/budget ownership, or omits error/fallback/ref contracts. |
Failure handling
- If the user asks for full React component implementation code → refuse code generation; explain that this skill outputs the locked component shape spec and minimal usage example for the web team to implement.
- If R3F version (8 vs 9) is unknown → include hook signature caveats for both versions.
- If animation clip details are missing → hand off to
glb-animation-handoff instead of inventing clip hooks.
- If memory or instance ceilings are unknown → hand off to
mobile-glb-budget.
- If material or color encoding questions arise → hand off to
color-management-decision and material-quality-checker.
Troubleshooting
| Problem |
Response |
| Material or color appearance mismatch reported |
Do not diagnose texture/color encoding here; hand off to color-management-decision and material-quality-checker. |
| Animation clip names or transitions mismatch |
Verify the animation hook contract against glb-animation-handoff and check R3F 8 vs 9 hook signature caveats. |
| Multi-instance memory or frame budget concerns |
Hand off to mobile-glb-budget to pin ceilings, and clarify the useGLTF caching and unmount cleanup contracts in the spec. |
| Asset delivery, compression, or packaging mismatch |
Hand off to glb-web-handoff for web delivery packaging details. |
Best practices
- Prefer declarative props and callbacks over implicit internal state.
- Lock all eight spec elements (props, ref, Suspense,
useGLTF cache policy, animation hook contract, cleanup, error/fallback, minimal call-site usage example) before web engineering starts.
- Document R3F 8 vs 9 hook signature differences as explicit caveats rather than asserting runtime guarantees.
- Respect strict role boundaries with
glb-animation-handoff, mobile-glb-budget, glb-web-handoff, and plain-language-response.
Good examples
- "Component spec
ProductHeroModel (R3F 8/9 caveat: verify hook signatures for target major version): Props { src: string, scale?: number = 1, animationName?: 'idle' | 'open' = 'idle', variant?: string, onLoaded?: () => void }; Ref { playAction(name: string): void }; Suspense: wrapped at parent section boundary; useGLTF policy: shared cache; Animation hook: bound to glb-animation-handoff clip contract; Cleanup: stop active mixer actions and release instance resources on unmount; Error/fallback: render fallback prop inside error boundary; Minimal usage: <ErrorBoundary fallback={<FallbackCard />}><Suspense fallback={<Loader />}><ProductHeroModel ref={modelRef} src=\"/model.glb\" animationName=\"idle\" /></Suspense></ErrorBoundary>. Runtime status: Not Run, Artifact status: Not Produced. Next: glb-web-handoff."
Bad examples
- "Just useGLTF and render." — no props, no ref, no Suspense, no error path.
- "Will be smooth." — no measurement, no ceiling.
User-facing response template
Component name: <PascalCase>
R3F version caveat: <R3F / 8 9 caveats hook signature>
Props table:
<name> | <type> | <default> | <purpose>
Ref interface:
<method>(args): <returnType> (or "none")
Suspense placement: <component boundary / page section / app root>
useGLTF caching policy: <shared cache / per-instance>
Animation hook contract: <aligned with glb-animation-handoff>
Cleanup contract: <unmount cleanup policy>
Error / fallback contract: <error boundary + fallback behavior>
Minimal usage example (call-site only, no component code):
<Suspense + Component ErrorBoundary call-site>
Runtime status: Not Run | Attempted | Produced | Verified | Failed
Artifact status: Not Produced | Produced | Verified | Failed
Evidence used: <links, paths, logs, or "none">
Limitations: <gaps>
Next: glb-web-handoff (then plain-language-response)
Anti-patterns
- Generating React Three Fiber component implementation code instead of a shape spec.
- Promising runtime performance without measurement.
- Presenting unverified R3F internals (hook implementation details, scene cloning APIs, HMR behavior) as BlendOps facts.
- Blurring boundaries into color/texture validation (
color-management-decision, material-quality-checker), animation contracts (glb-animation-handoff), budgets (mobile-glb-budget), or web delivery packaging (glb-web-handoff).
- Using
Artifact status: Not Run or upgrading truth states instead of keeping Runtime status: Not Run and Artifact status: Not Produced downgrade-only.
Cross-skill handoff
- [upstream_reference] Animation contract →
../glb-animation-handoff/SKILL.md
- [upstream_reference] Performance budget ceilings →
../mobile-glb-budget/SKILL.md
- [upstream_reference] Color and material checks (color-management-decision) →
../color-management-decision/SKILL.md
- [upstream_reference] Color and material checks (material-quality-checker) →
../material-quality-checker/SKILL.md
- [upstream_reference] Web delivery packaging →
../glb-web-handoff/SKILL.md
- [progression] Final user-facing response →
../plain-language-response/SKILL.md
Non-goals
- Generate React or Three.js component implementation code.
- Run web apps or execute React Three Fiber at runtime.
- Claim or verify web runtime performance.
- Upgrade truth states (web runtime belongs to the consumer team, not BlendOps).
- Own animation contracts, performance budgets, color/material validation, or web delivery packaging.
References
references/component-shape-patterns.md
references/suspense-placement-rules.md
references/usegltf-caching-rules.md
../../docs/skill-system.md
1---2name: r3f-component-plan3description: Plan the React Three Fiber component shape (props, refs, Suspense, useGLTF cache, animation hooks) before delivering a GLB to a web team.4metadata:5 source: https://skillmd.com/skills/thanhnguyxnorg/r3f-component-plan6---78# r3f-component-plan910## Purpose11Translate a planned GLB delivery into the exact public surface a React Three Fiber component should expose, so the web engineer's contract is locked before code is written.1213## Quick start14- enumerate the props the consumer needs (color, animation name, scale, onLoaded)15- decide ref shape (forwardRef, imperative methods)16- decide Suspense boundary location17- decide useGLTF caching + cleanup strategy18- decide animation hook contract (auto-play, manual control)1920## When to use21- the GLB will ship to a web app using React Three Fiber22- before the web team writes the component23- when "I'll just import the GLB" needs more rigor (multiple clips, prop overrides, lazy loading)2425## When not to use26<!-- blendops:generated:start exclusions -->27- consumers using vanilla Three.js (different API) → use `../glb-web-handoff/SKILL.md` (different API)28- consumers using Babylon / model-viewer (different stack) → use `../glb-animation-handoff/SKILL.md` (different stack)29- the GLB is rendered server-side (e.g. AR pre-render); no React component needed → use `../plain-language-response/SKILL.md` (Delegates out-of-scope requests to plain-language-response)30<!-- blendops:generated:end exclusions -->3132## Trigger phrases33<!-- blendops:generated:start triggers -->34- "how should the React component look"35- "what props should I expose"36- "ref shape for the model"37- "we use react-three-fiber"38<!-- blendops:generated:end triggers -->3940## Prerequisites / readiness41- GLB delivery contract known (clips, materials, variants)42- target React/Three.js/R3F versions known (or assume current stable)43- consumer team's preferred state-management style noted (Zustand / context / props)4445## Input schema4647### Required inputs4849| Input | Why it is required |50|---|---|51| GLB delivery contract (from `glb-web-handoff`) | Defines available variants, nodes, and delivery constraints |52| Animation contract (from `glb-animation-handoff`) | Defines clip names, triggers, loop/chain rules, and blend durations |53| R3F version (`8` vs `9`) | Hook signatures change between R3F 8 and R3F 9 and require explicit caveats |54| Use case (hero / configurator / interactive view) | Determines Suspense placement, fallback behavior, and instance policy |55| Customization scope | Determines which props and ref methods are exposed |5657### Optional inputs5859| Input | Use |60|---|---|61| Performance budget (from `mobile-glb-budget`) | Informs `useGLTF` shared caching vs per-instance policy within pinned ceilings |62| Existing consumer state pattern | Aligns prop and callback shapes with the consumer team's state flow |6364### Assumptions to confirm65- Animation clip contracts are already locked via `glb-animation-handoff`.66- Memory and asset ceilings are already pinned via `mobile-glb-budget`.67- Target R3F major version (8 or 9) is identified, or caveats for both are documented.6869## Output schema7071### Primary output72A locked React Three Fiber component shape spec (no generated component implementation code) containing:73- Props table (name, type, default, purpose)74- Ref interface (imperative methods exposed, or explicit "none")75- Suspense placement (inside vs outside component boundary)76- `useGLTF` caching policy (shared vs per-instance)77- Animation hook contract (aligned with `glb-animation-handoff`)78- Cleanup contract (unmount behavior)79- Error / fallback contract (what renders if GLB load fails)80- Minimal usage example (consumer call-site shape only, not component implementation code)8182### Secondary output83- R3F version compatibility caveats (specifically R3F 8 vs 9 hook signature differences)84- explicit boundary notes referencing `glb-animation-handoff`, `mobile-glb-budget`, and `glb-web-handoff`8586### Evidence / caveat output8788```txt89Runtime status: Not Run | Attempted | Produced | Verified | Failed90Artifact status: Not Produced | Produced | Verified | Failed91Evidence used: <links, paths, logs, or "none">92Limitations: <known gaps>93```9495Default is `Runtime status: Not Run` and `Artifact status: Not Produced`. Truth states are downgrade-only and never upgraded by this skill, as web runtime belongs to the consumer team.9697## Required laws98- `../../laws/evidence-before-done.md`99- `../../laws/non-blender-user-language.md`100- `../../laws/no-arbitrary-python-interface.md`101- `../../laws/official-runtime-only.md`102103## Official runtime boundary104105This skill produces **planning specs only**. It does not generate component code, run a web app, or claim that the resulting component will perform correctly without measured load tests. Web-side implementation is owned by the consumer team.106107If runtime is involved, refer to `../../docs/runtime-stack-strategy.md` for the 2-path + CLI appendix model. R3F lives entirely on the web side and does not interact with Blender at runtime.108109## Operating procedure1101111. Read the upstream animation contract (`glb-animation-handoff`) and performance ceilings (`mobile-glb-budget`).1122. Enumerate consumer customization points into the props table (name, type, default, purpose).1133. Define the ref interface for imperative controls (or mark "none required").1144. Specify Suspense boundary placement and the error / fallback contract.1155. Specify the `useGLTF` caching policy and the unmount cleanup contract.1166. Specify the animation hook contract matching `glb-animation-handoff` triggers and add R3F 8/9 hook signature caveats.1177. Provide a minimal call-site usage example (never generate the component implementation code).1188. Record truth states (`Runtime status: Not Run`, `Artifact status: Not Produced` default; downgrade-only) and hand off to `glb-web-handoff` (and `plain-language-response` for final user wording).119120## Decision tree121122```txt123Animation clips present but uncontracted?124 → Hand off to glb-animation-handoff first125Performance or memory ceilings unpinned?126 → Hand off to mobile-glb-budget first127Multiple instances vs single instance?128 → Document useGLTF caching policy (shared cache vs per-instance) and unmount cleanup contract129Interactive animation triggers required?130 → Expose declarative trigger props and/or ref interface aligned with glb-animation-handoff131R3F version 8 vs 9 unknown?132 → Document hook signature caveats for both R3F 8 and R3F 9133GLB load or network failure possible?134 → Lock explicit Suspense placement + error boundary / fallback contract135```136137## Playbooks138139### Playbook A: Hero single instance140141* Props table: transform props (`scale`, `position`, `rotation`) and `onLoaded` callback.142* Ref interface: none required (or root reference only).143* Suspense placement: around component boundary with explicit placeholder fallback.144* `useGLTF` caching policy: standard single-instance cache policy with explicit unmount cleanup contract.145* Animation hook contract: auto-play idle clip per `glb-animation-handoff`.146* Error / fallback contract: fallback visual if asset fetch fails.147148### Playbook B: Interactive configurator149150* Props table: `variant`, `colorOverride`, `animationName`, `onVariantChange`, `onError`.151* Ref interface: `playAction(name)`, `setVariant(name)`.152* Suspense placement: section-level boundary with loading fallback.153* `useGLTF` caching policy: shared cache policy aligned with `mobile-glb-budget` ceilings and explicit unmount cleanup.154* Animation hook contract: controlled transitions per `glb-animation-handoff` with R3F 8/9 hook signature caveats.155* Error / fallback contract: error boundary fallback prop.156157### Playbook C: Multi-instance product grid item158159* Props table: `src`, `instanceId`, `activeClip`, `onSelect`.160* Ref interface: `playAction(name)`, `stopAction()`.161* Suspense placement: grid or card boundary with lightweight fallback contract.162* `useGLTF` caching policy: shared asset cache policy paired with explicit unmount cleanup contract, bounded by `mobile-glb-budget`.163* Error / fallback contract: per-card fallback state on load error.164165## Mode handling166167### Text-only mode168169Produce the complete R3F component shape spec and minimal call-site usage example; do not generate component implementation code. Set `Runtime status: Not Run` and `Artifact status: Not Produced`.170171### Runtime-ready mode172173Web runtime belongs to the consumer team, not BlendOps. Keep `Runtime status: Not Run` and `Artifact status: Not Produced` as the planning default; truth states are downgrade-only and never upgraded by this skill.174175### Blocked runtime mode176177If the consumer R3F version or upstream contracts are incomplete, document R3F 8/9 hook signature caveats, keep truth states at `Runtime status: Not Run` and `Artifact status: Not Produced` (or downgrade to `Failed` if blocked), and name required upstream handoffs.178179## Validation checklist180181* [ ] Props table complete (name, type, default, purpose)182* [ ] Ref interface specified (or explicitly marked "no imperative methods needed")183* [ ] Suspense placement explicit184* [ ] `useGLTF` caching policy explicit185* [ ] Animation hook contract explicit and aligned with `glb-animation-handoff`186* [ ] Cleanup contract explicit187* [ ] Error / fallback contract explicit188* [ ] Minimal call-site usage example included (without generating component implementation code)189* [ ] R3F 8/9 hook signature caveats documented190* [ ] No performance promises without measurement191* [ ] Truth states set to `Runtime status: Not Run` and `Artifact status: Not Produced` (downgrade-only, never upgraded)192* [ ] Next handoff skill named (`glb-web-handoff` / `plain-language-response`)193194## Pass / Warn / Fail rubric195196| Verdict | Criteria |197|---|---|198| Pass | Complete component shape spec (props, ref, Suspense, `useGLTF` cache policy, animation hook contract, cleanup, error/fallback, minimal usage example), R3F 8/9 caveats noted, truth states downgrade-only, handoffs named. |199| Warn | Spec present but Suspense placement, cleanup policy, or R3F 8/9 version caveats are incomplete. |200| Fail | Generates component implementation code, claims runtime performance, upgrades truth states, invents R3F runtime internals as BlendOps facts, blurs color/material/animation/budget ownership, or omits error/fallback/ref contracts. |201202## Failure handling203204* If the user asks for full React component implementation code → refuse code generation; explain that this skill outputs the locked component shape spec and minimal usage example for the web team to implement.205* If R3F version (8 vs 9) is unknown → include hook signature caveats for both versions.206* If animation clip details are missing → hand off to `glb-animation-handoff` instead of inventing clip hooks.207* If memory or instance ceilings are unknown → hand off to `mobile-glb-budget`.208* If material or color encoding questions arise → hand off to `color-management-decision` and `material-quality-checker`.209210## Troubleshooting211212| Problem | Response |213|---|---|214| Material or color appearance mismatch reported | Do not diagnose texture/color encoding here; hand off to `color-management-decision` and `material-quality-checker`. |215| Animation clip names or transitions mismatch | Verify the animation hook contract against `glb-animation-handoff` and check R3F 8 vs 9 hook signature caveats. |216| Multi-instance memory or frame budget concerns | Hand off to `mobile-glb-budget` to pin ceilings, and clarify the `useGLTF` caching and unmount cleanup contracts in the spec. |217| Asset delivery, compression, or packaging mismatch | Hand off to `glb-web-handoff` for web delivery packaging details. |218219## Best practices220221* Prefer declarative props and callbacks over implicit internal state.222* Lock all eight spec elements (props, ref, Suspense, `useGLTF` cache policy, animation hook contract, cleanup, error/fallback, minimal call-site usage example) before web engineering starts.223* Document R3F 8 vs 9 hook signature differences as explicit caveats rather than asserting runtime guarantees.224* Respect strict role boundaries with `glb-animation-handoff`, `mobile-glb-budget`, `glb-web-handoff`, and `plain-language-response`.225226## Good examples227228* "Component spec `ProductHeroModel` (R3F 8/9 caveat: verify hook signatures for target major version): Props `{ src: string, scale?: number = 1, animationName?: 'idle' | 'open' = 'idle', variant?: string, onLoaded?: () => void }`; Ref `{ playAction(name: string): void }`; Suspense: wrapped at parent section boundary; `useGLTF` policy: shared cache; Animation hook: bound to `glb-animation-handoff` clip contract; Cleanup: stop active mixer actions and release instance resources on unmount; Error/fallback: render `fallback` prop inside error boundary; Minimal usage: `<ErrorBoundary fallback={<FallbackCard />}><Suspense fallback={<Loader />}><ProductHeroModel ref={modelRef} src=\"/model.glb\" animationName=\"idle\" /></Suspense></ErrorBoundary>`. `Runtime status: Not Run`, `Artifact status: Not Produced`. Next: `glb-web-handoff`."229230## Bad examples231- "Just useGLTF and render." — no props, no ref, no Suspense, no error path.232- "Will be smooth." — no measurement, no ceiling.233234## User-facing response template235236```txt237Component name: <PascalCase>238R3F version caveat: <R3F / 8 9 caveats hook signature>239240Props table:241 <name> | <type> | <default> | <purpose>242243Ref interface:244 <method>(args): <returnType> (or "none")245246Suspense placement: <component boundary / page section / app root>247useGLTF caching policy: <shared cache / per-instance>248Animation hook contract: <aligned with glb-animation-handoff>249Cleanup contract: <unmount cleanup policy>250Error / fallback contract: <error boundary + fallback behavior>251252Minimal usage example (call-site only, no component code):253 <Suspense + Component ErrorBoundary call-site>254255Runtime status: Not Run | Attempted | Produced | Verified | Failed256Artifact status: Not Produced | Produced | Verified | Failed257Evidence used: <links, paths, logs, or "none">258Limitations: <gaps>259Next: glb-web-handoff (then plain-language-response)260```261262## Anti-patterns263264* Generating React Three Fiber component implementation code instead of a shape spec.265* Promising runtime performance without measurement.266* Presenting unverified R3F internals (hook implementation details, scene cloning APIs, HMR behavior) as BlendOps facts.267* Blurring boundaries into color/texture validation (`color-management-decision`, `material-quality-checker`), animation contracts (`glb-animation-handoff`), budgets (`mobile-glb-budget`), or web delivery packaging (`glb-web-handoff`).268* Using `Artifact status: Not Run` or upgrading truth states instead of keeping `Runtime status: Not Run` and `Artifact status: Not Produced` downgrade-only.269270## Cross-skill handoff271<!-- blendops:generated:start handoffs -->272- [upstream_reference] Animation contract → `../glb-animation-handoff/SKILL.md`273- [upstream_reference] Performance budget ceilings → `../mobile-glb-budget/SKILL.md`274- [upstream_reference] Color and material checks (color-management-decision) → `../color-management-decision/SKILL.md`275- [upstream_reference] Color and material checks (material-quality-checker) → `../material-quality-checker/SKILL.md`276- [upstream_reference] Web delivery packaging → `../glb-web-handoff/SKILL.md`277- [progression] Final user-facing response → `../plain-language-response/SKILL.md`278<!-- blendops:generated:end handoffs -->279280## Non-goals281282* Generate React or Three.js component implementation code.283* Run web apps or execute React Three Fiber at runtime.284* Claim or verify web runtime performance.285* Upgrade truth states (web runtime belongs to the consumer team, not BlendOps).286* Own animation contracts, performance budgets, color/material validation, or web delivery packaging.287288## References289- `references/component-shape-patterns.md`290- `references/suspense-placement-rules.md`291- `references/usegltf-caching-rules.md`292- `../../docs/skill-system.md`