Architecture Enforce

Turn architecture policy into repository evidence and blocking checks while preserving behavior unless a requested migration explicitly changes it.

Use this skill

• Change or audit packages, directories, modules, schemas, APIs, tests, generated boundaries, build graphs, deployables, languages, storage, protocols, public contracts, or three or more sibling files.
• Use it for file shattering, flat folders, filename colonies, helper or manager proliferation, dependency cycles, ownership drift, and lint, test, architecture, or CI suppressions.
• Do not use for isolated formatting or comment edits, architecture ideation before a target is selected, or generated output when canonical generator input is available.
• Redirect target selection and ADRs to $architecture-design, repository policy to $repo-governance, and pipeline gates to $git-ci-cd.

Rules

• Read repository instructions, owning code, callers, tests, build configuration, generators, and public contracts before editing.
• Assign every changed path one durable owner, responsibility, visibility, lifecycle, dependency direction, and reason it remains separate.
• Prefer cohesive capability modules over one-type, one-operation, phase, helper, validation, or filename-prefix colonies.
• Inventory tracked, modified, staged, and non-ignored authored source; keep tracked files auditable.
• Every warning and error blocks. Never add ignores, exclusions, advisory modes, allow-failure paths, lower thresholds, or weakened tests.
• Change canonical generator inputs; do not hand-edit generated output. Preserve public entrypoints and contracts unless migration evidence records the change.