Feature-Module Boundaries & Anatomy — refactor-chain · do-the-work (web lane, step 02/05)

Bundle: refactor-chain (self-diagnosing, self-healing fix-it pipeline). Phase: do-the-work (web lane, step 02 of 05) · Prerequisite: refactor-web-01-structure · Next: refactor-web-03-components. Adaptivity / conditional: framework-adaptive via the harness signals registry — the feature layer is features/ (React/Svelte), modules/ (Vue), or Angular feature areas; router/store correspondence maps to the detected ecosystem.

Purpose

Carve the feature layer into domain-driven modules with hard walls. Boundary decisions come from a quorum matrix, not gut feel; each module's internal anatomy follows one standard shape; and no module ever reaches into a sibling's internals — cross-module needs route through the shared layers instead. The skill audits existing modules, plans confirmed splits/merges, and scaffolds new modules wired into routing.

When to use

• "Are our feature boundaries right?" / "module structure check" / "module dependency check".
• "This module has 30 pages, split it" / "this module is too big".
• "OrdersList imports customers' API file directly" / "features import each other's internals".
• "Create a new feature module" / "module scaffold".
• Automatically, as step 2 of the web lane after the structure step is clean.