2EU5/devkit

Claude Code plugin for game dev workflows.
| Skill | Command | What it does |
|-------|---------|--------------|
| ship | /studio:ship [auto] [digest] [task] | Unity C# loop: takes Linear Backlog issues, implements them in the Unity Editor, verifies, commits and pushes. Asks you when it needs you; with auto it never asks and decides itself. With digest, or when the project has no issues yet but has a GDD, it runs digest on the GDD first. |
| gdd | /studio:gdd [idea or GDD] | Interviews you about a game idea, then writes or updates a game design document. |
| audit | /studio:audit | Audits a skill, plan, design or doc and gives a checked, prioritized fix list. Not for code diffs (use code-review). |
| burst | /studio:burst [goal] or "give me N options" | Makes N distinct creative or strategic options (logos, names, copy, layouts, plans), scores each on a goal-based rubric, and picks a winner with a next step. |
| council | /studio:council or "help me decide between A or B" | Stress-tests a decision with a fixed council (Contrarian, First-Principles Thinker, Expansionist, Outsider, Executor) who debate it, then synthesizes tradeoffs and next steps. |
| verify | /studio:verify [issue or criteria] | Verifies Unity work in the Editor: runs EditMode and PlayMode tests, checks the console, screenshots visual work, and maps each acceptance criterion to pass, fail or needs user with evidence. |
| digest | /studio:digest | Breaks a GDD or plan doc into Linear milestones and issues in build order, with acceptance criteria and sizes, ready for ship. Also splits one large issue into sub-issues. |
| handoff | /studio:handoff [next focus] | Compacts the current conversation into a handoff doc in your OS temp folder so a fresh session can pick up the work. |
Install
Ship requirements
Ship checks all of these at startup and stops if any is missing.
- **Skills:** caveman, ponytail:ponytail (ponytail plugin), unity:unity-cli (Unity plugin).
- **Linear MCP** connected.
- **Unity Editor** open and reachable through a Unity MCP server or the Unity CLI.
- **Permission mode** auto or bypass, so permission prompts don't stall the run (required in auto mode).
- **Clean git working tree** with an origin remote. Work is committed to the branch that's checked out.
- **Unity .gitignore** that ignores Library/, Temp/, Logs/ and UserSettings/.
- **Linear team/project** named in the project's CLAUDE.md (otherwise ship asks once at startup).
Linear setup
- Ship creates team labels Needs Input and autopilot if missing.
- It works Backlog issues that are unassigned or assigned to you, milestone by milestone in project order, oldest first within each milestone; issues without a milestone go last. Statuses are picked by type (backlog / unstarted / started / completed), so custom names are fine.
- Because the Linear MCP acts as you, the autopilot label marks issues ship started. Started issues without it are left alone.