Prefer standard terminology

Use widely accepted industry-standard names and conventions rather than descriptive but non-standard alternatives. This improves code readability and maintainability by leveraging established terminology that developers are already familiar with.

For components, prefer established UI terminology over descriptive names:

// Avoid descriptive but non-standard names
const UiBlocker = () => { /* ... */ }

// Prefer widely accepted industry terms  
const Scrim = () => { /* ... */ }

For file extensions, use standard conventions consistently:

// Prefer standard extensions for new files
CollapseIcon.tsx  // instead of CollapseIcon.jsx

This approach reduces cognitive load for developers who can immediately understand the purpose and behavior based on familiar naming patterns from the broader development community.