restructure

Extract misplaced code from any folder (backend or frontend) and move it to a properly-named folder that fits this project's existing conventions. Plan-first - reads the codebase to infer style, proposes a move-plan grounded in clean-code principles (Rule 15, Martin ch 11, McConnell ch 5), waits for a single confirmation, then moves files + rewrites imports atomically with git-aware history preservation. Handles backend layouts (services, repositories, controllers, route handlers), frontend layouts (components, pages, features, hooks, stores, ui/design-system), and mixed monorepos. Auto-chains from /cleancode:rewrite when a file split would benefit from cross-folder relocation. Triggers on phrases like "restructure my project", "move this code to a proper folder", "extract this from routes/", "my routes folder is doing too much", "where should this code live", "reorganize my folders", "split this across modules", "extract feature folder", "move business logic out of pages/components", "promote this shared code", or /cleancode:restructure.