team-gamelisted

Delivers a playable web-game slice: game-concept check → engine ADR → simulation + rendering (three.js/Pixi) + UI overlay (Angular/Vue) + optional multiplayer (Go server) in parallel → frame-budget measurement → accessibility settings → review. Use to build the prototype or a game feature.
gonimar/claude-web-studio · ★ 0 · Web & Frontend · score 76

Install: claude install-skill gonimar/claude-web-studio

# Team: Game Reply in the project conversation language (CLAUDE.md → Language); code, identifiers, paths and commit messages stay in English. File writes and any mutation (git, deploy) happen only after an explicit "May I write?" / "Proceed?" — each one `AskUserQuestion` (proceed (Recommended) · show the draft/diff first · not now) → "yes"; delegated agents follow the same protocol. After the "write" answer: `touch .claude/.write-consent` (rule 7 — the consent-guard hook checks the marker). ## Phase 1: Readiness `docs/specs/game-concept.md` (missing → `/game-concept`); the engine ADR (missing → `/architecture-decision`); budgets in technical-preferences. ## Phase 2: Parallel implementation `web-game-engineer` (simulation, loop, input, audio, saves) ‖ `threejs-engineer` or `web-game-engineer` (rendering) ‖ `angular-engineer`/`vue-engineer` (UI overlay/menus from the UX spec) ‖ `multiplayer-engineer` + `go-engineer` (if networked; protocol via `api-designer` first). ## Phase 3: Measurements and accessibility `performance-engineer` (frame, draw calls, memory, load on 4G emulation) ‖ `accessibility-specialist` (menus, settings). ## Phase 4: Review and summary `/code-review --diff`; the "fun" criterion from the concept — the user plays and decides; a summary of numbers. Verdict: `PLAYABLE` | `PARTIAL` | `BLOCKED`. Next step — one `AskUserQuestion`: `/story-done` (Recommended) · the next slice · fix the open findings first.