Component Naming That Scales

1. Prefer intent over implementation

Names should describe the purpose of a component, not how it happens to work today. A name like SearchResults survives refactors better than FilteredTable.

2. Use consistent vocabulary

Establish a shared glossary for product terms and reuse them across the codebase. This keeps UI, documentation, and analytics aligned and avoids duplicates.

3. Keep names short but specific

Short names are good, but they should still carry meaning. Avoid abbreviations that require context and aim for names that read well in JSX.