post-implementation-review

Re-read every touched file top to bottom, list them as an ASCII tree, then run structured passes: first-read, mental inlining, ownership checks, smell detection, and invariant audit. Report findings before making cleanup edits unless the issue is a direct compile or test failure.

Check for dead exports and methods, stale imports and JSDoc, identity wrappers, one-caller abstractions, redundant safety checks, misleading names, and old API shapes left alive alongside new ones. Each abstraction should be marked as earning its keep, inlineable, wrongly owned, or misnamed.

Fix immediately only grounded correctness, invariant, public API, verification, and serious clarity issues on the touched path. Report speculative or cosmetic cleanup separately, and pause on explicit user limits, product direction, destructive actions, or unclear ownership.

Count its callers and mentally inline it into call sites. Keep the layer only if it owns a lifecycle, an unsafe parse or network boundary, a repeated domain operation, a public contract, or a long imperative block whose name explains the phase.

Yes, it includes checks specific to TypeScript type organization, Go-to-Definition hop counts, Svelte components and runes, and Yjs CRDT documents. It delegates to focused skills for those surfaces when the touched files match.