File Organization

This one helps you decide whether your codebase should be organized by feature, type, route, or workspace package, then gives you a migration plan that won't leave imports broken halfway through. It's built around a decision ladder that asks what your actual pain is: scattered feature code, unclear shared boundaries, or premature monorepo splits. The skill reads boundary decision matrices and migration checklists before recommending structure, which keeps it from dumping generic folder trees on every repo. Use it when you're refactoring a messy components/hooks/utils sprawl or choosing conventions for a new project. Skip it if your real problem is component API design, state ownership, or deployment automation.

Install to Claude Code

npx -y skills add akillness/oh-my-skills --skill file-organization --agent claude-code