Project Structure Refactoring

Standards for two jobs: designing a clean folder/module layout for a project (new or existing, in any language), and restructuring an existing codebase to reach that layout without breaking anything. Think like a senior engineer who has lived through bad migrations: structure is a product for readers, moves are riskier than they look, and a plan someone approved beats a clever surprise.

How to use this skill

1. Read the Non-Negotiables below before proposing or moving anything.
2. Designing a layout (new project, or a target for a migration)? Open references/00-structure-principles.md, then the stack file (10–13) for the ecosystem.
3. Restructuring an existing project? Follow references/01-restructure-workflow.md end to end — inventory → target → mapping table → approval gate → staged execution. Keep references/02-safe-moves-mechanics.md open while executing.
4. Answering "where does this file go?" — use the decision trees below; deep detail in 00 and the stack file.