Choose semantically clear and consistent names across related elements in your codebase. Names should convey their purpose without requiring additional context or explanation, and related elements should follow consistent naming patterns. Key principles: - Use descriptive names that clearly indicate functionality (e.g., `folder` vs `directory` where `folder` aligns with native behavior) - Maintain consistency between related elements like filenames and display names (e.g., if changing "Icon Position" to "Icon Placement", also update the corresponding filename from `icon-position.tsx` to `icon-placement.tsx`) - Avoid ambiguous or auto-generated identifiers (e.g., prefer `#inputsearch` over `#inputsearch-1`) - Follow consistent ordering patterns for API documentation (alphabetical for properties, then methods) Example: ```jsx // Good: Semantic and consistent naming Icon Placement // Bad: Inconsistent between filename and display Icon Placement ``` This ensures code is self-documenting and maintainable, reducing confusion for developers who encounter the code without prior context.