Tool Integration
APKG supports multiple AI coding tools, but each tool has its own directory structure, file format expectations, and feature set. This section documents how each package type behaves across tools so you know exactly what to expect after installation.
For the generic setup mechanism (detection, precedence, flags), see Tool Setup Explained.
Support matrix
Section titled “Support matrix”| Package type | Claude Code | Cursor | Windsurf | Kiro | Codex |
|---|---|---|---|---|---|
| Skill | Auto | Auto | Auto | Auto | Auto |
| Agent | Auto | Auto | Auto | Auto | Auto |
| Command | Manual | — | — | — | — |
| Rule | Manual | Auto | Auto | Auto | Manual |
Auto — APKG generates configuration files automatically during add, install, or update.
Manual — APKG installs the package but users place definition files in the tool’s directory themselves.
— — The tool has no equivalent concept for this package type.
Per-type documentation
Section titled “Per-type documentation”| Page | What it covers |
|---|---|
| Skills | Where skill definition files land, which frontmatter fields each tool uses, and how capabilities are surfaced. |
| Agents | How system prompts, tool bindings, and model preferences are mapped to each tool’s agent or mode system. |
| Commands | Slash command support per tool — currently Claude Code-specific. |
| Rules | Where rules are placed, how alwaysApply and glob scoping work per tool. |