What problem does it solve? Moving code between libraries in a layered monorepo often breaks import boundaries, leaves duplicate copies behind, and silently drops imports — this Skill provides a proven procedure to avoid those failures. ## Core Features & Use Cases - Plan-first relocation: Checks docs/plans/ before choosing a new location so moves align with decisions already recorded. - Dependency-ordered moves: Derives move order from the dependency graph via grep of domain aliases rather than plan lists, avoiding temporary boundary widening. - Placement rules: Maps shared code to the correct lib (libs/common/util, common/platform, common/ui, family core) based on who consumes it. - Post-move verification: Runs nx lint --fix, project-list lint runs, check:layers, check:dupes, and manual route scenario checks. - Use Case: When moving list utilities from one lib to another in an Nx workspace, follow this pattern to pick the right destination, sequence the move, and catch vanished imports across all touched projects. ## Quick Start Ask the AI to move a symbol or domain from one library to another in the monorepo and have it follow the lib-layers move pattern for ordering, boundaries, and verification.
