| name | arch-drift-guard |
| description | Use when a repo is suffering architecture drift, API drift, main-file bloat, boundary erosion, or repeated breakage from cross-layer edits. Enforces artifact-first anti-drift governance: classify drift type, declare allowed change surface, write durable repo artifacts, require mechanical checks, and only then modify code.
|
| tags | ["architecture","drift","governance","anti-erosion","refactoring","large-repo"] |
| version | 1 |
arch-drift-guard
When to use
Use this skill when any of the following appears:
- giant
main.rs / god file keeps regrowing
- repeated API drift after partial refactors
- struct initializer drift after adding fields
- cross-layer edits keep breaking compile/tests
- module boundaries are unclear or routinely violated
- agent edits cause repo erosion over time
- user says things like: “漂移”, “越改越乱”, “边界不稳”, “模块化不够”
Do not use when
- simple isolated bug with clear local fix -> use
systmt-dbggng
- brand-new system design -> use
ddd-project-grdrls
- only one extraction move with known order in ict-engine main.rs -> consider
ict-engi-stag-main-extr
Core rule
Do not start with code changes.
First classify the drift, define the allowed change surface, and write the governing artifacts.
Drift classes
