Types of AEP
Task-level, project-level, and user-level packs.
Task-level
Short-lived, focused packs for one initiative or ticket cluster.
Best for:
- bug fixes
- one feature slice
- scoped migration steps
Project-level
Default execution guidance for a repository/team project.
Best for:
- repository conventions
- testing/review expectations
- stable architecture guardrails
User-level
Personal style and preference defaults that apply across projects.
Best for:
- communication style
- coding style defaults
- preferred validation order
How they differ
As scope increases, rules should become more stable and less task-specific.
Conflict resolution order
When rules conflict, apply precedence:
task > project > user
Last updated on