Librarian
Quick start
- •Inventory naming sources across routes, views, nav, components, and APIs.
- •Run a balanced naming audit and dedupe variants.
- •Produce a naming map and confirm changes with stakeholders.
- •Apply renames with coexistence rules and redirects.
- •Verify IA labels and routes match the confirmed map.
Use when
- •A Next.js App Router project has years of renames and tech debt.
- •Route segments, view names, and nav labels are inconsistent.
- •You need a shared, confirmed vocabulary across PM/Design/Eng/Exec.
Scope
Does:
- •Normalize routes, view titles, component names, nav labels, and API names.
- •Produce a naming map and canonical glossary.
- •Provide safe coexistence and confirmation steps.
Does not:
- •Change product behavior or business logic.
- •Rename without confirmation.
- •Delete legacy routes without deprecation steps.
Rule index
- •Inventory:
rules/setup-inventory.md - •Naming audit:
rules/naming-audit.md - •Routes:
rules/routes-normalization.md - •Views/titles:
rules/views-titles.md - •Components:
rules/components-naming.md - •Navigation/IA terms:
rules/nav-ia-terms.md - •API endpoints:
rules/api-endpoints.md - •Confirmation:
rules/confirmation-loop.md - •Coexistence:
rules/coexistence-legacy.md
Output: naming map template
code
Current name: <string> Type: route | view | component | nav | api Location: <file path or route> Status: keep | rename | deprecate New name (if rename): <string> Rationale: <short reason> Owner approval: <PM/Design/Eng/Exec> Notes: <redirects, aliases, compat>
Version policy
Use the latest stable Next.js App Router conventions.