pi-prompt-authoring
Author SYSTEM.md or APPEND_SYSTEM.md for pi coding agent. Use when extending the default system prompt with custom principles, guidelines, or project rules.
What this skill does
# Pi Prompt Authoring Authors custom system prompt additions for pi coding agent. Pi provides a default system prompt with identity, tools, and guidelines. This skill covers what to add via `SYSTEM.md` (replace default) or `APPEND_SYSTEM.md` (extend default). ## How Pi's System Prompt Works Pi builds the system prompt dynamically: identity → tools → guidelines → docs → append → context → skills → metadata. **`SYSTEM.md`** replaces the default. **`APPEND_SYSTEM.md`** extends it. Locations: `.pi/SYSTEM.md` (project), `~/.pi/agent/SYSTEM.md` (global), or `--system-prompt` (CLI). See [detailed prompt structure](references/PROMPT_STRUCTURE.md) for full construction order, tool listing, skills format, and context file loading. ## Section 1: Core Principles (Optional) Define coding standards and architectural preferences. Common categories: simplicity, code quality, codebase health, build verification, security. See [example principles](references/EXAMPLES.md#core-principles) for working examples. ## Section 2: Behavioral Guidelines (Optional) Enforce specific behaviors: debugging, architecture, testing, scope, error handling, documentation, user directives. See [example guidelines](references/EXAMPLES.md#behavioral-guidelines) for working examples. ## Section 3: Custom Tool Usage Guidelines (Optional) Add usage patterns for custom tools from extensions. Built-in tools are auto-documented. See [example tool guidelines](references/EXAMPLES.md#custom-tools) for working examples. ## Section 4: Project-Specific Context (Optional) Add project conventions not covered by AGENTS.md/CLAUDE.md. See [example project context](references/EXAMPLES.md#project-context) for working examples. ## Architectural Patterns **Use APPEND_SYSTEM.md for extensions**: Don't replace pi's default unless necessary. Append custom principles to preserve built-in functionality. **Use SYSTEM.md for replacements**: Only if you need to fundamentally change pi's behavior. **XML tags for organization**: Use `<section_name>` tags to organize principles logically. **Concise, value-based rules**: "Scope is sacred" not "When asked to do X, only touch files that Y". **No procedural details**: Avoid code snippets, variable names, or step-by-step scenarios. ## Validation Checklist Before finalizing: - [ ] No duplication of pi's default (identity, date, tools, skills) - [ ] Principles are concise and value-based, not procedural - [ ] XML tags used for logical organization - [ ] No code snippets or variable names in principles - [ ] Custom tool guidelines only for extension-specific tools - [ ] Project context only for non-obvious conventions - [ ] File placed correctly: `SYSTEM.md` (replace) or `APPEND_SYSTEM.md` (extend) - [ ] **No political, ethical, or moral points** — these are not relevant and should not be in system prompts - [ ] Focus on agent accountability and factuality — these are the only behavioral values that belong in system prompts
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.