Domain-Focused Naming

$npx mdskill add obra/clank/Domain-Focused Naming

Name code by domain purpose, not implementation details.

  • Eliminates confusion from vague or history-based identifiers.
  • Applies across variables, functions, classes, and modules.
  • Prevents adding library names or pattern keywords to names.
  • Guides refactoring by replacing implementation-focused labels.

SKILL.md

.github/skills/Domain-Focused NamingView on GitHub ↗

No skill content available yet.

More from obra/clank

SkillDescription
Commenting IntentComment WHY code exists and non-obvious decisions, not WHAT code does (mechanics)
Creating SkillsTDD for process documentation - test with subagents before writing, iterate until bulletproof
Designing Before CodingDesign in pseudocode first, iterate approaches, then translate to code
Encapsulating ComplexityHide implementation details behind interfaces - work at domain level (what), not implementation level (how)
Exploring AlternativesTry 2-3 different approaches before implementing - don't settle for first design you think of
Installing Skills SystemFork, clone to ~/.clank, run installer, edit CLAUDE.md
Keeping Routines FocusedEach routine does one thing and does it well - extract when routines have multiple responsibilities
Localizing VariablesDeclare variables in smallest possible scope, initialize close to first use, minimize span and live time
Maintaining Consistent AbstractionsClass interfaces present one cohesive abstraction - don't mix domain logic with serialization, persistence, or unrelated concerns
Naming VariablesChoose names that fully and accurately describe what the variable represents