tutti-architecture-review

# Tutti Architecture Review Use this skill when reviewing a `tutti` change or a named module for repository structure, module ownership, or layering compliance. This is a focused architecture review, not a general bug hunt. ## Vocabulary Use the architecture vocabulary consistently: - **Module**: anything with an interface and an implementation. - **Interface**: everything a caller must know to use the module correctly. - **Implementation**: the code inside a module. - **Depth**: leverage at the interface; deep modules hide useful behavior behind a small interface. - **Seam**: where an interface lives. - **Adapter**: a concrete thing satisfying an interface at a seam. - **Leverage**: what callers get from depth. - **Locality**: what maintainers get from depth. Prefer these words in findings. Avoid vague substitutes such as "component", "service", "utility", or "boundary" when a vocabulary term fits. ## Workflow 1. Resolve the user's review intent: - plain `git diff` review for the current change - module-focused diff review when the user names a module inside the current change - static module review when the user wants a named module inspected even without current diff overlap Use light natural-language guidance when the request is ambiguous. Do not force the user through a fixed mode menu. 2. When the user names a module, let the main agent infer a few candidate path keywords and gather candidate paths. Then normalize those paths into a scope file: ...