What problem does it solve? Fixing game visuals without a structured loop wastes tokens on repeated full-scene renders and manual eyeballing, and makes it easy to break unrelated scenes while fixing one. This Skill defines a disciplined render-critique-fix cycle for a Flix 2D game engine where every change is verified by machine comparison. ## Core Features & Use Cases - Cost-Filtered Review: Runs reference hash checks first, then image digests (diff pixel ratio, changed regions, color counts), reserving visual inspection for one final confirmation. - Single-Scene Rendering: Renders only the touched scene via make render SHOT=<name> or changed templates via make render-changed, avoiding full 150-second re-renders during iteration. - One-Fix-at-a-Time Discipline: Presents at most 3 candidate fixes for a human to pick, then shows before/after images side by side with make diff. - Use Case: A user says "the title screen looks off" — the Skill renders just that shot, proposes three fixes, applies the chosen one, and shows a left/right diff for approval. ## Quick Start Ask the AI to fix the look of a specific game scene, for example: "The battle scene looks wrong, render it and show me what to fix."
