game-craft

Make 2D sprite animation read well: frame budgets per clip, timing and spacing, cancel windows, smears, secondary motion, wiring clips in Phaser. Generating frames is pixel-art / animated-spritesheets.

Interview the user about a fuzzy game idea, one question at a time, until it is build-ready. Skip when they already know what to build.

Critique a game's design through Schell's lenses, MDA and systems thinking, ranking findings by severity with fixes. Design-level review, not bugs or feel tuning.

Get a stalled or sprawling game project to ship: diagnose the death loop, cut to the core, set a binary finish line.

Design and tune game systems and economies: core loops, sources and sinks, cost and power curves, loot tables, progression, dominant-strategy and soft-lock audits.

Tune how a game feels — input forgiveness, movement curves, hit stop, screen shake, squash and stretch, camera and audio feel — with concrete numbers.

Build a browser game end to end from a one-line idea, plus the craft checklist that separates a tech demo from something fun.

Design in-game interfaces: HUD zoning and hierarchy, meters and numerals, menu and overlay states, touch targets and safe areas, for Phaser, Three.js or DOM.

Design levels, waves, arenas and difficulty progression: structure, pacing, teaching through geometry, guiding the eye, wave grammar for endless games.

Design a game's first minute: invisible tutorials, difficulty curves, failure and retry loops, assist modes. Use when players quit early or don't get it.

Teach the user to build browser games themselves across sessions, by building real games together. Not for building a game for them.

Build real-time 2D effects in-engine — explosions, hit sparks, trails, smoke, pickups, shockwaves, weather — with particle recipes, readability rules and mobile budgets.