Skip to content

Skill

Reviewing Architecture and Boundaries

Reviews software architecture and module boundaries from inspected code or design material.

Back to Skills

When to use

Reviews software architecture and module boundaries from inspected code or design material - evidence-based architecture classification, layering violations, dependency direction, boundary leakage, interface contract drift, state ownership, and coupling - and proposes the smallest structural change set with a confidence score.

  • Use when

    Use when the main question is whether system structure, layers, ownership, or dependency flow are correct.

  • Limits

    Not for framework best-practice sweeps, code-quality review, security review, or performance tuning.

Skill package

reviewing-architecture-boundaries.zip

The ZIP contains the complete reviewing-architecture-boundaries folder: SKILL.md and 1 supporting file, at the paths the Skill uses.

  • reviewing-architecture-boundaries/SKILL.md
  • reviewing-architecture-boundaries/references/boundary-checks.md

Inputs required

Review goal
What to evaluate: the observed architecture, layering, dependency direction, state ownership, module or interface boundaries, or a specific structural concern.
Materials
Code, file tree or module map, diagrams, design notes, interface contracts, configuration excerpts, or repository access.
Constraints
Language, framework, runtime, platform, and deployment constraints that are known.

Access needed

Needs read access to the code or design material under review (repository, files, or pasted excerpts). No network access required. Read-only; does not modify files.