Adapted from mattpocock/skills at commit 3cca18b368ae95cdbdebbff572ccafa662551015 (MIT).

Architecture review

Review architecture without editing code or defining final interfaces. Use the repository's domain terms and existing ADRs. Use this vocabulary consistently: module, interface, implementation, depth, deep, shallow, seam, adapter, leverage, and locality.

Scope

Use the user's named area. Otherwise inspect recent history for repeatedly changed hotspots before scanning broadly. Follow actual call paths and tests.

Look for evidence of:

• shallow modules whose interface nearly matches their implementation;
• one concept scattered across many files;
• duplicated orchestration around a missing deep interface;
• tests that reach through internals because no stable public seam exists;
• details leaking between coupled modules; and
• extracted helpers that improve unit-test access but reduce locality.