| name | hai-architecture |
| description | Investigates architecture and software change complexity, from whole-repository runtime paths to a bounded module/design decision. Use for 系统太绕、复杂度审计、调用链/配置太散、架构审查、模块边界、拆分合并, or why a repo is hard to change. Select global investigation or bounded design mode; return traced evidence, the complexity center, alternatives, and a first proof. Use hai-debug for an unexplained malfunction and code-review-and-quality for reviewing a change or local code smells.
|
Hai Architecture
For Chinese readers, see SKILL.zh_CN.md. The English SKILL.md is the execution source of truth.
Purpose
Review existing architecture or guide one design decision through the lens of managing complexity.
Find the boundary where change amplification, cognitive load, or unknown unknowns concentrate, then
recommend the smallest structural move that makes the system easier to understand and change.
Select the work mode
- Global investigation: the cause or boundary of change friction is unclear, or the request
spans a repository/large subsystem. Read
references/global-audit.md and follow its entrypoint,
call-chain, state/config, and test tracing procedure. Converge on important paths after mapping
the entrypoint families; do not substitute a local smell review.
- Bounded review/design: a module, package boundary, or design choice is already identified.
Follow the workflow below, inspecting its direct callers, contracts, and tests.
- A request can move from global investigation into a bounded decision. Reuse collected evidence;
do not rerun two full reviews or ask the user to choose an internal mode.
Evidence gate
Before making an architecture claim:
- Read every cited file in this session and cite real
file:line locations.
- Trace callers and implementations before asserting a call chain or blast radius; name the search.
- Read ADRs, dependency rules, architecture tests, and public contracts that declare intended
boundaries.
