/ الدليل / الملعب / Claude-Code-Game-Studios
← كل الخوادم ↗ GitHub
● مجتمع Donchitos ⚡ فوري

Claude-Code-Game-Studios

بواسطة 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).

▶ شاهد العرض 📦 التثبيت 💡 حالات الاستخدام

لماذا تستخدمه

الميزات الأساسية

عرض مباشر

كيف يبدو في الممارسة

جاهز

التثبيت

اختر العميل

~/Library/Application Support/Claude/claude_desktop_config.json  · Windows: %APPDATA%\Claude\claude_desktop_config.json
{
  "mcpServers": {
    "game-studios-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/Donchitos/Claude-Code-Game-Studios",
        "~/.claude/skills/Claude-Code-Game-Studios"
      ],
      "_inferred": true
    }
  }
}

افتح Claude Desktop → Settings → Developer → Edit Config. أعد التشغيل بعد الحفظ.

~/.cursor/mcp.json · .cursor/mcp.json
{
  "mcpServers": {
    "game-studios-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/Donchitos/Claude-Code-Game-Studios",
        "~/.claude/skills/Claude-Code-Game-Studios"
      ],
      "_inferred": true
    }
  }
}

يستخدم Cursor نفس مخطط mcpServers مثل Claude Desktop. إعدادات المشروع أولى من الإعدادات العامة.

VS Code → Cline → MCP Servers → Edit
{
  "mcpServers": {
    "game-studios-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/Donchitos/Claude-Code-Game-Studios",
        "~/.claude/skills/Claude-Code-Game-Studios"
      ],
      "_inferred": true
    }
  }
}

انقر على أيقونة MCP Servers في شريط Cline الجانبي، ثم "Edit Configuration".

~/.codeium/windsurf/mcp_config.json
{
  "mcpServers": {
    "game-studios-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/Donchitos/Claude-Code-Game-Studios",
        "~/.claude/skills/Claude-Code-Game-Studios"
      ],
      "_inferred": true
    }
  }
}

نفس الصيغة مثل Claude Desktop. أعد تشغيل Windsurf لتطبيق التغييرات.

~/.continue/config.json
{
  "mcpServers": [
    {
      "name": "game-studios-skill",
      "command": "git",
      "args": [
        "clone",
        "https://github.com/Donchitos/Claude-Code-Game-Studios",
        "~/.claude/skills/Claude-Code-Game-Studios"
      ]
    }
  ]
}

يستخدم Continue مصفوفة من كائنات الخادم بدلاً من خريطة.

~/.config/zed/settings.json
{
  "context_servers": {
    "game-studios-skill": {
      "command": {
        "path": "git",
        "args": [
          "clone",
          "https://github.com/Donchitos/Claude-Code-Game-Studios",
          "~/.claude/skills/Claude-Code-Game-Studios"
        ]
      }
    }
  }
}

أضف إلى context_servers. يعيد Zed التحميل تلقائيًا عند الحفظ.

claude mcp add game-studios-skill -- git clone https://github.com/Donchitos/Claude-Code-Game-Studios ~/.claude/skills/Claude-Code-Game-Studios

أمر من سطر واحد. تحقق باستخدام claude mcp list. احذف باستخدام claude mcp remove.

حالات الاستخدام

استخدامات عملية: Claude-Code-Game-Studios

Run a 1-week sprint on your indie game

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

متى تستخدمه: You're making a game solo and discipline is what's failing, not ideas.

المتطلبات الأساسية
  • Skill installed — git clone https://github.com/Donchitos/Claude-Code-Game-Studios ~/.claude/skills/game-studios
  • GDD or design brief — Even a rough design doc is enough to anchor
الخطوات
  1. Plan
    Use game-studios. I'm solo-devving a platformer in Godot. Plan this week's sprint — here's the GDD: <brief>✓ تم النسخ
    → 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?✓ تم النسخ
    → Prioritized day plan with slip allowance
  3. Retro
    Sprint done. What slipped? What to carry over? What to change next sprint?✓ تم النسخ
    → Honest retro with specific improvements

النتيجة: A game in motion with cadence you can sustain.

المزالق
  • Over-planning for a solo dev — Use the 1-week cadence, skip the enterprise workflows
اجمعها مع: filesystem

Run a structured playtest and synthesize feedback

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

متى تستخدمه: You just ran 5 playtests and have 5 video recordings + notes to make sense of.

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

النتيجة: Next sprint's work driven by real player data, not hunches.

المزالق
  • Treating one playtester's strong opinion as general — Theme needs to appear in ≥2 sessions to qualify

التركيبات

اجمعها مع خوادم MCP أخرى لتحقيق نتائج x10

game-studios-skill + filesystem

Keep the whole studio context in /studio/ folder

Organize /studio/sprints/, /studio/playtests/, /studio/retros/.✓ تم النسخ
game-studios-skill + github

Issues per task, milestones per sprint

Create GitHub issues from the sprint plan; make a milestone for this sprint.✓ تم النسخ

الأدوات

ما يوفره هذا الـ MCP

الأداةالمدخلاتمتى تستدعيهاالتكلفة
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

التكلفة والحدود

تكلفة التشغيل

حصة API
N/A
الرموز لكل استدعاء
Plans are cheap; role-review of big artifacts (levels, art) can be expensive
التكلفة المالية
Free (MIT)
نصيحة
Don't ask every role to review every artifact — pick who's relevant

الأمان

الصلاحيات والأسرار ونطاق الأثر

تخزين بيانات الاعتماد: None
نقل البيانات الخارجي: None

استكشاف الأخطاء

الأخطاء الشائعة وحلولها

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

البدائل

Claude-Code-Game-Studios مقابل البدائل

البديلمتى تستخدمهاالمقايضة
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

المزيد

الموارد

📖 اقرأ ملف README الرسمي على GitHub

🐙 تصفح القضايا المفتوحة

🔍 تصفح أكثر من 400 خادم MCP و Skills