AI workflows
A Practical Handoff Template for Game Agent Tasks
Hand off game development work with a specific outcome, reproducible context, bounded ownership, and evidence another developer can verify.
The AI Games Kit blog
Practical game development guides for the work between your first idea and your next release.
Unity. Browser games.
AI-assisted workflows.
Start with the next useful step.
Latest guide Publishing
Turn a post-release game bug into a reproducible incident with version evidence, player-impact priorities, a bounded fix, and recovery checks.
Field notes / workflow
Turn a task into a repeatable process.
AI workflows
Hand off game development work with a specific outcome, reproducible context, bounded ownership, and evidence another developer can verify.
AI workflows
Use a compact resource ledger to test game economy pacing, purchase choices, retries, and progression without guessing at a universal balance formula.
AI workflows
Separate unclear rules, execution demands, and recovery cost in a focused difficulty playtest, using controlled variants and observable acceptance checks.
AI workflows
Turn conflicting playtest notes into reproducible observations, focused hypotheses, and a small change plan you can validate with the next game build.
AI workflows
Plan an evidence-first AI game development workflow: establish a baseline, make bounded changes, playtest the result, and keep a clear release decision.
Field notes / unity
Investigate, improve, and ship your Unity project.
Unity
Review a Unity release candidate using an identified artifact, change-based test coverage, upgrade checks, and an explicit decision about unresolved risks.
Unity
Trace Unity settings from stored values to runtime behavior, define defaults and apply rules, and test persistence without erasing unrelated player progress.
Unity
Compare Unity Editor and player behavior using matching routes, real player logs, build configuration, and one controlled hypothesis at a time.
Unity
Define Unity performance budgets around player scenarios, comparable captures, and explicit release decisions instead of a single unexplained average frame rate.
Unity
Trace Unity Web loading failures through the actual request, response headers, release files, and startup state before changing compression or game code.
Unity
Plan Unity asset moves around metadata, path-based loading, and assembly boundaries, then verify each small batch without mixing cleanup with behavior changes.
Unity
Distinguish Unity memory growth from expected caching, compare equivalent snapshots, and trace retained resources to the system responsible for their lifetime.
Unity
Trace a missing or duplicated Unity input through device state, bindings, action ownership, and gameplay gates before changing the control scheme.
Unity
Review Unity prefab overrides by intent and ownership, choose the correct apply target, and test the instances that should change alongside those that should not.
Unity
Plan a Unity save migration with versioned fixtures, explicit defaults, interruption tests, and recovery rules that preserve the original player data.
Unity
Trace duplicate listeners, persistent objects, and stale session state in Unity restart bugs, then verify the fix across repeat sessions and a built player.
Unity
Investigate missing Unity scripts without discarding serialized state: identify the affected owner, trace asset identity, and verify a narrow recovery.
Unity
Investigate a large Unity WebGL build with a repeatable checklist for transferred bytes, asset costs, code stripping, compression headers, and first-play testing.
Unity
Audit a Unity project without turning it into a risky cleanup: reproduce the build, check asset references, record technical risks, and prioritize the next fix.
Field notes / browser
Build for the browser and the people playing in it.
Browser games
Observe a new player's first browser game session and turn confusion into specific onboarding changes with clear tasks, evidence, and acceptance checks.
Browser games
Verify browser game resizing with a clear policy for layout, rendering resolution, pointer mapping, orientation changes, and uninterrupted progress.
Browser games
Protect browser game progress with a focused save test covering failed writes, invalid data, version changes, multiple tabs, and honest recovery messages.
Browser games
A practical audio startup workflow for browser games: distinguish permission from loading failures and verify mute, resume, and repeated scene entry.
Browser games
Build a repeatable tab-resume test for browser games, covering simulation time, held input, audio, delayed requests, and safe return to play.
Browser games
Trace missed taps, stuck drags, and duplicate actions with a browser game touch checklist covering coordinates, cancellation, and real-device checks.
Browser games
Find the real cause of browser-game loading delays, stutter, and memory growth with a repeatable profiling checklist and a focused AI-agent handoff.
Field notes / publishing
Prepare your game for its next destination.
Publishing
Turn a post-release game bug into a reproducible incident with version evidence, player-impact priorities, a bounded fix, and recovery checks.
Publishing
Build a CrazyGames release checklist around the correct launch stage, tested export, platform preview, and concrete evidence for unresolved integration risks.
Publishing
Prepare a specific Poki candidate build with current requirements, Inspector evidence, lifecycle checks, and a clear release decision without guessed SDK calls.
Publishing
Check a browser-game release artifact for loading, input, audio, saves, portal integration, and recovery before submitting the exact tested build.