senior-surveylisted

# Senior Code Survey Use this skill before writing any new file under `src/`. It ensures you reason like a senior engineer: identify what already exists, decide the minimum viable path, and document the decision with evidence. ## When to Use Any time you are about to call Write with a path under `src/` that does not yet exist. ## Skip When - File already exists (you are editing, not creating) - Target is under `__tests__/`, `docs/`, `scripts/` — not under `src/` - Target is a test file (`*.test.ts`, `*.spec.ts`) ## Protocol ### Step 1 — Name the target State: - Relative path: `src/<path/to/file>.ts` - Main export(s) you plan to add ### Step 2 — Run ≥3 searches Execute these (replace `<Name>` and `<keyword>` with your specific terms): ```bash grep -r "export.*<Name>" src/ --include="*.ts" -l grep -r "<keyword>" src/ --include="*.ts" -l ls src/<sibling-directory>/ ``` Capture the results (file:line hits or `(no match)`). ### Step 3 — Classify Choose one decision keyword: | Keyword | Meaning | | -------------------- | ------------------------------------------------------------------------ | | `refactor-applied` | Similar code found; you are extending/extracting instead of creating new | | `refactor-rejected` | Similar code found but refactoring would pollute the abstraction | | `extend` | Adding to an existing file/module rather than creating new |