What problem does it solve? Large TypeScript codebases drift into tangled imports, god modules, circular dependencies, and inconsistent conventions that are hard to see from inside the code. This Skill audits the repository against an opinionated architectural baseline and produces an evidence-backed findings report plus an optional implementation plan. ## Core Features & Use Cases - Graph-powered structural analysis: Reads the Graphify knowledge graph to detect circular dependencies, god modules, god components, orphaned files, and fan-in/fan-out threshold violations. - Four-layer audit model: Covers module boundaries, coupling and complexity, state and data flow, and convention adherence, preceded by a diagnostic snapshot of the codebase's actual shape. - Pattern-aware checks: Detects Next.js, Remix, Vite-React, and architectural patterns (feature-folders, layered, atomic-design, monorepo workspaces) and applies the matching boundary rules. - Use Case: Run the audit on a React monorepo to discover that a shared api-client module has 87 inbound edges, two features import each other through deep paths, and half the components are marked 'use client' — then generate an ordered implementation plan to fix each gap. ## Quick Start Run /architecture-audit in the project root after running /pre-audit-setup to build the knowledge graph, then review the findings report written to .architect-audits/architecture-audit/.
