Project Structure Refactoring

Cross-language project structure and structural refactoring standards: design clean folder/module layouts and safely restructure existing codebases. Use when restructuring or reorganizing a codebase, choosing or fixing a repo's folder structure, deciding where a file belongs, package-by-feature vs by-layer, reorganizing/moving files, planning a migration to a new layout, fixing messy/flat/deep folder trees, splitting a giant or god file into modules, monorepos (apps/packages, workspaces, Turborepo/Nx), Python src layout, Go cmd/internal layout, React/Next.js/Expo feature folders, barrel files, import path aliases, or updating Dockerfiles/CI/configs after file moves. Covers plan-approve-execute staged migrations with green builds, git mv history preservation, and boundary enforcement. Structural only: hand code-level refactoring (extract/rename/dedupe) to code-implementation or codebase-audit, NestJS layout specifics to nestjs-dev-guidelines. Principles apply to any language beyond the stacks documented.

myatminlu Updated

File contents

myatminlu/vector-skills commit 57226693fa

Frequently asked questions

npx get-skill add myatminlu/project-structure-refactoring