naming-quality

Review existing file, module, and API names for clarity, longevity, and domain terminology alignment. This process yields durable alternatives that reduce churn and prevent drift across code, docs, and product surfaces.

Durable naming is the practice of choosing clear, stable names that align with domain terminology across code and docs. It matters because inconsistent naming causes confusion and drift, degrading overall code quality and maintainability.

Rename user-facing product labels by evaluating scope and cross-system risk before making changes. This structured approach provides rationale for alternatives, ensuring terminology remains consistent across code, APIs, and documentation surfaces.

Yes, you can get naming recommendations for both internal code and user-facing copy. The guidance covers files, modules, APIs, routes, and product labels, proposing durable alternatives that align terminology across all surfaces.

You should review existing names for terminology alignment and longevity when you need to name or rename files, modules, APIs, fixtures, routes, or environment labels. This prevents future naming churn and maintains cross-system consistency.