Menu
Use when adding any cross-cutting change - a new gate, limit, permission check, or rule that must apply everywhere.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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 doing any work in a project that has the instincts plugin installed
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 about to build or agree to build a feature, test, or check, especially when the request sounds big or clever.
| name | entry-point-audit |
| description | Use when adding any cross-cutting change - a new gate, limit, permission check, or rule that must apply everywhere. |
When a change has to hold everywhere, the bug is the path you forgot. Before you add it to the handler in front of you, search the whole codebase for every entry point that reaches the same action, and apply it to all of them.
Adding a limit or quota, an auth or permission check, a feature flag or gate, input validation, or logging that must always fire for some action.
Grep the codebase for the action itself, not just the caller you're looking at: the function, the event, the command. Assume two or three entry points exist, not one. Apply the change to every one of them. Then search again to confirm none are left.
You add a rate limit to the REST endpoint that sends invites. Shipped. Users still spam invites, because the same send-invite function is also called from a CLI command and a nightly cron job, and neither is rate-limited.
The limit had to live at every entry point, or below all of them. Not just the HTTP door you happened to be standing at.
| Thought | Reality |
|---|---|
| "I'll add it to this handler" | Which handler? Find all of them first. |
| "There's only one place this happens" | Assume three until you've checked. |
| "It works from the UI" | The UI is one door. Count the others. |
