file-system-organization

What problem does it solve?

This Skill eliminates code sprawl and "utility hell" by enforcing a strict, modular file system organization. It ensures that all related code (functions, tests, helpers, constants, types) lives together, making codebases easier to navigate, refactor, and delete without creating orphaned files, saving you countless hours of maintenance.

Core Features & Use Cases

• One Entity Per Folder: Every function and component gets its own self-contained folder, improving discoverability and modularity.
• Deep Linking & No Barrel Files: Enforces direct imports, enabling aggressive tree shaking and clear dependency graphs.
• Private Helper Encapsulation: Clearly defines how to organize private helper functions in subfolders, preventing accidental exposure and maintaining encapsulation.
• Use Case: When creating a new processOrder function, this skill guides you to create a processOrder/ folder containing index.ts, index.test.ts, and any private helpers like _validateItems/ within their own subfolders. This ensures that processOrder is a self-contained, easily movable, and deletable unit.

Quick Start

Explain the correct file system structure for a new function named 'calculateDiscount' that has a private helper function '_applyTax'.