architecture-guard

You can enforce architecture rules by validating new file paths against .context/architecture.md. The Skill classifies the target module, checks path conformance and import restrictions, and returns a clear approval or rejection before code is written.

Preventing architectural drift requires validating file placement during creation, moves, and code reviews. The Skill reads your architecture.md, classifies the proposed file into the correct module, and rejects misplacements before they enter your codebase.

Yes, you can enforce import restrictions during code reviews by validating the target file path. The Skill checks the proposed placement against module boundaries and import rules defined in architecture.md, returning a clear rejection for any violations.

The best way to guard module boundaries is to validate proposed file paths against architecture.md before creation. This pre-check classifies the target module, enforces placement rules, and stops misplacements before any code is actually written.

Yes, you need a .context/architecture.md file to validate path conformance. The Skill reads this file to understand module boundaries, responsibilities, and import rules required to classify and approve target file placements.

You should validate file moves before executing them to avoid breaking architecture. The Skill checks the proposed destination path against architecture.md, ensuring the new placement and its imports conform to module boundaries.