project-onboarding
Onboard Codex to crashwoc-decomp. Use when working in this repository and Codex needs the project layout, build and verification commands, generated-file rules, helper tooling, or the standard workflow for Crash Bandicoot: The Wrath of Cortex GameCube decompilation.
Best use case
project-onboarding is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Onboard Codex to crashwoc-decomp. Use when working in this repository and Codex needs the project layout, build and verification commands, generated-file rules, helper tooling, or the standard workflow for Crash Bandicoot: The Wrath of Cortex GameCube decompilation.
Teams using project-onboarding should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/project-onboarding/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How project-onboarding Compares
| Feature / Agent | project-onboarding | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Onboard Codex to crashwoc-decomp. Use when working in this repository and Codex needs the project layout, build and verification commands, generated-file rules, helper tooling, or the standard workflow for Crash Bandicoot: The Wrath of Cortex GameCube decompilation.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Project Onboarding ## Quick Start - Read [../../../AGENTS.md](../../../AGENTS.md) first for the repo-level summary. - Read [../../../.github/copilot-instructions.md](../../../.github/copilot-instructions.md) when the active agent is GitHub Copilot. - If generated build files may be stale or missing, run `python configure.py --version GCBE7D --toolchain prodg35`. - Use `python tools/ai_lookup_symbol.py ...`, `python tools/ai_lookup_unit.py ...`, or `python tools/ai_context.py ...` before manual repo-wide searching. - Use `python tools/ai_match_plan.py <unit-or-path>` when the task starts from a file or unit and needs a backlog of remaining functions. ## Build Flow Use these commands as the default local workflow: - `python configure.py --version GCBE7D --toolchain prodg35` - `ninja` - `ninja progress` - `ninja baseline` - `ninja changes` - `python tools/changes_fmt.py build/GCBE7D/report_changes.json` For automation, never use interactive `objdiff-cli diff` sessions. Prefer the report-based commands above, or direct `objdiff-cli report changes ... -o <file>` when you need raw objdiff output. For narrow iteration, build the single object or context target instead of the whole project: - `ninja build/GCBE7D/src/<unit>.o` - `ninja build/GCBE7D/src/<unit>.ctx` ## Working Rules - Edit checked-in source files such as `config/GCBE7D/splits.txt` and `config/GCBE7D/config.yml`, not generated outputs. - Treat `config/GCBE7D/symbols.txt` as authoritative for validated symbol names. - Treat `src/dump_alphaNGCport_DWARF.txt` as a clue source when validated data is missing. - Prefer repo-local helper scripts over ad hoc parsing when a script already exists for the job. ## References - Read [references/repo-map.md](references/repo-map.md) for the important project files and what they mean. - Read [references/build-flow.md](references/build-flow.md) for configure, build, and regression commands.
Related Skills
task-pack
Generate and run provider-neutral decompilation task packs in crashwoc-decomp. Use when an agent should turn a unit, function, or decomp.me bundle into a self-contained task pack and run it against any backend (print, copilot, codex, claude, aider, or gemini).
symbol-lookup
Lookup symbols, addresses, units, and match metadata in crashwoc-decomp. Use when Codex needs to map a function or global to config/GCBE7D/symbols.txt, split ownership, build/GCBE7D/report.json, or fallback DWARF lines.
split-maintenance
Maintain config/GCBE7D/splits.txt and its generated companions. Use when Codex needs to add or replace unit ranges, import split data from the backup file, seed split ownership, or reason about normalized unit names like ai_1.c and GBA_1.c.
match-workflow
Drive symbol-to-verification matching work in crashwoc-decomp. Use when Codex needs to take a symbol or unit from lookup through context gathering, narrow local builds, and final regression checks.
ghidra-workflow
Query the local Crash WOC Ghidra project through analyzeHeadless.bat for function lookup, decompilation, disassembly, and datatype inspection.
build-triage
Diagnose build failures, progress regressions, and single-object compile problems in crashwoc-decomp. Use when Codex needs to narrow a failing target, inspect report data, or summarize changes from ninja changes.
agent-orchestration
Orchestrate one Crash WOC unit or one function with Copilot using the repo-local helper scripts, prompt entry points, and a one-writer-at-a-time workflow.
decomp-match
Autonomous matching-decompilation workflow for Crash WOC GameCube units. Use when the agent needs to decomp-match functions in a C source file.
plan-creating-project-plans
Comprehensive project planning standards for plans/ directory including folder structure (ideas.md, backlog/, in-progress/, done/), stage-aware naming convention (backlog/done use YYYY-MM-DD__identifier/, in-progress uses identifier/ with no date prefix), five-document file organization (README.md, brd.md, prd.md, tech-docs.md, delivery.md for multi-file default; single README.md for trivially-small single-file exception), BRD/PRD content-placement rules, Gherkin acceptance criteria, and the mandatory structured multiple-choice grilling gates (pre-write and post-write) for resolving design decisions with the user. Essential for creating structured, executable project plans.
LinkedIn Auto-Commenter — Project Standards
## Comment Quality
~aod-project-plan
Validates architecture documentation completeness by checking for technology stack, API specifications, database schema, security architecture, and alignment with feature specification. Use this skill when you need to check if plan.md is complete before implementation, validate architecture documentation, or review technical plans for completeness.
django-project-setup
Set up a new Django 6.0 project with modern tooling (uv, direnv, HTMX, OAuth, DRF, testing). Use when the user wants to create a Django project from scratch with production-ready configuration.