naming-conventions

naming-conventions is a skill for Claude Code, Codex from TechyMT/claude-code-superpowers. It costs 100 tokens per session (1,637 once invoked), scanned A, original, MIT.

A guide to naming files, commands, types, functions, variables, constants, and event handlers in Claude Code projects. It defines patterns such as kebab-case commands and verb-based camelCase functions.

In plain words
What is it for?
Use it when adding or renaming tools, commands, types, functions, variables, constants, and event handlers.
Why use it?
Consistent names make a large codebase easier to navigate and help developers infer what a file or identifier is for before opening it.

Skill for Claude CodeCodex

Part of the claude-code-superpowers plugin — 16 skills shipped together

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/techymt/claude-code-superpowers/naming-conventions
Any agent
npx skills add TechyMT/claude-code-superpowers --skill naming-conventions
Clone the repo
git clone --depth 1 https://github.com/TechyMT/claude-code-superpowers

Made for: Claude Code, Codex.

Or install claude-code-superpowers, the plugin that ships this one along with the rest of its 16 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for naming-conventions

README.md
[![agentmods](https://agentmods.dev/badge/skills/techymt/claude-code-superpowers/naming-conventions.svg)](https://agentmods.dev/skills/techymt/claude-code-superpowers/naming-conventions)
Your own site
<a href="https://agentmods.dev/skills/techymt/claude-code-superpowers/naming-conventions"><img src="https://agentmods.dev/badge/skills/techymt/claude-code-superpowers/naming-conventions.svg" alt="Measured on agentmods" height="20"></a>
Per session 100 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,637 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00100 $0.01637
Opus 5 $0.00050 $0.00818
Sonnet 5 $0.00020 $0.00327
Haiku 4.5 $0.00010 $0.00164

Measured 4d ago against content hash 01dc982e5d71, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

naming-conventions scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/naming-conventions/SKILL.md · 132 lines

How it starts

The opening of the file, as written. The whole thing — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Naming Conventions

The pattern

Claude Code uses a set of naming conventions that encode the role of a file or identifier in its name. A file named BashTool.tsx is a Tool implementation with UI concerns. A file named BashTool.ts is a Tool implementation with no UI. A function named isConcurrencySafe returns a boolean about concurrency. A function named getBranch fetches a value. A constant named MAX_STATUS_CHARS is a numeric limit. These are not accidental — reading the name tells you the role without reading the implementation.

Why this matters

At ~512K lines across 1,884 files, Claude Code is too large for any individual to hold in memory. Naming conventions serve as a file-system-level type system: you can predict what's in a file before opening it. AgentTool/AgentTool.tsx will export a Tool<Input, Output> that has UI progress output. state/AppStateStore.ts will export the AppState type and initial state. hooks/useCanUseTool.ts will export a React hook returning a permission-checking function.

How to apply it

Files:

  • Tools: src/tools/[Name]Tool/[Name]Tool.ts[x].tsx if the tool renders JSX output
  • Commands: src/commands/[kebab-name]/index.ts or src/commands/[kebab-name].ts
  • React hooks: src/hooks/use[Name].ts — always prefixed with use
  • React components: src/components/[Name].tsx
  • Utilities: src/utils/[name].ts — lowercase, describe the domain (e.g., git.ts, path.ts)
  • Types: src/types/[name].ts — lowercase file, PascalCase exports

Identifiers:

  • Types, interfaces, classes: PascalCase (e.g., ToolUseContext, AppState, PermissionResult)
  • Functions: camelCase starting with a verb (e.g., createTaskStateBase, normalizeMessages, getGitStatus)
  • Booleans and boolean-returning functions: is/has prefix (e.g., isConcurrencySafe, isReadOnly, hasWorktreeChanges, isENOENT)
  • Event handlers and callbacks: on[Event] prefix (e.g., onProgress, onChangeAppState, onCompactProgress)
  • Constants: UPPER_SNAKE_CASE for numeric/string limits; PascalCase for object constants (e.g., MAX_STATUS_CHARS, IDLE_SPECULATION_STATE)
  • Tool exports: named constant matching the file name (e.g., export const BashTool, export const FileReadTool)
  • Async functions: same naming as sync — the Promise return type is the indicator, not a naming convention

Read the full file on GitHub · 132 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 4d ago First seen · 132 lines · 100 tokens per session scan A 01dc982e5d71

Subscribe to this mod's changes

naming-conventions is a skill published in the GitHub repository TechyMT/claude-code-superpowers (5 stars, last pushed 5mo ago), licensed MIT. It adds 100 tokens to every session and 1,637 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens