What problem does it solve? In a Next.js App Router codebase, pages can silently become coupled through deep imports into shared components, hooks, and internal logic, eroding the architecture where each page should act as an independent mini-app. This Skill audits all entrypoints and classifies every @/components/* import so coupling is detected before it spreads. ## Core Features & Use Cases - Import Classification: Scans 125+ page/layout/loading/error/not-found entrypoints and classifies each import as Compliant (top-level or page-unit barrel), Warning (deep import), or Violation (lib/hooks/_internal dependency). - Independence Scoring: Computes a Compliant/Warning/Violation ratio to quantify how independent each page really is and track progress over time. - Staged Remediation: Produces a prioritized fix list and a phased roadmap for converting deep imports into sub-barrels, with a strict mode that promotes Warnings to Errors in CI. - Use Case: Before a release, run the report to confirm no page depends on another group's internal hooks, then plan Phase 1/2/3 sub-barrel refactors for the remaining deep imports. ## Quick Start Run the barrel isolation audit on this repository and report which pages violate the import boundary rules with a prioritized fix plan.
