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.

skills.sh installs: 185
GitHub stars: 22
last updated: Jun 3, 2026

View on GitHub

Install

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

Installs into .claude/skills of the current project.

Files

File Organization

Use this skill when the main question is "what structural boundary should this codebase use, and how do we move toward it without turning a reorg into chaos?"

The job is not to dump a giant folder tree and pretend it fits every repo. The job is to:

identify the real organizing unit,
separate feature/shared/framework/package boundaries,
define naming and import rules that prevent drift,
plan the migration safely,
return a structure brief another engineer or agent can apply immediately.

Read references/boundary-decision-matrix.md before recommending a structure. Read references/migration-checklist.md before moving files or renaming directories. Read references/naming-and-import-rules.md when the problem includes barrel files, alias paths, or team conventions.

SKILL.md on GitHub

Sponsors

Promote your product hereReach 125k+ visitors monthly Promote your product hereReach 125k+ visitors monthly