Domain-Focused Naming

What problem does it solve?

This Skill eliminates confusing, misleading, or quickly outdated names that expose implementation details, temporal context, or unnecessary design patterns. It ensures code names clearly communicate their purpose within the business domain, making the codebase more intuitive and maintainable.

Core Features & Use Cases

• Problem-Oriented Naming: Guides you to name variables, functions, and classes based on what they represent in the problem domain (e.g., User, Order), not how they are implemented (e.g., ZodValidator, JSONParser).
• Avoid Temporal Context: Prevents names from including "New", "Legacy", "Improved", or "Unified" which quickly become stale and misleading.
• Hide Implementation Details: Encourages abstracting away technical specifics like library names, protocols, or internal data formats from public-facing names.
• Use Case: Instead of naming a class ImprovedZodConfigValidator, this skill guides you to simply name it ConfigValidator, focusing on its domain purpose rather than its implementation or history.

Quick Start

Review the attached code snippet. Identify any names that expose implementation details, temporal context, or unnecessary pattern names. Suggest domain-focused alternatives for each.