Menu
Pi slash commands, prompt templates, workflow skills, or command placement. Not for skill authoring; use skills-engineer.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
| name | pi-command |
| description | Pi slash commands, prompt templates, workflow skills, or command placement. Not for skill authoring; use skills-engineer. |
Use pi-command for command surface and placement decisions. Use skills-engineer for generic skill quality, frontmatter, or activation trigger editing.
| Need | Preferred surface |
|---|---|
| Prompt-only slash command | pi/prompts/<name>.md (frontmatter, auto-discovered) |
| Workflow command with TS logic or state | pi/extensions/ registration + body in pi/skills/workflow/<name>.md (no frontmatter) |
| Structured tool-backed command | pi/extensions/ |
| Shared Claude/OpenCode wrapper | claude/commands/ only when cross-client support is requested |
| OpenCode override | opencode/commands/ |
Keep command-specific model instructions in the owning prompt template, workflow skill, or extension. Do not place them in pi/AGENTS.md; reserve AGENTS for repository-wide rules that apply independently of the active command and tool set.
Pi-first rule: when improving agent runtime features, implement in Pi unless the request is explicitly Claude/OpenCode-only.
Stateful commands must be idempotent and use locked read-modify-write plus atomic writes for shared .pi/*.json files. Reset commands must target exact owned files, never broad globs.
A command whose output is visible to the user must persist that output or a faithful summary in model context. UI-only notifications, widgets, and overlays are defects when they contain state the model cannot read back.
claude/ as a proxy for Pi behavior.Pi extensions and tool policy: extensions/*.ts, hooks, registerTool, promptGuidelines, registerCommand, footer/status UI, tool_result, session hooks, or subprocesses. Not for slash-command placement; use pi-command.
README, CHANGELOG, docs/, RFCs, ADRs, guides, or Markdown structure. Not for prose cleanup or archival work.
Prose cleanup for filler, hype, vague claims, repetition, detection tells, or uncited specifics. Not for Markdown architecture or archival work.
Requirements, user stories, acceptance/verification criteria, or testable outcomes. Not for PRD drafting (/prd) or Pi /goal prompts.
Use for /prd-it or to draft, refine, or review a Product Requirements Document. Not for acceptance criteria, planning, or Pi /goal prompts.
Pi session, trace, metrics, routing, workflow-friction, workflow-telemetry, usage, or local JSONL analysis with DuckDB. Use for aggregating or correlating Pi runtime logs. Not for adding telemetry, generic SQL/database design, or non-Pi logs.