Adoption Model
Four adoption layers
L1: Personal acceleration
Use one primary rule to stabilize your own workflow.
L2: Project consistency
Version .cursorrules in Git and align contributors around one shared baseline.
L3: Team governance
Add templates, change review, and update discipline so rules stay maintainable.
L4: Platform capability
Treat rules as reusable organizational infrastructure across projects.
Progress signals
| Layer | Signal |
|---|---|
| L1 | Fewer repeated prompt instructions |
| L2 | Less style drift in pull requests |
| L3 | Clear ownership and update flow |
| L4 | Reuse across multiple repositories |