/ Directory / Playground / Claude-Code-Game-Studios
← All servers ↗ GitHub
● Community Donchitos ⚡ Instant

Claude-Code-Game-Studios

by Donchitos · Donchitos/Claude-Code-Game-Studios

49 agents + 72 workflow skills mirroring a real game studio — turn Claude Code into a mini dev team.

Claude-Code-Game-Studios simulates a full game dev studio as a skills bundle: designers, programmers, artists, QA, audio — plus workflows for sprint planning, playtests, bug triage. Made for indie devs who want process without hiring a team. Opinionated but framework-flexible (Godot, Unity, Unreal, custom engines).

▶ Watch demo 📦 Install 💡 Use Cases

Why use it

Key features

Live Demo

What it looks like in practice

ready

Install

Author repository · Claude Skills documentation

Use Cases

Real-world ways to use Claude-Code-Game-Studios

Run a 1-week sprint on your indie game

👤 Solo / 2-person indie teams ⏱ ~45 min intermediate

When to use: You're making a game solo and discipline is what's failing, not ideas.

Flow
  1. Plan
    Use game-studios. I'm solo-devving a platformer in Godot. Plan this week's sprint — here's the GDD: <brief>✓ Copied
    → Sprint with tasks in role buckets (design/code/art/audio), sized
  2. Daily standup
    What should I do today to hit the sprint goal? What can slip?✓ Copied
    → Prioritized day plan with slip allowance
  3. Retro
    Sprint done. What slipped? What to carry over? What to change next sprint?✓ Copied
    → Honest retro with specific improvements

Outcome: A game in motion with cadence you can sustain.

Pitfalls
  • Over-planning for a solo dev — Use the 1-week cadence, skip the enterprise workflows
Combine with: filesystem

Run a structured playtest and synthesize feedback

👤 Indie devs pre-Early-Access ⏱ ~60 min intermediate

When to use: You just ran 5 playtests and have 5 video recordings + notes to make sense of.

Prerequisites
  • Playtest artifacts — Notes, timestamps, transcripts in /playtests/
Flow
  1. Ingest
    Use game-studios/playtest. Ingest /playtests/session-*/ and tag feedback by type (bug, UX, mechanic, audio).✓ Copied
    → Tagged feedback inventory
  2. Cluster
    Cluster by feedback theme. What came up across multiple sessions?✓ Copied
    → Cross-session patterns, not per-person complaints
  3. Prioritize
    For each theme: frequency, severity, effort to fix. Feed into next sprint.✓ Copied
    → Prioritized changes ready to plan

Outcome: Next sprint's work driven by real player data, not hunches.

Pitfalls
  • Treating one playtester's strong opinion as general — Theme needs to appear in ≥2 sessions to qualify

Combinations

Pair with other MCPs for X10 leverage

game-studios-skill + filesystem

Keep the whole studio context in /studio/ folder

Organize /studio/sprints/, /studio/playtests/, /studio/retros/.✓ Copied
game-studios-skill + github

Issues per task, milestones per sprint

Create GitHub issues from the sprint plan; make a milestone for this sprint.✓ Copied

Tools

What this MCP exposes

ToolInputsWhen to callCost
sprint_plan brief, duration Start of each sprint 0
role_review role, artifact Gut-check before shipping 0
playtest_synthesize sessions[] After playtests 0
retro sprint_notes End of each sprint 0

Cost & Limits

What this costs to run

API quota
N/A
Tokens per call
Plans are cheap; role-review of big artifacts (levels, art) can be expensive
Monetary
Free (MIT)
Tip
Don't ask every role to review every artifact — pick who's relevant

Security

Permissions, secrets, blast radius

Credential storage: None
Data egress: None

Troubleshooting

Common errors and fixes

Plans feel AAA-studio, not indie

Pin your scope explicitly: "solo dev, 1 hour/day, 3 month timeline"

Role advice conflicts

That's realistic — pick the one that serves the next milestone

Skill doesn't know Godot specifics

Prepend Godot docs or relevant GDScript examples; it's engine-agnostic by default

Alternatives

Claude-Code-Game-Studios vs others

AlternativeWhen to use it insteadTradeoff
Notion / Trello boardYou want project management without LLM synthesisNo playtest synthesis, no role critique
game-specific communitiesYou want human feedback on designSlow, and people are biased by their own games

More

Resources

📖 Read the official README on GitHub

🐙 Browse open issues

🔍 Browse all 400+ MCP servers and Skills

Continue exploring

Related tools and workflows

Choose another guide for your workflow, or explore a collection.

Shared context · game

Scenario Agent Skills

Create images, game assets, textures, video, audio, and consistent characters with Scenario’s skills and its MCP server.

Skill

Browse all topic collections → · See 29 new official additions →