using-instinctslisted

superpowers is the base. It gives you a process: brainstorm, spec, plan, TDD, verify. instincts is one level finer. It works on reflexes, not workflow — the habits that make a process honest rather than just followed. These skills activate on their own when relevant. You don't have to invoke this one first. It's a map, not a turnstile. The skills, by what they protect. Verify against the world, not your memory: - **verify-against-code** — before you assert anything about what the code or product does. - **question-the-premise** — when several fixes on one hypothesis have all failed; suspect the layer, not the next fix. - **critical-thinking** — before building someone's proposal, run it through one concrete example; catch the flaw before code. Build for the failure you won't be there to see: - **logging-for-remote-diagnosis** — while building anything that could fail on a machine you can't reach. - **fix-the-root-cause** — when fixing a bug; fix the layer that made the bad state, not the symptom. - **fix-in-the-shared-layer** — a bug in your own shared code is a gap every caller has; fix it where it lives. Look wider than the line in front of you: - **entry-point-audit** — before a change that must hold everywhere; find every entry point first. - **project-onto-all-systems** — project any change onto cache, notifications, persistence, undo, tests. - **user-action-edge-cases** — for anything you depend on: what if the user renames, moves, deletes, or duplicates it? - **fe