القائمة
Use when doing any work in a project that has the instincts plugin installed
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when about to show any prose a human will read - docs, README, commit bodies, UI copy, store text.
Use when building any mechanic that could fail on a machine out of reach - a shipped product, a CLI a user runs, a server.
Use when touching build scripts, release or packaging steps, publish flows, or CI config.
Use when about to build something someone proposed, especially when the proposer sounds confident and the idea sounds obviously fine.
Use when adding any cross-cutting change - a new gate, limit, permission check, or rule that must apply everywhere.
Use when about to build or agree to build a feature, test, or check, especially when the request sounds big or clever.
| name | using-instincts |
| description | Use when doing any work in a project that has the instincts plugin installed |
superpowers is the base process: brainstorm, spec, plan, TDD, verify. instincts is one level finer — a set of working reflexes that keep that process honest rather than just followed. This skill is the map to them.
Load an instinct with the Skill tool the first time it applies in a session — before you act on it. Announce "Using [instinct] to …" and follow the skill you loaded. If several instincts hit the same move, load them all in one response.
Once loaded, a skill stays active for the rest of the session: apply it without re-invoking. One exception — after a context compact, if you can no longer see the skill's full text, it's gone; reload it before relying on it.
Acting on an instinct that was never loaded this session is working from memory, and it doesn't count: you lose the current text and the checklist, and nothing shows the reflex ran — exactly how corners get cut. Nothing runs until you call the Skill tool. The load is once per skill per session; the cost argument is spent.
| Rationalization | Reality |
|---|---|
| "I applied it internally — same result" | If it was never loaded this session, you worked from memory, not the current text. No checklist, no trace. |
| "The map line below tells me enough" | The map routes, it doesn't teach. The method lives in the skill. |
| "Loading it won't change what I'm about to type" | Then it costs seconds and confirms you. When it would have changed something — that's the whole point. |
| "No time for ceremony right now" | One load per skill per session, seconds each. You'll spend longer justifying the skip. |
| "I loaded it earlier" — said after a compact | If you can't see its full text anymore, it's gone. Reload before relying on it. |
| "superpowers already forces skills, so these are covered" | Not covered — each instinct still gets its own first load. |
| You named an instinct in your reasoning without ever loading it | Naming it is not running it. Load the skill, then proceed. |
User instructions — CLAUDE.md, AGENTS.md, direct requests — take precedence over any instinct here, and instincts take precedence over default behavior. Never cite an instinct against what the user explicitly asked for; skip a skill only when they told you to.
Load the one that matches the move you're about to make.
Verify against the world, not your memory:
Build for the failure you won't be there to see:
Look wider than the line in front of you:
Design for real conditions, not the happy path:
Finish honestly:
These sit on top of superpowers, the base process, installed separately (/plugin marketplace add obra/superpowers, then /plugin install superpowers). Without it, instincts works standalone — the reflexes just have less process around them.
