Front-End Naming Check & Repair — refactor-chain · Web lane · step 05

Bundle: refactor-chain (self-diagnosing, self-healing fix-it pipeline). Phase: do-the-work (web lane) · Prerequisite: refactor-web-04-layout · Next: refactor-code-principles, then the review gate. Adaptivity / conditional: framework-adaptive — the harness signals registry (scripts/lib/signals.mjs + languages.mjs under ~/.claude/skills/refactor-chain/scripts/) identifies the framework, and each rule is applied in that framework's naming idiom (React callback props, Vue emitted-event casing, Angular file-role suffixes, and so on). Style-class rules are convention-aware: the skill detects whether the project uses BEM, CSS Modules, or utility classes and enforces that, not a foreign convention.

Purpose

Make every name in the front end say what the thing is. This skill audits eight naming categories — components, files and directories, variables and functions, CSS classes, event handlers, user-facing labels, workflow/menu nodes, and props/contract types — and produces a severity-ranked report. In fix mode it performs renames the safe way: plan first, get a yes, then propagate every rename through imports, template/JSX usages, style selectors, and tests so nothing dangles.

When to use

• A naming audit is requested: "naming check", "naming review", "are our names consistent".
• A repair is requested: "fix the naming", "rename these properly", "clean up our casing".
• One category is in question: "component naming", "file naming", "CSS class names", "handler prefixes", "props types".
• The orchestrator reaches step 05 of the web lane.