Use when writing or modifying C# for a Unity project driven through the Claude Bridge — MonoBehaviour components, ScriptableObjects, Editor scripts, and gameplay code. Teaches idiomatic Unity 6 / C# patterns (MonoBehaviour lifecycle, [SerializeField] serialization, Editor vs runtime, AssetDatabase, coroutines, prefabs, physics) and the s&box/Unreal -> Unity translations, so the agent writes Unity, not another engine's patterns. Verify exact signatures live via the bridge's describe_type.
Use when building, modifying, or polishing any feature in a Unity project through the Claude Bridge — gameplay systems, components, prefabs, scene layout, materials/lighting, UI, anything that produces a visible or runtime change. Codifies the screenshot-driven iteration workflow that prevents the "guess-and-check" loop the bridge is most susceptible to, plus the hard-won Unity gotchas to bake in from day one.
Use when building a whole Unity game or a specific game SYSTEM through the Claude Bridge and you want a proven build order grounded in THIS bridge's real tools instead of guessing. A ROUTER over genre playbooks (tycoon/management, survival, fps-shooter, platformer, top-down twin-stick, tower-defense, rpg, horror, puzzle, racing) and per-system how-tos (inventory, save-load, economy-currency, health-combat, npc-ai, spawning-waves, progression-upgrades, dialogue, day-night, objectives-quests, ui-hud, audio, building-placement). Each reference names the exact bridge scaffolds/tools to compose (create_health_system, create_inventory, create_economy_wallet, create_npc_brain, create_save_system, create_player_controller, create_spawner, scatter_props, apply_atmosphere, screenshot_orbit, the editor_recompile→wait_ready→get_compile_errors trio, sim_play, set_runtime_property, invoke_method, …) and how to verify each step. Triggers on "how do I build a <genre> game", "inventory system", "save system", "economy / curre
Use when iterating on GAMEPLAY LOGIC in play mode through the Claude Bridge — tuning a method body and wanting to see the effect WITHOUT the domain-reload tax (which exits play and drops runtime state). Covers the Live Patch family (live_patch_apply / live_patch_status / live_patch_revert / live_patch_list): when it applies a method-body change to the running domain instantly, when it must fall back to a normal recompile, and how to fold it into the screenshot-driven playtest loop. EXPERIMENTAL; requires the optional com.lousputthole.livepatch package.
Use when the user asks for a whole playable game in one go through the Claude Bridge for Unity — "make me a first-person game", "scaffold a game", "give me something I can press Play on". Orchestrates the bridge's gameplay scaffolds (create_player_controller / create_objective_system / create_game_manager / create_health_system / create_pickup / create_trigger_zone + the primitives, colliders, camera, and set_component_reference wiring) into a first-person starter you can enter Play mode in and actually move around, see a level, and win or lose. Handles the generate→recompile→place sequencing and the screenshot verify loop.
First-run onboarding for the Claude Bridge for Unity. Run when a user first connects the bridge or asks how to get started — it verifies the connection (bridge_status), reports the project + Unity version, recommends a first move, and points to help + feedback. Keep it warm and brief.