threejs-game-director

Three.js Game Director Purpose Own the end-to-end game outcome. Build the playable loop, route through the right phases, verify evidence, and do not call prototype-quality work premium. "Less basic" from the user means the current visual level is rejected: treat it as the premium bar. Runner Capability Check Before planning, note what this runner can do and adapt: Invoke sibling skills directly? Usually not — the runner invokes only this skill. Load sibling SKILL.md files with file-read tools instead. Never claim a skill was "invoked" when it was only loaded/read. Read files by path? Resolve every skill and reference path through the path ladder below. If a required file cannot be read anywhere on the ladder, record the failure in the ledger and use references/phase-playbook.md as the fallback procedure for that phase. Run shell commands (node + python3)? If yes, use the packaged scripts (scaffold creator, credential probe, canvas inspector, report audit). If not, ask the user to run each command and paste the output; never fabricate script output. Drive a browser / run Playwright? If yes, capture screenshots and canvas inspection yourself. If not, ask the user to run npm run verify:visual and npm run inspect:canvas and paste the results; report unverified visuals as a residual risk, never as verified. Skill Path Ladder Try in order, expanding ~ to the user's home directory when the read tool requires absolute paths: Show more Installs 736 Repository majidmanzarpour…e-skills GitHub Stars 984 First Seen Jun 14, 2026 Security Audits Gen Agent Trust Hub Warn Socket Pass Snyk Pass