cat-herder

Expert three.js and React Three Fiber (r3f/drei) development for games, interactive 3D, data-viz, product configurators, model viewers, and WebXR on the web. Use this skill whenever a task involves three.js, @react-three/fiber, @react-three/drei, Threlte, WebGL or WebGPU rendering, a 3D scene/camera/mesh/material/light, loading a .glb/.gltf/ .fbx/.obj/.usdz model, GLSL or TSL shaders, node materials, post-processing/bloom, raycasting/picking, instancing/performance tuning, or debugging a "black screen"/ washed-out-colors/z-fighting 3D bug — even if the user never says "three.js" and just says "3D scene", "WebGL", "render a model in the browser", or "make a browser game". Prevents the two dominant failure modes: version drift (three ships ~monthly with breaking changes) and hallucinated API signatures.

Convert a set of Jira stories or GitHub issues into a dependency-aware, parallelized orchestration plan plus a resumable STATE.md tracker. Use this skill whenever someone pastes a set of issues, stories, or a work-item table (especially with a "blocked by" / dependency column) and wants it turned into an agent-driven execution plan. Trigger on phrasings like "turn these issues into an orchestrated plan", "build me an orchestration plan", "make a wave plan", "fan out agents to implement these stories", "orchestrate this backlog", "plan parallel execution with worktrees", or when a tracking issue links several sub-issues that need coordinated implementation. Also trigger when someone has a dependency graph of work and wants maximum safe parallelism with a single clean merge.

Produces a bulletproof implementation plan for a GitHub issue by collaborating with three specialist subagents — senior engineer, game/application architect, and technical writer — in parallel, validating every claim against CLAUDE.md, CONTEXT.md (when it exists), and the ADRs, then presenting the plan in plan mode for approval before any code is written. Every plan carries the full standard SDLC envelope (branch → implement → test → commit → review + self-review → fix → commit → PR → retrospective) so it lands a PR for sign-off. Use when the user wants to plan or spec out a GitHub issue, runs /bulletproof-plan with an issue number or URL, or asks for a rigorous multi-specialist implementation plan.