gamedev-skills

Use when the development process itself needs to change — a rule keeps getting violated or worked around, an escaped bug or rework exposes a process gap, you're about to add/edit/remove a workflow rule, the rules file is bloating, or upstream tooling changed and old rules may not hold

Use when setting up or driving the Claude Code toolchain for Godot game development — deciding which superpowers skill applies at each stage, calling the godot-mcp-enhanced MCP server (screenshots, game bridge, audio, editor), or keeping the toolchain current after upstream updates

Use when writing or debugging automated tests for Godot 4 projects — headless tests hang or time out with no output, animation/physics timing asserts fail intermittently, new class_name types are "not found", a freed object crashes a typed parameter, or the test suite has grown slow

Use when an AI agent is dispatching, briefing, or budgeting subagents across a long project — repeated dispatches drift or re-paste boilerplate, you're picking model tiers/effort per task, subagent reports get lost or bloat context, review depth must match change risk, or main-session context is ballooning toward cost cliffs

Use when an AI agent shares a git worktree with a human whose editor is open in parallel — uncommitted human edits appear mid-session, the engine editor re-saves files as "churn", commits need landing without PRs, or commit messages / PowerShell scripts get mangled by encoding