ericrisco/rsc-harness / skills/gamedev-shaders
gamedev-shaders
VerifiedUse when authoring or debugging a shader, material, VFX, or full-screen post-process in a game engine — Godot 4.x `.gdshader`, Unity 6 URP/HDRP, Unreal 5.x Materials, effect recipes, shader performance. NOT gameplay or engine-API code (that is `godot`/`unity`/`unreal`), NOT physics (`gamedev-physics`), NOT build variant stripping (`gamedev-shipping`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 14.2 KB |
| evals/README.md | markdown | 1.1 KB |
| evals/cases.yaml | config | 4.0 KB |
| references/effect-recipes.md | markdown | 8.1 KB |
| references/godot-shading-language.md | markdown | 5.8 KB |
| references/unity-and-unreal-shaders.md | markdown | 7.2 KB |
evals/README.md
View on GitHub# Eval harness — `gamedev-shaders` skill
These cases are run by the rsc skill-eval harness (a Claude agent with the full catalog loaded),
or read manually. They assert two things: **triggering** — the description fires on shader /
material / VFX / post-process / "how do I make X effect" prompts (including Spanish and
symptom-only phrasings like "slow on mobile") and stays quiet on near-misses, routing each to the
right sibling (`godot`/`unity`/`unreal` for gameplay-or-setup, `gamedev-physics` for simulation,
`gamedev-shipping` for variant stripping, `sql` for the false-friend "optimize"); and
**capability** — that with `SKILL.md` and its references loaded, the generated Godot 4 dissolve
shader satisfies the rubric (valid `shader_type`, `discard` against an animatable threshold, an
emissive `smoothstep` edge, `source_color` hints, no removed `SCREEN_TEXTURE`/`hint_color` APIs,
code-driven animation, and an overdraw note). Run 3–5 trials per prompt since routing is
non-deterministic; a prompt passes on a majority. No network needed — the capability rubric is
judged by reading the output against the points.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |