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
1# Onboarding: [Role/Area]
2
3## Project Summary
4[2-3 sentence summary of what this game is and its current state]
5
6## Your Role
7[What this role does on this project, key responsibilities, who you report to]
8
9## Project Architecture
10[Relevant architectural overview for this role]
11
12### Key Directories
13| Directory | Contents | Your Interaction |
14|-----------|----------|-----------------|
15
16### Key Files
17| File | Purpose | Read Priority |
18|------|---------|--------------|
19
20## Current Standards and Conventions
21[Summary of conventions relevant to this role from CLAUDE.md and agent definition]
22
23## Current State of Your Area
24[What has been built, what is in progress, what is planned next]
25
26## Current Sprint Context
27[What the team is working on now and what is expected of this role]
28
29## Key Dependencies
30[What other roles/systems this role interacts with most]
31
32## Common Pitfalls
33[Things that trip up new contributors in this area]
34
35## First Tasks
36[Suggested first tasks to get oriented and productive]
37
381. [Read these documents first]
392. [Review this code/content]
403. [Start with this small task]
41
42## Questions to Ask
43[Questions the new contributor should ask to get fully oriented]