Domain Focused Naming
Name code by what it does in the domain, not how it's implemented or its history
Install
npx skills add obra/clank --skill Domain-Focused Naminggit clone --depth 1 https://github.com/obra/clank.git /tmp/clank
mkdir -p ~/.claude/skills
cp -r /tmp/clank/skills/coding/naming-by-domain ~/.claude/skills/Domain-Focused-NamingPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Domain-Focused Naming
## Overview
Names documenting implementation or history create confusion. "NewUserAPI" doesn't tell what it does. "ZodValidator" exposes internals.
**Core principle:** Names tell what code does in the domain, not how it's built or what it replaced.
**Violating the letter of this rule is violating the spirit of naming.**
## When to Use
**Use for:**
- Variables, functions, classes, modules
- Refactoring existing code
- Code review feedback
- API design
**Use ESPECIALLY when:**
- Refactoring (tempted to add "New" or "Improved")
- Replacing implementations (tempted to add "Zod" or "MCP")
- Using design patterns (tempted to add "Factory" or "Manager")
- Documenting changes (tempted to add "Unified" or "Enhanced")
## The Rules
### NEVER Use Implementation Details
Names expose WHAT, not HOW.
<Bad>
```typescript
class ZodValidator { } // Exposes Zod library
class MCPToolWrapper { } // Exposes MCP protocol
class JSONConfigParser { } // Exposes JSON format
```
</Bad>
<Good>
```typescript
class Validator { } // What it does
class RemoteTool { } // What it represents
class ConfigReader { } // What it does
```
</Good>
### NEVER Use Temporal Context
Code exists in present. Don't reference past or transitions.
<Bad>Details
- Skill name
Domain-Focused Naming- Repository
- obra/clank
- Path
skills/coding/naming-by-domain/SKILL.md- Repo updated
- 9 October 2025
FAQ
What does the Domain Focused Naming skill do?
Name code by what it does in the domain, not how it's implemented or its history
How do I install the Domain Focused Naming skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add obra/clank --skill Domain-Focused Naming. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Domain Focused Naming popular?
It lives in obra/clank, which has 43 GitHub stars and 26 forks.
Related skills
Gardening Skills Wiki
43obra/clank
Maintain skills wiki health - check links, naming, cross-references, and coverage
Remembering Conversations
43obra/clank
Search previous Claude Code conversations for facts, patterns, decisions, and context using semantic or text search
Brainstorming Ideas Into Designs
43obra/clank
Interactive idea refinement using Socratic method to develop fully-formed designs
Encapsulating Complexity
43obra/clank
Hide implementation details behind interfaces - work at domain level (what), not implementation level (how)
Designing Before Coding
43obra/clank
Design in pseudocode first, iterate approaches, then translate to code
Exploring Alternatives
43obra/clank
Try 2-3 different approaches before implementing - don't settle for first design you think of
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.