~/.zerotwo), so they’re not shared through your repository. If you want to share a prompt (or want ZeroCode to implicitly invoke it), use skills.
- Create the prompts directory:
- Create
~/.zerotwo/prompts/draftpr.mdwith reusable guidance:
- Restart ZeroCode so it loads the new prompt (restart your CLI session, and reload the desktop app if you are using it).
/prompts:draftpr in the slash command menu shows your custom command with the description from the front matter and hints that files and a PR title are optional.
Add metadata and arguments
ZeroCode reads prompt metadata and resolves placeholders the next time the session starts.- Description: Shown under the command name in the popup. Set it in YAML front matter as
description:. - Argument hint: Document expected parameters with
argument-hint: KEY=<value>. - Positional placeholders:
$1through$9expand from space-separated arguments you provide after the command.$ARGUMENTSincludes them all. - Named placeholders: Use uppercase names like
$FILEor$TICKET_IDand supply values asKEY=value. Quote values with spaces (for example,FOCUS="loading state"). - Literal dollar signs: Write
$$to emit a single$in the expanded prompt.
Invoke and manage custom commands
- In ZeroCode (CLI or desktop app), type
/to open the slash command menu. - Enter
prompts:or the prompt name, for example/prompts:draftpr. - Supply required arguments:
- Press Enter to send the expanded instructions (skip either argument when you don’t need it).
draftpr.md, replacing placeholders with the arguments you supplied, then sends the result as a message.
Manage prompts by editing or deleting files under ~/.zerotwo/prompts/. ZeroCode scans only the top-level Markdown files in that folder, so place each custom prompt directly under ~/.zerotwo/prompts/ rather than in subdirectories.