What problem does it solve? Inconsistent naming across folders, files, classes, database tables, and API routes creates confusion and technical debt. This Skill provides a single source of truth for every naming decision in a NestJS/TypeScript codebase, so names stay consistent as the project grows. ## Core Features & Use Cases - Comprehensive naming rules: Covers module folders, file suffixes, classes, interfaces, enums, variables, DB tables/columns/indexes, migrations, and HTTP paths with concrete examples. - Reserved verb vocabulary: Standardizes method names like findById, findByIdOrFail, and assert<Constraint> so teams stop inventing synonyms. - Three usage modes: check <path> audits a file for violations, propose <thing> generates compliant names for new code, and show prints the detailed reference. - Use Case: Before creating a new transfers module, ask the Skill to propose the folder structure, entity class, DTO names, and table/column names so everything matches the convention from day one. ## Quick Start Ask the assistant to check whether the names in a given source file follow the project's naming conventions and report any violations with proposed fixes.
