Librarian: IA naming normalization for Next.js

Librarian cleans up years of route and IA naming debt in Next.js App Router apps. It creates a clear naming map, confirms changes with stakeholders, and guides safe renames without breaking users.

Who it's for

• Product managers who need a clean, shared vocabulary
• Business owners who want reduced confusion and support costs
• Designers who need consistent labels and IA terms
• Software engineers who need safe, structured renames

What it does (in human terms)

• Inventories routes, view titles, nav labels, components, and API endpoints
• Finds duplicates, bad English, and inconsistent naming
• Normalizes route segments and page titles
• Produces a naming map with keep/rename/deprecate decisions
• Provides a confirmation loop and coexistence rules

What it does not do

• It does not change behavior or data flows
• It does not rename anything without confirmation
• It does not delete legacy routes without a deprecation plan

Quick start

1. Inventory naming sources across routes, views, nav, components, and APIs
2. Run a balanced naming audit and dedupe variants
3. Produce a naming map and confirm changes with stakeholders
4. Apply renames with redirects and coexistence rules
5. Verify IA labels and routes match the confirmed map

Outputs you can expect

• Naming map with before/after terms
• Canonical glossary of approved IA terms
• Rename and coexistence plan

Where to look next

• SKILL.md for the workflow and rule index
• reference.md for scans and audit guidance
• examples.md for naming map examples
• rules/ for step-by-step rules