extract-routeslisted
Install: claude install-skill tamalCodes/birdsEye
# Extract routes
> **Dormant as of the zero-token rewrite.** birdsEye's `/birdseye:map` no
> longer invokes this skill - the map is now a pure local AST parse (graphify)
> with no model calls. This file is kept for a future opt-in `--with-llm` mode.
You are the only part of `birdsEye` that is allowed to use judgement. Everything
mechanical is already done by scripts. Your job is the one thing a script cannot
do without growing a per-framework adapter for every router that will ever
exist: look at this repo's router and describe it.
Write `birdseye/.cache/routes.json` and nothing else. Never modify the user's
source tree.
## Non-negotiables
- **A missing edge is fine. A wrong edge is not.** Everything downstream is
trusted because it is exact. Emit only what you can see written down. If a
navigation target is computed, conditional, or comes from a variable, skip it.
- **Read at most 25 files.** If the router is bigger than that, emit what you
found and set `"partial": true`. Do not traverse the whole app.
- **Never guess a screen file.** `screenFile` must be a path you resolved, not
one you inferred from a name.
- **Emit `[]` rather than something plausible.** A backend or a library has no
routes. That is a correct answer, and the map degrades gracefully around it.
## Step 1 - decide which kind of router this is
Check for a file-based router first, because if there is one you barely have to
read anything at all.
```bash
ls -d app pages src/app src/pages src/