invest-architecture

You can audit codebase architecture by running this Skill, which reads your doctrine files like ARCHITECTURE.md, VECTOR.md, and CLAUDE.md to verify layer boundaries, naming conventions, and import direction compliance across the project.

Import direction compliance verifies that modules respect architectural layer boundaries by ensuring imports follow the allowed direction defined in your doctrine, preventing lower layers from improperly importing higher layers.

Yes, the architecture audit reads ARCHITECTURE.md to derive rules and enforce alignment, and also reads VECTOR.md and CLAUDE.md to fully derive the operator's doctrine before validating layers, naming, and imports.

Yes, the audit produces a structured report with findings, severity levels, and optional auto-fix hints that you can use to correct layer boundary, naming convention, and import direction violations across your codebase.

The best way to enforce naming conventions is to define them in your doctrine files and run a doctrine-driven architecture audit, which derives rules from ARCHITECTURE.md and verifies that all modules follow the specified naming patterns.

The audit derives rules strictly from existing doctrine files like ARCHITECTURE.md and CLAUDE.md, meaning if your doctrine does not explicitly define stack choices or layer boundaries, the audit cannot verify compliance for those unspecified architectural constraints.