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: 1. identify the real organizing unit, 2. separate feature/shared/framework/package boundaries, 3. define naming and import rules that prevent drift, 4. plan the migration safely, 5. return a structure brief another engineer or agent can apply immediately. Read references/boundary-decision-matrix.md before recommending a structure.…