file-organization

What problem does it solve?

Disorganized project files lead to confusion, wasted time searching, and "file organization debt," hindering productivity. This skill automatically enforces project-specific file organization standards, ensuring a clean, consistent, and easy-to-navigate codebase without manual effort.

Core Features & Use Cases

• Automated Reorganization: Automatically moves files to their correct locations based on predefined rules (e.g., shell scripts to scripts/, documentation to docs/).
• Root Directory Policy: Enforces a clean root directory with a limited number of essential files, preventing clutter.
• Categorized Structure: Guides shell scripts, documentation, and source code into logical subdirectories (e.g., scripts/test/, docs/guides/, src/).
• Use Case: If you accidentally create a test-script.sh in the root directory, this skill will automatically move it to scripts/test/test-script.sh and notify you, keeping your project organized without manual intervention.
• Use Case: Ensure all new documentation files are placed in the correct docs/ subdirectory based on their content (e.g., docs/architecture/ for ADRs).

Quick Start

This skill is auto-invoked before file/directory creation or moves.

To see it in action, try creating a shell script in the root:

(Claude will auto-correct its location based on project rules)

Write: test-script.sh

Content: echo "Hello from a test script!"