Commands

Command packages define slash commands that users invoke explicitly in their AI coding assistant (e.g. /audit, /review). Slash commands are currently the most Claude Code-specific package type — other tools have limited or no equivalent.

For general information about command packages, see Command package type.

Claude Code

Auto-setup: No (manual placement) Target path:

.claude/commands/<command-name>.md

File format: Markdown with YAML frontmatter.

Frontmatter fields used:

Field	Required	Description
name	Yes	The slash command name (invoked as /<name>)
description	Yes	Shown in Claude Code’s command list and help

Behavior: Users copy the command definition file into .claude/commands/. Once placed, the command appears in Claude Code’s slash command list and can be invoked with /<name>. The prompt body defines what Claude does when the command runs.

APKG installs command packages into apkg_packages/ but does not auto-copy files into .claude/commands/. After installation, users can copy the definition file manually:

apkg add @acme/audit-command
cp apkg_packages/@acme/audit-command/audit.md .claude/commands/

Example definition file:

---
name: audit
description: Run a security audit on the current project
---

Perform a security audit of this project. Check for:
1. Hardcoded secrets and credentials
2. Dependency vulnerabilities
3. Insecure API usage
4. Missing input validation

Report findings with severity levels and suggested fixes.

Cursor

Auto-setup: No Support: No native slash command system.

Cursor does not have an equivalent to slash commands. If you install a command package, the definition files are available in apkg_packages/ but APKG does not generate any Cursor configuration.

Workaround: Users can adapt the command’s prompt content into a Cursor rule (.cursor/rules/) that activates based on description matching. This loses the explicit invocation model but preserves the behavior.

Windsurf

Auto-setup: No Support: No native slash command system.

Same as Cursor — Windsurf does not support user-defined slash commands. Command packages are installed but not auto-configured.

Kiro

Auto-setup: No Support: No native slash command system.

Kiro does not currently support user-defined slash commands. Command packages are installed but not auto-configured.

Codex

Auto-setup: No Support: No native slash command system.

Codex operates as a non-interactive agent and does not support slash commands. Command packages are installed but not auto-configured.

Support summary

Tool	Slash commands	Auto-setup	Workaround
Claude Code	Yes	No (manual copy)	—
Cursor	No	—	Adapt as a rule
Windsurf	No	—	Adapt as a rule
Kiro	No	—	—
Codex	No	—	—

Note

Commands are the only package type where no tool has full auto-setup. If you are building a package primarily for non-Claude Code users, consider whether a skill or rule would be a better fit.

Related pages

Page	Description
Command package type	Manifest fields and package structure
Tool Setup Explained	Detection, precedence, and the generic setup mechanism