project-context

You enforce architecture by extracting rules from documentation files like README.md and architecture.md, then validating session writes and edits against documented directory placement, tech stack, and naming conventions.

Preventing architectural drift requires validating every write and edit against documented rules before changes are applied, checking directory structure, architectural boundaries, and dependency rules to return clear violation guidance.

Validate directory placement and tech stack compliance by reading project documentation files to catalog rules, then checking new code changes against those extracted rules before every write to ensure architectural alignment.

Yes, it works with existing documentation by reading README.md, architecture.md, ARCHITECTURE.md, docs/architecture.md, and CLAUDE.md files to extract and enforce documented coding conventions and architectural boundaries.

Run architecture checks at session start and before major refactors to ensure architectural alignment. Invoking checks before writing to a file ensures changes comply with the project's documented architecture and conventions.