onboardlisted

# Codebase Onboarding: $ARGUMENTS ## Principle Understanding is built from **behavior first, then structure, then history** — run it before reading it, trace one real flow before mapping all of them, and let `git log` tell you what the files can't: where the work happens, who knows it, and what everyone is afraid to touch. The output is a written map, because comprehension that stays in one session's head is re-paid by every next session. Read-only on app code. The only file you create is the orientation report. ## Phase 0 — Context (works pre-bootstrap by design), and which mode you are in Read `README`/`CONTRIBUTING`/docs index if present — as *claims to verify*, not facts: docs drift, code doesn't. Then pick the mode from whether the repo carries an active profile: **Cold mode — no `.claude/PROJECT.md`.** The default, and what this skill was built for: run the full suite of phases below and build the map from zero. Don't stop for the missing profile. **Verification mode — an active `PROJECT.md` (plus `CONTEXT.md`, project rules, docs index).** The repo is already profiled, so **start from what exists, verify it against code, and report drift** rather than rediscovering from scratch: read the profile's architecture/module map and commands first, then run the phases as *checks* on those claims — does the entry point still live where the map says, does the stated test command still pass, does the traced flow still go through the layers the profile names. Every phase st