Keep module boundaries explicit and enforceable.
What it does
Turns structural invariants into named contracts with written rationales and mechanical guards.
When to use it
Use when changes cross module boundaries, add dependency directions, touch critical paths, conflict with principles, or update architecture principles.
How to use it
It changes how the agent defines, documents, mechanically enforces, and reviews architectural invariants in the project.
What you provide
- An existing project
Security reviews
Not yet reviewed.
What you need · 1
The skill requires the principal-engineering skill as background.
Access · 0
No additional actions listed.