Instructions, skills, and subagents
Instructions, skills, and subagents
Section titled “Instructions, skills, and subagents”Agents Pack manages three kinds of content. You choose where they apply, which coding agents receive them, and which components to install. Agents Pack then renders provider-native files for Claude Code, Codex, and Cursor, and records what it wrote so updates can be previewed, validated, applied, or rolled back safely.
Instructions
Section titled “Instructions”Instructions are durable rules that should guide normal project work. They stay loaded as ongoing guidance rather than a one-off workflow.
The official core pack ships a required instruction set (ap-core-instructions). Official instruction components cannot be forked. For repository-specific additions, put them outside Agents Pack’s managed block or in a user-owned skill.
See Core instructions.
Skills
Section titled “Skills”Skills are focused workflows — for example debugging, API development, plan review, frontend design, documentation refresh, or security auditing.
Every installation includes two required management skills:
ap-manage-agents-pack— inspect and change the installation through the CLIap-create-new-skill— create portable user-owned skills from chat
Browse the full skills catalog.
Subagents
Section titled “Subagents”Subagents are specialized roles — for example code reviewer, backend developer, UX enhancer, or researcher. New user-owned subagents are read-only by default; use --write only when the role must edit the workspace.
Browse the subagents catalog.
How the pieces fit together
Section titled “How the pieces fit together”- Choose repository or global scope.
- Choose coding agents (Claude Code, Codex, and/or Cursor).
- Choose a component selection.
- Agents Pack renders native files and tracks ownership so safety and drift rules can protect your work.
Day to day, you can manage Agents Pack through your coding agent or run the CLI directly.