analyserlisted

# Analyser — Existing-Codebase Architecture Audit ## Purpose Reverse-engineer the architecture from source, identify pain points, score the codebase, and produce one of: 1. An **in-place refactor plan** (when the current pattern is salvageable). 2. A **migration recommendation** that hands off to the `migrator` skill. ## Inputs - Repository root path. - Optional: deployment target, team size, business constraints (ask if missing). ## Step 1 — Inventory Run these checks with `Grep`/`Glob`/`Bash`. Cache results before reasoning. These greps are **coarse signals, not proof**. Names like `Interactor`, `Presenter`, `Builder`, `Coordinator`, `Store`, `Reducer` are reused across patterns (and across unrelated domain code), so a raw match count classifies poorly on a mature or mixed repo. Treat each signal as a hypothesis to confirm by opening representative files and reading how the pieces actually wire together — directory layout, who-owns-navigation, how state flows. Never report a pattern from grep counts alone. | Signal | Command | What it tells you | |---|---|---| | File count by suffix | `find . -name "*.swift" \| wc -l`, group by directory | Codebase size | | ViewController count | `grep -r "UIViewController" --include="*.swift" \| wc -l` | UIKit dominance | | SwiftUI View count | `grep -r ": View {" --include="*.swift" \| wc -l` | SwiftUI dominance | | Coordinator presence | `grep -r "Coordinator" --include="*.swift" \| wc -l` | MVVM-C / VIPER router | | VIPER marker