← ClaudeAtlas

naminglisted

Use when deciding what something is called — what should I call this module or class, this name is vague, rename this, re-derive a ported or generated name. Owns the derivation procedure, the six naming tests, the `I` prefix on ports, the error-class and repository-class identifier forms, the vague-noun replacements, and the role suffixes (`Handler`, `Result`, `Payload`, `Service`) an architecture defines that are exempt from them. The mechanics around a name are `python-packaging`. - Naming a variable, parameter, enum member or constant; choosing between `fetch_`, `build_` and `get_by_`; standardising a term the repository already spells two ways.
wntic/pyhouse · ★ 3 · Code & Development · score 76
Install: claude install-skill wntic/pyhouse
# Naming — deriving a name instead of recalling one A name is the first thing a reader sees and usually the only thing they read before deciding what something does. The cost of getting it wrong is asymmetric: **wrong code fails loudly, a wrong name misleads quietly for as long as it survives** — through every review, every search, and every later change made on the strength of what it seemed to promise. This skill owns the choice of the name itself. It is architecture-neutral and project-neutral, and is loaded alongside whichever skill owns the artifact being named. It holds in any Python project — a single package, a service, a library, a workspace of several. Examples use this set's placeholder vocabulary (`myapp`, `foos`/`bars`, `Foo`/`Bar`) with real technology names (`redis`, `s3`, `stripe`) kept concrete; substitute your project's own concepts, never its layout. ## When to use vs. neighbours - Choosing or judging any identifier — package, module, class, function, method, parameter, variable, enum, constant → this skill, before writing the line. - Porting or generating code and keeping the names that came with it → this skill, first; that is its primary case. - One class per module, `__all__`, the `__init__.py` re-export contract, import spelling, a circular import → `python-packaging`. It owns the *mechanics* around a name; this skill owns the name, so "name this module" is a request for this skill and not for that one. - Which package a module belongs in