File Organization

Use this skill when the real question is "what structure should this repo use next, and how do we improve it without creating a bigger mess?"

The job is to choose the lowest-complexity structure that fits, define the boundary rules, and give an incremental migration path when the repo already exists.

Read references/repo-shape-decision-guide.md before choosing a structure. Read references/migration-playbook.md when the repo is already messy. Read references/repo-type-patterns.md when the request spans frontend, backend, docs/ops, or game-development layouts.

When to use this skill

• Decide how to structure a frontend, backend, fullstack, docs, or game-development repo
• Choose between framework defaults, feature/domain folders, apps/ + packages/libs/, docs taxonomy, or engine-aware hybrid layouts
• Reorganize an existing repo whose folders no longer communicate ownership or intent
• Define naming and placement rules for code, docs, scripts, assets, tests, or packages
• Stop shared/, common/, misc/, helpers/, or utils/ junk drawers from spreading
• Plan an incremental reorganization instead of a risky all-at-once rewrite