Frontend Structure Audit & Scaffold — refactor-chain · do-the-work (web lane, step 01/05)

Bundle: refactor-chain (self-diagnosing, self-healing fix-it pipeline). Phase: do-the-work (web lane, step 01 of 05) · Prerequisite: green baseline (refactor-safety-net) · Next: refactor-web-02-modules. Adaptivity / conditional: framework-adaptive — the harness signals registry (refactor-chain/scripts/lib/signals.mjs, surfaced by diagnose.mjs) detects React / Vue / Svelte / Angular / React Native, and every rule is phrased in that framework's native vocabulary.

Purpose

Give a web frontend a predictable, layered source tree: every file has one obvious home, and dependencies only flow downward. The skill does two jobs — audit (scan the tree, report violations with severities and fixes) and scaffold (generate a compliant skeleton, including a design-token variables file, then self-check it against the same rules). Directory moves are planned first, confirmed by the user, and executed with full import-path rewriting so nothing breaks.

When to use

• "Is our folder structure sane?" / "project structure check" / "layered architecture review".
• "Set up a new frontend project properly" / "scaffold the app skeleton".
• "Components are importing feature code and it's a mess" / "fix our import directions".
• As the entry step whenever the orchestrator routes a repo into the web lane.