菜单
Use at the start of every conversation to establish skill-driven workflows. Ensures relevant skills are loaded before any action or response.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use before any creative work — creating features, building components, adding functionality, or modifying behavior. Explores intent, requirements, and design before implementation.
Use when completing tasks, implementing major features, or before merging. Covers both performing self-review and responding to external review feedback.
Use when starting feature work needing isolation or when completing a development branch — covers worktree creation, setup, and branch finishing.
Use when you have a spec or requirements for a multi-step task. Covers both writing implementation plans and executing them task-by-task with review checkpoints.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when implementing any feature or bugfix, before writing implementation code
| name | pi-superpowers |
| description | Use at the start of every conversation to establish skill-driven workflows. Ensures relevant skills are loaded before any action or response. |
Check for and load relevant skills BEFORE any implementation, debugging, or multi-step work. When in doubt, load the skill.
Use read to load the full SKILL.md for any skill, or the user can invoke /skill:name.
Refer to the <available_skills> block in the system prompt. Match the task against each skill's description. If a skill is relevant, load it with read before proceeding.
Skip the skill check for:
"Build X" → brainstorming first, then planning, then TDD. "Fix this bug" → systematic-debugging first, then TDD for the fix.
You have a todo tool. Use it to:
batch action with groups)start, done, skip, block)summary action)Create a todo list when starting any multi-step workflow.
These thoughts mean STOP — you're rationalizing skipping skills:
| Thought | Reality |
|---|---|
| "This is just a simple question" | Questions are tasks. Check for skills. |
| "I need more context first" | Skill check comes BEFORE gathering context. |
| "Let me explore the codebase first" | Skills tell you HOW to explore. Check first. |
| "The skill is overkill" | Simple things become complex. Use it. |
| "I'll just do this one thing first" | Check BEFORE doing anything. |
Rigid (TDD, debugging, verification): Follow exactly. No shortcuts. Flexible (brainstorming, planning): Adapt principles to context.
The skill itself tells you which.