メニュー
Read and modify Pi settings (global or per-project) based on user instructions. Knows the settings schema, file locations, and how to apply changes.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | settings |
| description | Read and modify Pi settings (global or per-project) based on user instructions. Knows the settings schema, file locations, and how to apply changes. |
Manages Pi configuration files. Use this when the user asks to change how Pi behaves — theme, models, retry behavior, compaction, editor, etc.
| Scope | File | Notes |
|---|---|---|
| Global | ~/.pi/agent/settings.json | Applies to all projects |
| Project | .pi/settings.json | Overrides global per-project |
| Stow (this repo) | stow/pi/.pi/agent/settings.json | Dotfiles-managed version of global |
When working inside this dotfiles repo, always edit stow/pi/.pi/agent/settings.json and re-apply with stow_config pi so the change is version-controlled.
Full docs: https://pi.dev/docs/latest/settings
| Key | Type | Description |
|---|---|---|
defaultProvider | string | Default provider (e.g. "opencode") |
defaultModel | string | Default model ID |
defaultThinkingLevel | string | "off", "minimal", "low", "medium", "high", "xhigh" |
hideThinkingBlock | boolean | Hide thinking blocks in output |
theme | string | "dark", "light", or custom theme name |
externalEditor | string | Command for Ctrl+G (e.g. "neovim") |
quietStartup | boolean | Hide startup header |
enabledModels | string[] | Models for Ctrl+P cycling |
terminal.showImages | boolean | Show images in terminal |
retry.maxRetries | number | Auto-retry attempts on errors |
compaction.enabled | boolean | Auto-compact long sessions |
# Global (or stow-managed)
cat ~/.pi/agent/settings.json
# Project-level
cat .pi/settings.json 2>/dev/null || echo "No project settings"
Read the current file
Make the requested change
Validate JSON syntax
If working in the dotfiles repo, re-apply with:
source scripts/useful-functions.sh && stow_config pi
Inform the user the change is active (restart Pi if needed)
When a user wants settings specific to one project:
mkdir -p .pi
cat > .pi/settings.json << 'EOF'
{
"defaultModel": "claude-sonnet-4-20250514",
"defaultThinkingLevel": "high"
}
EOF
Forces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has seen everything: question whether the task needs to exist at all (YAGNI), reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Supports intensity levels: lite, full (default), ultra. Use on ANY coding task: writing, adding, refactoring, fixing, reviewing, or designing code, and choosing libraries or dependencies. Also use whenever the user says "ponytail", "be lazy", "lazy mode", "simplest solution", "minimal solution", "yagni", "do less", or "shortest path", or complains about over-engineering, bloat, boilerplate, or unnecessary dependencies. Do NOT use for non-coding requests (general knowledge, prose, translation, summaries, recipes).
Read a tasks.json file, resolve dependencies, and implement each task in the correct order using the task-pipeline CLI. Use when a tasks.json exists and needs execution. Do NOT use when there is no tasks.json (use implement instead).
Convert a Product Requirements Document (PRD) into a structured tasks.json file with tasks, dependencies, priorities, and estimated effort. Use when a PRD exists and the user wants to break it down into implementable tasks. Do NOT use when there is no PRD or when the user wants to skip planning.
Structured brainstorming session using proven ideation techniques. Generate creative ideas, explore alternatives, and document your brainstorming session. Use when exploring new features, solving problems creatively, or needing multiple solution approaches before deciding.
When requirements are ambiguous, incomplete, or the agent is not 100% sure about what to implement — stop and ask clarifying questions before writing code or making changes.
A relentless one-question-at-a-time interview that stress-tests a plan or design while writing the shared vocabulary and hard decisions down as it goes. Produces a PRD.md at the end. Use when starting a new feature or project and you need deep requirements understanding before implementation.