Enforce descriptive file and folder naming conventions in repositories.
npx skills add https://github.com/erichugy/agentic.skills --skill file-naming
Please help me install this Agent Skill. Skill: file-naming Source: https://github.com/erichugy/agentic.skills/tree/main/file-naming Command: npx skills add https://github.com/erichugy/agentic.skills --skill file-naming
Vague or inconsistent file and folder names hide intent, slow development, increase cognitive load during reviews, and make refactors fragile. This Skill provides concrete naming rules and patterns so developers and maintainers can understand code structure without opening files.
Rename ambiguous files such as utils.ts into clear purpose-named files like parse-options.ts or split responsibilities into a module folder with well-named role files.
High-intent search queries and answers about installing and using this skill.
To make code structure self-explanatory, enforce clear file and folder naming by using descriptive filenames instead of vague buckets like utils, ensuring folders provide domain context, and mirroring tests to source files for immediate discoverability.
Rename ambiguous utility files during a project refactor by replacing generic names like utils.ts with specific purpose-named files like parse-options.ts, or split responsibilities into a module folder containing well-named role files.
Use domain-context folders versus action-first file naming conventions based on what varies more in your source code repository: choose folder-first structures when domains vary most, and file-first structures when actions or roles vary most.
You need indexed consumer barrels when reorganizing modules for code reviews to provide a clear consumer-facing interface, ensuring that files provide specific roles while barrels expose the module's public API cleanly.
Inconsistent file naming slows development and increases cognitive load because vague or generic bucket names hide intent, making each file's purpose unclear without opening it, which makes code reviews and refactoring fragile.
These file naming conventions can be applied to source code repositories, documentation, and project refactors to enforce clear, specific naming, making each file's purpose immediately discoverable without opening files.
scottopellExtract domain entities, states, transitions, and boundaries into an Allium-style spec.
ShunmeiChoOrganize files and folders by detecting duplicates and restructuring with user approval.
Gentleman-ProgrammingEnforce Angular project structure and naming conventions across feature and shared boundaries.
StudentCristianApply explicit design patterns to naming, API ergonomics, and domain organization in functional codebases.
