Patpat Game Builder

Before following this skill, apply the skill state and mutation gate.

Work in the user's actual game project and conventions. For a new feature, guide the work from brief to runnable slice; for existing projects, load only the applicable playbooks. Verify requested rules and player-facing behavior on the target runtime when available; name any missing proof. Keep this entry point short: load the primary playbook and only the conditional workflows and matrix rows that apply.

Read gameplay contract, player feedback, smallest safe change, preserve safety, and proof over proxy. For architecture, security, persistence, cross-cutting, or delivery risk, read the operating protocol in full. Do not load the router.

Choose the workflow

• For a new game or an end-to-end gameplay feature, follow build a playable slice.
• For a gameplay defect found while building that slice, follow diagnose gameplay behavior. Route an isolated existing defect through patpat-debug.
• To prove the result on the player's interface, follow verify a playthrough.
• When the user requests visual direction or polish, also follow visual iteration. A visual pass is not implied by every gameplay request.
• Read the gameplay validation matrix to select relevant checks; skip rows outside the requested scope.

Keep the work Patpat-native

• Inspect and change the user's target project. Never replace it with a throwaway or canary game to stand in for the requested work.
• Detect and use the project's actual engine, version, launcher, input map, assets, and test conventions. Do not require a particular engine, CLI, MCP, plugin, agent role, or reference-image set.
• Preserve the user's language and design intent. A request inspired by an existing game permits broad mechanic inspiration, not copying its code, identity, art, audio, levels, or presentation.
• Do not use a build, screenshot, or rule test as a substitute for an actual playthrough when player behavior is claimed.
• Keep playable, rule-correct, visual, performance, and release claims separate. Report only the gates the request and evidence cover.
• Do not publish, upload, buy assets, create accounts, or enable online services without explicit authority.

Proof closure

Define the five-field proof contract before any mutation. Close mutating work with:

• Always: patpat-verify, using authoritative evidence.
• When required: patpat-review for delivery intent, auth/security/billing/secrets, architecture or cross-cutting scope, durable-run LEARN or REPORT, land/merge, or another operating-protocol review gate.

For clear, bounded, reversible local work with none of those review requirements, proceed from verification to REPORT without independent review.