repo-geolisted

# repo-geo Make a repository accurately findable and citable by AI search systems. Audit first, report, get confirmation, then edit. ## Core principle Every change must make it **easier for a model to accurately understand what already exists**. Never add content that restates information already on the page. If a proposed change does not add new information, drop it. Ranking tricks, padding, and score-chasing are out of scope and actively harmful. ## Workflow Run these phases in order. Do not skip to editing. ### Phase 1 — Detect repo type Inspect the repo root and classify into exactly one of: - **backend** — no site output. Signals: `pyproject.toml`, `go.mod`, `Cargo.toml`, `package.json` without a bundler/framework, presence of `openapi.*` / `main.go` / `src/lib`, absence of `index.html` / `public/`. - **fullstack** — both. Signals: `next.config.*`, `nuxt.config.*`, `remix.config.*`, or a `web/` + `server/` split, or `package.json` with both a server framework and a UI framework. - **frontend** — site or client app. Signals: `index.html`, `public/`, `dist/`, `vite.config.*`, static site generators (Hugo, Astro, Docusaurus, VitePress). State the classification and the evidence you used before continuing. If ambiguous, ask. Also determine: is there a **published site** (a domain this repo deploys to)? Site-level items only apply if yes. Read `references/repo-types.md` for the per-type action table. ### Phase 2 — Audit (read-only) Run the audit script: ```bash p