command-authoring

Cross-CLI slash command authoring requires defining expected frontmatter shapes and emission paths for CC, Codex, and Gemini from a single source body. You write the command definition in the authoritative CC source path, keeping the body neutral so it safely emits to all target CLIs.

A sync manifest ensures new slash commands are actually shipped by adding them to the correct tier and handling CLI-specific emit exclusions. It registers commands during authoring to maintain cross-CLI compatibility and proper deployment wiring.

The slash command body guidance enforces a maximum length of 150 lines to prevent crowding out user intent and breaking downstream parsers. Command-body discipline also requires neutral phrasing to maintain compatibility across CC, Codex, and Gemini.

You handle CLI-specific variants using slot-based variant overlays for per-CLI deltas. This approach allows you to manage differences between CC, Codex, and Gemini without rewriting the entire command body for each environment.

You carve out native-primitive commands to avoid shadowing built-in CLI functionalities. Excluding these native primitives from the sync manifest prevents conflicts and ensures custom slash commands do not override existing tool behaviors.

Mandatory YAML or TOML frontmatter fields are required for slash command definitions to satisfy cross-CLI compatibility rules. The specific shapes vary by target CLI, but frontmatter must be present to ensure correct rendering and behavior across CC, Codex, and Gemini.