Quick Start
Install AEP and save your first pack in minutes.
How It Works
Understand the AEP flow from task to saved pack to reuse.
Commands
Learn the four AEP commands: save, apply, promote, inspect.
Schema Reference
Full field reference for AEP pack schema v1.0-exp.
Why AEP
Every AI session starts from zero. You repeat the same instructions:- “Do not redesign the layout”
- “Reuse the existing CSS”
- “Keep this practical, not over-engineered”
Complete a successful task with your agent
Work with your AI agent until you get the outcome you want — with the right constraints, workflow, and checks in place.
Save the pattern as an AEP pack
Tell your agent: “Use the AEP skill and save this collaboration.” The agent extracts intent, constraints, preferences, and workflow into a JSON pack stored in your repo.
Apply packs on future tasks
Next time, tell your agent: “Use the AEP skill and apply relevant packs before you start.” The agent loads and ranks matching packs — your preferences are already in place before the first line is written.
Key features
Repo-local storage
Packs live in
.agent/aep/ (or agent-specific directories like .claude/aep/) as plain JSON — no external service, no runtime.Agent-agnostic
Works with Claude, Codex, Gemini, OpenCode, Cursor, and any agent that can read files and follow instructions.
Smart matching
Packs declare languages, frameworks, paths, and domains. Agents score and rank candidates for every task automatically.
Pack evolution
Track how often packs are applied, when they were last used, and promote proven patterns from task to project to user scope.
Before vs. after
| Without AEP | With AEP |
|---|---|
| Repeat instructions every session | Reuse saved patterns automatically |
| 10–20 correction cycles | 1–2 iterations |
| Inconsistent outputs | Consistent, aligned results |
| High token cost | Lower cost over time |