invest-architecture

To enforce architectural rules automatically, audit your codebase against project-specific doctrine defined in markdown files. This skill scans for layer separation, import direction, and naming conventions to prevent architectural drift.

Prevent architectural drift by running an audit that checks new code against established rules in your architecture markdown files. It verifies layer separation and design token usage, offering optional auto-fixing for eligible violations.

Yes, you must define your project's layers and naming conventions in markdown files like ARCHITECTURE.md before auditing. The architecture audit uses these specific doctrine files to evaluate code compliance.

Yes, an architecture audit can automatically fix eligible violations. Alongside reporting layer separation and naming convention issues, it supports optional auto-fixing for certain import direction and architectural rule breaches.

The best way to check design token usage is to run an automated code audit against your project's architectural doctrine. It evaluates token application alongside import direction and layer separation to ensure consistency.