code-tourlisted

# Create persona-targeted, file-anchored code tours A great tour is a narrative — a story told to a specific person about what matters, why it matters, and what to do next. Every file path and line number must be real and verified. ## Persona selection Infer silently from the request: | User says | Persona | Depth | |-----------|---------|-------| | "tour for this PR" | pr-reviewer | standard | | "why did X break" / "RCA" | rca-investigator | standard | | "onboarding" / "new joiner" | new-joiner | standard | | "quick tour" / "vibe check" | vibecoder | quick | | "architecture" | architect | deep | | "security" / "auth review" | security-reviewer | standard | | (no qualifier) | new-joiner | standard | **Depth guidelines:** - Quick: 5–8 steps, high-level, 1–2 sentences per step. - Standard: 10–20 steps, full narrative, 3–5 sentences per step. - Deep: 20–40 steps, links between steps, covers edge cases and design rationale. ## Tour file format ```json { "$schema": "https://aka.ms/codetour-schema", "title": "Tour title — persona", "description": "One sentence: what this tour covers and who it's for.", "steps": [ { "file": "src/index.ts", "line": 1, "title": "Entry point", "description": "The application starts here. The `main()` function wires together the three primary subsystems..." } ] } ``` Tours live in `.tours/<name>.tour` in the repo root. **Markdown fallback.** The `.tour` JSON is the primary output. When the CodeTour exte