Architecture documents drift from the code
Layer and import rules are easy to agree on and hard to enforce. Reviewers repeatedly catch the same violations, while developers receive feedback too late.
Make the rule executable and local
I implemented BR001 through BR005 in a Rust analyzer, validated configuration at runtime with Zod, and connected results to a Vite overlay for immediate feedback.
Benchmarks include generated fixtures and a real monorepo snapshot so performance claims remain reproducible instead of anecdotal.
Fast feedback at repository scale
The analyzer processed a 10,000-file fixture in 164.20 ms and matched 2,559 import edges. Architecture rules became part of the development loop rather than a document checked after the fact.
Trace
Rule model, Rust analyzer, configuration validation, editor overlay, and benchmark design
Static analysis · Architecture rules · Vite overlay · Benchmarking
Rust · TypeScript · Zod · Vite · Static Analysis · NPM · GitHub Actions
Benchmarks use public fixtures and a documented local environment.