What problem does it solve? In-house React framework monorepos often break when packages are extracted without rewiring imports, leaving missing relative paths, circular dependencies, and barrels that eagerly re-export broken modules. This Skill provides a structured workflow to map package ownership, detect extract-without-rewire failures, and restore a healthy package graph. ## Core Features & Use Cases - Package ownership mapping: Build a package-to-role-to-health table across packages/* before editing anything. - Boundary repair patterns: Quarantine broken modules under src/legacy/, slim root barrels, and fix circular dependencies between core and hooks packages. - React hooks API rules: Enforce named use* exports, 2-tuple useState compatibility, SSR guards, and cleanup-preserving debounced effects. - Use Case: After splitting hooks out of a core package, imports like ../components silently break and the whole package fails to load. Use this Skill to diagnose the failure, quarantine broken modules, and rewire dependencies on @scope/core public exports. ## Quick Start Review the packages directory of my React framework monorepo, find broken imports and circular dependencies, and propose a repair plan.
