mirror of
https://github.com/Donchitos/Claude-Code-Game-Studios.git
synced 2026-06-27 13:01:50 +00:00
f36494e70c
Model tier assignment: - model: haiku → help, sprint-status, story-readiness, scope-check, project-stage-detect, changelog, patch-notes, onboard (read-only/format) - model: opus → review-all-gdds, architecture-review, gate-check (multi-doc synthesis, high-stakes verdicts) PostCompact hook: - New .claude/hooks/post-compact.sh — fires after compaction, reminds Claude to re-read production/session-state/active.md to restore context - Registered in settings.json between PreCompact and Stop Parallel Task spawning: - review-all-gdds: Phase 2 (consistency) and Phase 3 (design theory) now explicitly instructed to spawn as parallel Task agents simultaneously Error Recovery Protocol: - Standard BLOCKED-handling section added to: review-all-gdds, architecture-review, dev-story, team-combat, team-qa, team-narrative, team-level, team-ui, team-audio, team-release, team-polish - Pattern: surface blocker → assess dependencies → offer 3 options via AskUserQuestion → always produce partial report Coordination rules: - Added Model Tier Assignment table with routing rationale - Added Subagents vs Agent Teams section (experimental agent teams docs) - Added Parallel Task Protocol (when/how to spawn parallel agents) Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
73 lines
2.2 KiB
Markdown
73 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
|
|
model: haiku
|
|
---
|
|
|
|
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]
|
|
```
|