name: pi-knowledge
description: "Use for questions about Pi and for implementing or changing Pi extensions, skills, themes, prompts, models, providers, packages, SDK integrations, TUI components, keybindings, or environment behavior."
compatibility: "Requires Pi and either bash or PowerShell."
Pi knowledge
Use Pi's installed documentation as the source of truth.
Read paths from the PI_CONTEXT_* environment variables instead of assuming an installation layout.
Resolve only the needed variables with the active shell, for example $PI_CONTEXT_DOCS_PATH in Bash or $env:PI_CONTEXT_DOCS_PATH in PowerShell, then pass the resulting absolute paths to file tools.
Never dump the complete environment.
If neither Bash nor PowerShell is available, state that installed documentation paths cannot be resolved and do not guess them.
Topic map
Overview and CLI: PI_CONTEXT_README_PATH
Extensions: PI_CONTEXT_DOCS_PATH/extensions.md and PI_CONTEXT_EXAMPLES_PATH/extensions/
Package metadata and Pi configuration name: PI_CONTEXT_PACKAGE_JSON_PATH
Read every selected Markdown file completely before answering or implementing.
Follow its relevant Markdown cross-references and read those targets completely too.
Inspect relevant examples before implementing Pi APIs.
If a mapped file moved or is absent, discover its replacement from PI_CONTEXT_README_PATH, the contents of PI_CONTEXT_DOCS_PATH and PI_CONTEXT_EXAMPLES_PATH, and PI_CONTEXT_PACKAGE_JSON_PATH.
Do not silently substitute remembered API behavior for installed documentation.
---
name: pi-knowledge
description: "Use for questions about Pi and for implementing or changing Pi extensions, skills, themes, prompts, models, providers, packages, SDK integrations, TUI components, keybindings, or environment behavior."
compatibility: "Requires Pi and either bash or PowerShell."
---
# Pi knowledge
Use Pi's installed documentation as the source of truth.
Read paths from the `PI_CONTEXT_*` environment variables instead of assuming an installation layout.
Resolve only the needed variables with the active shell, for example `$PI_CONTEXT_DOCS_PATH` in Bash or `$env:PI_CONTEXT_DOCS_PATH` in PowerShell, then pass the resulting absolute paths to file tools.
Never dump the complete environment.
If neither Bash nor PowerShell is available, state that installed documentation paths cannot be resolved and do not guess them.
## Topic map
- Overview and CLI: `PI_CONTEXT_README_PATH`
- Extensions: `PI_CONTEXT_DOCS_PATH/extensions.md` and `PI_CONTEXT_EXAMPLES_PATH/extensions/`
- Themes: `PI_CONTEXT_DOCS_PATH/themes.md`
- Skills: `PI_CONTEXT_DOCS_PATH/skills.md`
- Prompt templates: `PI_CONTEXT_DOCS_PATH/prompt-templates.md`
- TUI components: `PI_CONTEXT_DOCS_PATH/tui.md`
- Keybindings: `PI_CONTEXT_DOCS_PATH/keybindings.md`
- SDK integrations: `PI_CONTEXT_DOCS_PATH/sdk.md` and `PI_CONTEXT_EXAMPLES_PATH/sdk/`
- Custom providers: `PI_CONTEXT_DOCS_PATH/custom-provider.md`
- Models: `PI_CONTEXT_DOCS_PATH/models.md`
- Packages: `PI_CONTEXT_DOCS_PATH/packages.md`
- Environment variables: `PI_CONTEXT_DOCS_PATH/environment-variables.md`
- Release changes: `PI_CONTEXT_CHANGELOG_PATH`
- Package metadata and Pi configuration name: `PI_CONTEXT_PACKAGE_JSON_PATH`
Read every selected Markdown file completely before answering or implementing.
Follow its relevant Markdown cross-references and read those targets completely too.
Inspect relevant examples before implementing Pi APIs.
If a mapped file moved or is absent, discover its replacement from `PI_CONTEXT_README_PATH`, the contents of `PI_CONTEXT_DOCS_PATH` and `PI_CONTEXT_EXAMPLES_PATH`, and `PI_CONTEXT_PACKAGE_JSON_PATH`.
Do not silently substitute remembered API behavior for installed documentation.