What problem does it solve?
Naming is the foundation of readable code. This skill enforces consistent, descriptive identifiers to reduce confusion and maintenance overhead across projects and languages.
Core Features & Use Cases
- Hierarchy of Authority: prioritize project conventions, then language/framework norms, then the skill's own rules to resolve naming decisions.
- Core Rules: avoid ALL_CAPS (except PHP defines as needed), spell words out, context informs naming, no redundant suffixes, and hide implementation details.
- Semantic Patterns: apply booleans with is/has/can/should prefixes; use verb+noun patterns for actions; ensure proper pluralization based on containers; consider transformers and accessors naming.
- Checklist: verify no abbreviations (except common ones), minimize redundancy, and ensure names convey intent.
Quick Start
Rename a sample identifier 'MyVariable' to a compliant, descriptive name like 'myVariable' following the skill's naming rules.