mirror of
https://github.com/PlayableIntelligence/game-creator.git
synced 2026-09-19 07:34:10 +08:00
rshtirmer
eaa818074e
Reduce top-level directories from 19 to 14 and unify the two disconnected site pages into a single build script. Site unification: - gallery/ → site/ (manifest.json, build.js, thumbnails/, telemetry/) - New unified site/build.js generates both _site/index.html (landing) and _site/gallery/index.html (gallery) with shared CSS, nav, footer - Landing page game cards are now data-driven from manifest (no drift) - Optional benchmarks section renders when site/benchmarks.json exists - npm run build:site produces the whole _site/ Directory consolidation: - character-library/ + 3d-character-library/ → assets/characters/ + assets/3d-characters/ - evals/ → tests/ (trigger files, flows, README) - docs/troubleshooting.md → TROUBLESHOOTING.md - benchmarks/ deleted (empty) All references updated across ~15 files (CLAUDE.md, skills, templates, package.json, examples). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
1.7 KiB
1.7 KiB
Flow Test 05: Improve Existing Game
Objective
Test the audit + implementation flow for improving an existing game.
Prerequisites
- An existing game (e.g.,
examples/flappy-bird/or output from flow 01) - Game has working
npm run devandnpm run build
Steps
Phase 1: Deep Audit
- Run
/improve-gameon the game directory - Skill reads ALL source files (not just package.json)
- Produces a diagnostic table with scores for each area
- Overall score reported as X/65
Phase 2: Improvement Plan
- Top 5-8 improvements listed, ranked by player impact
- Each improvement has: title, area, impact, what to do, files touched
- Asks the user which improvements to implement before proceeding
- Waits for user selection (does NOT auto-implement all)
Phase 3: Implementation
- Implements selected improvements following architecture rules
- New constants in Constants.js (zero hardcoded values)
- New events in EventBus.js with domain:action naming
- Runs
npm run buildafter each improvement - No build errors introduced
Phase 4: Verification
- Final
npm run buildsucceeds - Existing tests still pass (if present)
- Report shows before/after scores
- Files created/modified listed
Success Criteria
- All checkboxes pass
- 0 build failures in final state
- <= 2 clarifying questions
- Score improves by at least 5 points
- No existing gameplay broken
Anti-patterns
- Implementing all improvements without asking the user
- Skipping the audit and going straight to changes
- Modifying gameplay physics without being asked
- Not running build verification between improvements