mirror of
https://github.com/Donchitos/Claude-Code-Game-Studios.git
synced 2026-06-27 13:01:50 +00:00
ad540fe75d
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>
72 lines
2.2 KiB
Markdown
72 lines
2.2 KiB
Markdown
---
|
|
name: onboard
|
|
description: "Generates a contextual onboarding document for a new contributor or agent joining the project. Summarizes project state, architecture, conventions, and current priorities relevant to the specified role or area."
|
|
argument-hint: "[role|area]"
|
|
user-invocable: true
|
|
allowed-tools: Read, Glob, Grep, Write
|
|
---
|
|
|
|
When this skill is invoked:
|
|
|
|
1. **Read the CLAUDE.md** for project overview and standards.
|
|
|
|
2. **Read the relevant agent definition** from `.claude/agents/` if a specific
|
|
role is specified.
|
|
|
|
3. **Scan the codebase** for the relevant area:
|
|
- For programmers: scan `src/` for architecture, patterns, key files
|
|
- For designers: scan `design/` for existing design documents
|
|
- For narrative: scan `design/narrative/` for world-building and story docs
|
|
- For QA: scan `tests/` for existing test coverage
|
|
- For production: scan `production/` for current sprint and milestone
|
|
|
|
4. **Read recent changes** (git log if available) to understand current momentum.
|
|
|
|
5. **Generate the onboarding document**:
|
|
|
|
```markdown
|
|
# Onboarding: [Role/Area]
|
|
|
|
## Project Summary
|
|
[2-3 sentence summary of what this game is and its current state]
|
|
|
|
## Your Role
|
|
[What this role does on this project, key responsibilities, who you report to]
|
|
|
|
## Project Architecture
|
|
[Relevant architectural overview for this role]
|
|
|
|
### Key Directories
|
|
| Directory | Contents | Your Interaction |
|
|
|-----------|----------|-----------------|
|
|
|
|
### Key Files
|
|
| File | Purpose | Read Priority |
|
|
|------|---------|--------------|
|
|
|
|
## Current Standards and Conventions
|
|
[Summary of conventions relevant to this role from CLAUDE.md and agent definition]
|
|
|
|
## Current State of Your Area
|
|
[What has been built, what is in progress, what is planned next]
|
|
|
|
## Current Sprint Context
|
|
[What the team is working on now and what is expected of this role]
|
|
|
|
## Key Dependencies
|
|
[What other roles/systems this role interacts with most]
|
|
|
|
## Common Pitfalls
|
|
[Things that trip up new contributors in this area]
|
|
|
|
## First Tasks
|
|
[Suggested first tasks to get oriented and productive]
|
|
|
|
1. [Read these documents first]
|
|
2. [Review this code/content]
|
|
3. [Start with this small task]
|
|
|
|
## Questions to Ask
|
|
[Questions the new contributor should ask to get fully oriented]
|
|
```
|