file-naming

What problem does it solve?

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.

Core Features & Use Cases

• Specific, self-documenting names: prefer descriptive filenames over generic buckets like utils or helpers.
• Domain vs. action patterns: choose folder-first or file-first structures based on what varies more.
• Folder and file roles: ensure folders provide domain context, files provide role, use barrels for consumer-facing modules, and mirror tests to source files.
• Use Case: apply these rules during code reviews, repo onboarding, or when reorganizing modules to reduce search time and prevent duplicated responsibilities.

Quick Start

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.