onboard

Generate role-focused onboarding documents from project documentation and directories.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/polsegu/Claude-Code-Game-Dev --skill onboard-polsegu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: onboard
Source: https://github.com/polsegu/Claude-Code-Game-Dev/tree/main/.claude/skills/onboard
Command: npx skills add https://github.com/polsegu/Claude-Code-Game-Dev --skill onboard-polsegu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a fast, contextual summary to onboard a new contributor or agent by extracting project state, architecture, conventions, and current priorities tailored to a specific role or area.

Core Features & Use Cases

  • Contextual Summaries: Reads CLAUDE.md, relevant agent definitions, recent changes, and role-specific directories to produce a concise onboarding document.
  • Role-Focused Scanning: Targets directories like src/, design/, design/narrative/, tests/, and production/ depending on the specified role to surface only relevant information.
  • Actionable First Steps: Produces recommended first tasks, key files to read, common pitfalls, and suggested dependencies or collaborators.
  • Use Case: When a new programmer joins a game project, generate a one-page onboarding that summarizes architecture, coding conventions, key files, and the top three starter tasks.

Quick Start

Create an onboarding document for the role programmer that summarizes the project state, key directories and files, conventions, current sprint context, and three suggested first tasks.

Frequently Asked Questions about onboard

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate role-specific onboarding documentation for a new game development contributor?

Role-focused onboarding scans target directories like src/, design/, and tests/ based on the specified role, such as programmer, designer, or QA, to surface only relevant project state and conventions.

Can I create onboarding docs for different studio roles like narrative and production?

The scan targets role-specific directories like design/narrative/ to extract relevant context and current sprint priorities for each area.

What is the best way to summarize project architecture and conventions for a new programmer?

The output is a one-page onboarding document highlighting coding conventions, key files, and suggested starter tasks.

How do I save generated onboarding documents to my project repository?

This organizes contextual summaries, recommended first tasks, and key files directly within the project structure.

Does onboarding automation work without external dependencies or components?

It reads project docs and agent definitions to compile a self-contained, role-focused markdown summary.