codebase-maplisted

# Orient in the code before you act on it Structural orientation - who calls this, what depends on it, what the schema really is, how far a change reaches - makes every other practice sharper: a tighter baseline, a root cause seated at the right seam, a review that knows the blast radius. One job: **get that orientation from the best map available, and never block when there isn't one.** This is one concrete instance of a general practice - on a capability gap, source the map rather than hand-roll it. better-dev ships no code-graph engine and keeps no index of its own: that's mature ecosystem territory, and a stale index you maintain by hand is worse than none. The practice ships; the structural tool underneath stays swappable. Read `.better-dev/overrides.md` first. A repo often settles this already - it may pin a code-graph skill, an LSP setup, or a convention for how the team navigates. Honor that and use what it names; don't source a second tool alongside one the project already runs. ## 1. Use the map that's already here Look for a structural source the project or host already provides, and prefer it over blind grep for "callers / dependents / schema / blast-radius" questions: - A code-graph, structural-search, or knowledge-graph skill the host or project ships - names vary by host, so detect by what it answers (callers, dependents, symbol paths), not by a name this skill can't know is installed. better-dev ships `/graphify-wrapper-query` (with `/graphify-wrappe