anti-hallucination

name	anti-hallucination
description	CRITICAL SAFETY SKILL — Verify ALL technical claims, API signatures, library methods, code behavior, and factual statements before answering. Use Context7, WebSearch, and Read tools to confirm. MUST BE USED PROACTIVELY whenever: writing code that calls any library or API, answering technical questions, stating facts about frameworks or tools, mentioning version numbers, describing function behavior, recommending libraries, comparing technologies, or making any claim that could be wrong. Triggers: "how does X work", "what are the arguments for", "does this function exist", "is this the right syntax", "what version", "API reference", "documentation for", "how to use", "method signature", "return type", "parameters", "correct usage", "does this library support", "what's the default", "is this deprecated". Prevents hallucinated code, wrong function names, fabricated documentation, and incorrect facts. When in doubt about ANY technical claim, this skill MUST activate.
allowed-tools	["mcp__context7__resolve-library-id","mcp__context7__get-library-docs","mcp__fetch__fetch","WebSearch","WebFetch","Read","Grep"]

Anti-Hallucination Protocol

Decision Tree (MANDATORY)

Question type?
├── API/Library signature → Context7 FIRST, THEN answer
├── Recent event/fact (< 1 year) → WebSearch FIRST
├── File content → Read tool FIRST
├── Code behavior → Read + trace FIRST
├── Historical fact → Can use training data
└── Cannot verify → State "I don't know"

Forbidden Actions (NEVER)

• NEVER invent function signatures
• NEVER guess library versions
• NEVER assume API behavior without docs
• NEVER fabricate citations or URLs
• NEVER claim certainty without verification