onboard
The onboard skill generates customized onboarding documents for new contributors or agents joining a project by analyzing project context, architecture, and conventions specific to their role. Use this skill when bringing someone new into a game development project to provide structured guidance covering project summary, role responsibilities, key files, current standards, sprint context, dependencies, common pitfalls, and initial tasks.
git clone --depth 1 https://github.com/Donchitos/Claude-Code-Game-Studios /tmp/onboard && cp -r /tmp/onboard/.claude/skills/onboard ~/.claude/skills/onboardSKILL.md
## Phase 1: Load Project Context Read CLAUDE.md for project overview and standards. Read the relevant agent definition from `.claude/agents/` if a specific role is specified. --- ## Phase 2: Scan 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 Read recent changes (git log if available) to understand current momentum. --- ## Phase 3: Generate 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] ``` --- ## Phase 4: Save Document Present the onboarding document to the user. Ask: "May I write this to `production/onboarding/onboard-[role]-[date].md`?" If yes, write the file, creating the directory if needed. --- ## Phase 5: Next Steps Verdict: **COMPLETE** — onboarding document generated. - Share the onboarding doc with the new contributor before their first session. - Run `/sprint-status` to show the new contributor current progress. - Run `/help` if the contributor needs guidance on what to work on next.
The Accessibility Specialist ensures the game is playable by the widest possible audience. They enforce accessibility standards, review UI for compliance, and design assistive features including remapping, text scaling, colorblind modes, and screen reader support.
Brownfield onboarding — audits existing project artifacts for template format compliance (not just existence), classifies gaps by impact, and produces a numbered migration plan. Run this when joining an in-progress project or upgrading from an older template version. Distinct from /project-stage-detect (which checks what exists) — this checks whether what exists will actually work with the template's skills.
The AI Programmer implements game AI systems: behavior trees, state machines, pathfinding, perception systems, decision-making, and NPC behavior. Use this agent for AI system implementation, pathfinding optimization, enemy behavior programming, or AI debugging.
The Analytics Engineer designs telemetry systems, player behavior tracking, A/B test frameworks, and data analysis pipelines. Use this agent for event tracking design, dashboard specification, A/B test design, or player behavior analysis methodology.
Creates an Architecture Decision Record (ADR) documenting a significant technical decision, its context, alternatives considered, and consequences. Every major technical choice should have an ADR.
Validates completeness and consistency of the project architecture against all GDDs. Builds a traceability matrix mapping every GDD technical requirement to ADRs, identifies coverage gaps, detects cross-ADR conflicts, verifies engine compatibility consistency across all decisions, and produces a PASS/CONCERNS/FAIL verdict. The architecture equivalent of /design-review.
Guided, section-by-section Art Bible authoring. Creates the visual identity specification that gates all asset production. Run after /brainstorm is approved and before /map-systems or any GDD authoring begins.
The Art Director owns the visual identity of the game: style guides, art bible, asset standards, color palettes, UI/UX visual design, and the art production pipeline. Use this agent for visual consistency reviews, asset spec creation, art bible maintenance, or UI visual direction.