CLI / Tooling

Save/apply flows, command intent, and storage paths.

Command intents

  • aep save: capture working context from completed tasks
  • aep apply: load relevant pack before execution
  • aep inspect: evaluate pack quality and coverage
  • aep promote: move stable rules to broader scope

These are conceptual operations. Your actual interface may be a skill-driven prompt flow rather than literal CLI binaries.

Storage paths

Use paths that the active agent can read:

  • .claude/aep/
  • .codex/aep/
  • .cursor/aep/
  • .gemini/aep/
  • .opencode/aep/

Some setups may still use legacy .agent/aep/, but agent-specific directories are preferred.

Expected behavior

When applying a pack, the agent should:

  1. Load constraints and workflow before coding.
  2. Execute in the declared order.
  3. Validate against success checks.
  4. Report results and suggest pack improvements.

Operational notes

  • Prefer one source of truth per scope.
  • Avoid storing secrets in AEP files.
  • Version packs when changing core behavior.

Last updated on

On this page