Naming

One list, synced from the hub. The gate naming checks what a machine can check, on push and in CI; the rest is your judgement. references/lint.md draws the line.

Before you name anything, run node .agents/skills/naming/scripts/config.mjs and read its output as the current rules: it prints references/naming.json merged with the project's overrides.

Rules

1. One word per thing, and the word comes from GLOSSARY.md. Look there first, then in existing types, DB tables and API routes. The repo's word beats the request's word.

   Good	Bad	Why
   testimonial	customerQuote	the request said "customer quotes", the repo says testimonial
   Testimonial type, testimonials table, /api/testimonials	Testimonial type, reviews table	one word per thing, everywhere
   order	purchase beside order	two words for one thing splits the search

2. No word yet? Run term-check, show the result to the user, get sign-off, then add the word to GLOSSARY.md through domain-modeling, which owns that file.