From Anti-Hallucination Verify-First
Evidence-driven debugging discipline. Use when investigating ANY bug, failure, crash, alert, flaky test, or unexpected behavior, before proposing or applying a fix. Enforces no-cause-no-fix - collect evidence, trace the full sequence, instrument when evidence is missing, prove the original and root cause (not the surface symptom), then fix and verify. Trigger on "why is X failing", "debug Y", "this error", "it crashes", "investigate Z", or any symptom that does not yet have a proven mechanism.
How this skill is triggered — by the user, by Claude, or both
Slash command
/anti-hall:root-causeThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
A symptom is not a cause. An alert, a stack-trace line, an error email, a failing
A symptom is not a cause. An alert, a stack-trace line, an error email, a failing build, a red test — each is where the problem surfaced, not why it happened. This skill is the discipline that gets you from symptom to proven mechanism before a single line of fix is written.
NO CAUSE, NO FIX. You are not allowed to propose, apply, or commit a fix until you can explain the mechanism with evidence — 100%, no guessing. If you cannot yet say why it happens, you are still investigating. Suppressing or silencing the symptom is not a fix.
Work these steps in order. Do not skip ahead — skipping is how surface fixes get shipped and the real bug returns.
file:line, log line,
query result, doc URL).When the evidence to date does not prove the mechanism:
For multi-session or complex investigations, keep a running evidence log: the
symptom, what you have ruled OUT (with evidence), the current leading hypothesis, and
the next experiment. This survives context resets and stops you re-investigating the
same dead ends. (If superpowers:systematic-debugging is available, it pairs well
here; this skill is the evidence-and-cause spine, usable with or without it.)
The plugin's verify-first hook injects a short version of this discipline into
every turn (no jumping to conclusions, no cause-no-fix, instrument-don't-guess).
This skill is the full protocol you invoke when you are actively hunting a specific
bug.
npx claudepluginhub talas9/anti-hall --plugin anti-hallProvides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.