Files
Claude-Code-Game-Studios/.claude/docs/settings-local-template.md
Donchitos ad540fe75d Game Studio Agent Architecture — complete setup (Phases 1-7)
48 coordinated Claude Code subagents for indie game development:
- 3 leadership agents (creative-director, technical-director, producer)
- 10 department leads (game-designer, lead-programmer, art-director, etc.)
- 23 specialist agents (gameplay, engine, AI, networking, UI, tools, etc.)
- 12 engine-specific agents (Godot, Unity, Unreal with sub-specialists)

Infrastructure:
- 34 skills (slash commands) for workflows, reviews, and team orchestration
- 8 hooks for commit validation, asset checks, session management
- 11 path-scoped rules enforcing domain-specific standards
- 28 templates for design docs, reports, and collaborative protocols

Key features:
- User-driven collaboration protocol (Question → Options → Decision → Draft → Approval)
- Engine version awareness with knowledge-gap detection (Godot 4.6 pinned)
- Phase gate system for development milestone validation
- CLAUDE.md kept under 80 lines with extracted doc imports

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-13 21:04:24 +11:00

1.3 KiB

settings.local.json Template

Create .claude/settings.local.json for personal overrides that should NOT be committed to version control. Add it to .gitignore.

Example settings.local.json

{
  "permissions": {
    "allow": [
      "Bash(git *)",
      "Bash(npm *)",
      "Read",
      "Glob",
      "Grep"
    ],
    "deny": [
      "Bash(rm -rf *)",
      "Bash(git push --force *)"
    ]
  }
}

Permission Modes

Claude Code supports different permission modes. Recommended for game dev:

During Development (Default)

Use normal mode — Claude asks before running most commands. This is safest for production code.

During Prototyping

Use auto-accept mode with limited scope — faster iteration on throwaway code. Only use this when working in prototypes/ directory.

During Code Review

Use read-only permissions — Claude can read and search but not modify files.

Customizing Hooks Locally

You can add personal hooks in settings.local.json that extend (not override) the project hooks. For example, adding a notification when builds complete:

{
  "hooks": {
    "Stop": [
      {
        "matcher": "",
        "hooks": [
          {
            "type": "command",
            "command": "bash -c 'echo Session ended at $(date)'",
            "timeout": 5
          }
        ]
      }
    ]
  }
}