Skills naming-format

Use when reviewing file names, renaming files, fixing naming conventions, or auditing exports. Enforces consistent casing and suffix patterns.

install
source · Clone the upstream repo
git clone https://github.com/amanahmed2222/skills
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/amanahmed2222/skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/naming-format" ~/.claude/skills/amanahmed2222-skills-naming-format && rm -rf "$T"
manifest: skills/naming-format/SKILL.md
source content

You are a naming conventions expert. Infer the project's language variant (US/UK English) from existing commits, docs, and code, and match it in all output.

Read individual rule files in

rules/
for detailed explanations and examples.

Rules Overview

RuleImpactFile
Case consistencyHIGH
rules/case-consistency.md
File suffixesHIGH
rules/file-suffixes.md
Export namingHIGH
rules/export-naming.md
Index filesHIGH
rules/index-files.md
Framework conventionsMEDIUM
rules/framework-conventions.md

Workflow

Step 1: Detect

Scan the project to identify:

  • Dominant filename casing convention (count files by pattern)
  • Framework indicators in
    package.json
    (Next.js, Expo, etc.)
  • Existing suffix patterns (
    .test.ts
    vs
    .spec.ts
    , etc.)
  • Export naming patterns across the codebase

Step 2: Audit

Check all files and exports against the rules. Report violations grouped by rule:

## Naming Audit Results

### HIGH Severity
- `src/components/userProfile.tsx` - File should be `user-profile.tsx` (kebab-case)
- `src/hooks/UseAuth.ts` - Hook export `UseAuth` should be `useAuth` (camelCase with `use` prefix)

### MEDIUM Severity
- `src/utils/index.ts` - Barrel file with 12 re-exports → use direct imports

### Summary
| Rule              | Violations | Files |
|-------------------|------------|-------|
| Case consistency  | X          | N     |
| Export naming     | Y          | N     |
| **Total**         | **X+Y**    | **N** |

Step 3: Fix

Apply fixes for each violation:

  1. Rename files using
    git mv
    to preserve git history
  2. Update all import paths in dependent files
  3. Verify no broken imports remain after renames