naming-conventions

Function naming verbs like get, fetch, validate, and parse should be chosen based on side effects, cost, and failure behavior to ensure identifier semantics truthfully reflect the operation. This prevents misleading names and improves codebase readability.

Artifact-specific casing rules apply kebab-case to files and paths, camelCase to variables, PascalCase to types, SCREAMING_SNAKE_CASE to constants, and snake_case to SQL columns. Applying the correct casing consistently helps readers trust what names imply across the codebase.

Detecting names that lie involves identifying common naming bugs like boolean polarity inversion, getX functions that mutate state, and stale meanings left after refactors. Truthful naming requires validating identifiers against their actual behavior and downstream dependencies.

Safe rename coordination requires finding all call sites, updating references in a single commit, and choosing deprecation aliases when needed. This workflow prevents broken downstream dependencies and ensures behavior interpretation remains intact across the refactor.

Naming conventions are explicitly scoped to enforce truthful, consistent naming for files, functions, variables, types, routes, and data or schema artifacts. This skill avoids documentation writing, content prose, code restructuring, PR review, and debugging.