Prompt templates turn Markdown files into reusable / commands. Use one when you want to reuse the same prompt without adding executable behavior or a larger set of supporting instructions.
A template can accept arguments and appear in command completion. Pi can load templates from personal configuration, project configuration, an explicit path, or a Pi package. Project configuration loads only after project trust is granted.
Create ~/.pi/agent/prompts/review.md:
---
description: Review staged git changes
argument-hint: "[focus]"
---
Review the staged changes. Focus on ${1:-correctness, security, and error handling}.The filename becomes the command name, so this template is available as /review. The description appears in command completion. If it is omitted, Pi uses the first non-empty line.
argument-hint is optional. Use <angle brackets> for required arguments and [square brackets] for optional arguments.
Run /reload after adding or changing a template in an active session.
Type the template command in the editor:
/review
/review concurrency
Pi expands the template before the resulting text enters the agent. Extensions receive the raw input first through the input event unless an extension command with the same name handles it.
Templates support these substitutions:
| Syntax | Result |
|---|---|
$1, $2, … |
One positional argument |
$@ or $ARGUMENTS |
All arguments joined with spaces |
${1:-default} |
First argument, or a default value |
${@:-default} |
All arguments, or a default value |
${@:N} |
Arguments starting at position N |
${@:N:L} |
L arguments starting at position N |
Arguments follow shell-like quoting, so /review "API compatibility" supplies one argument containing a space.
Place the template in your user or project prompt directory. Conventional prompt directories load direct .md children only.
Settings and packages can select nested Markdown files; a package manifest can narrow discovery with explicit paths and globs. See Settings and Pi Packages for these options.
Project templates become commands in the editor after trust is granted. Review their content before trusting an unfamiliar project. See Security.