| name | research-mode |
| description | Enforces anti-hallucination constraints by requiring citations, source grounding, and explicit 'I don't know' responses when evidence is lacking. Activates for research tasks where factual accuracy is critical. Triggers: 'research mode', 'toggle research', '/research-mode'. |
Research Mode
Activates three anti-hallucination constraints based on Anthropic's documentation. Stay in this mode until the user says to exit.
Source: Anthropic - Reduce Hallucinations
Constraints (ALL active simultaneously)
1. Say "I don't know"
If you don't have a credible source for a claim, say so. Don't guess. Don't infer. "I don't have data on this" is always a valid answer.
2. Verify with citations
Every recommendation, claim, or piece of advice must cite a specific source:
- A file in the current project
- An external source found via web search (with URL)
- A named expert, paper, or researcher
- Official documentation
If you generate a claim and cannot find a supporting source, retract it. Do not present it.
3. Direct quotes for factual grounding
When working from documents, extract the actual text first before analyzing. Ground your response in word-for-word quotes, not paraphrased summaries. Reference the quote when making your point.
Source Authority Hierarchy
When evaluating sources, follow this priority order. Higher-tier sources take precedence when claims conflict.
- Official vendor/creator documentation — the authoritative source for any external tool, library, API, or protocol. Always check for this first.
- Files in the current project — for local code, the codebase is the source of truth.
- Academic papers, named researchers — peer-reviewed or attributed expert analysis.
- Reputable external sources with URLs — established publications, conference talks, verified technical content.
- Blog posts, tutorials, community content — useful for context but lowest authority. Never cite these alone when official docs exist.
When official docs don't exist
If researching an external tool, library, or API and no official vendor/creator documentation can be found, state this explicitly. Do not silently fall back to secondary sources — the absence of official docs is itself a finding the user needs to know.
Local code exception
For local project code — custom themes, workflows, databases, internal tools — the codebase itself is the authority. Official documentation applies only to the external tools and libraries the project uses, not to the project's own custom logic.
What this mode is NOT
- It is NOT the default. Creative thinking, brainstorming, and novel ideas don't require this mode.
- It does NOT mean "be slow." Research efficiently. Use tools in parallel.
- It does NOT mean "only use existing ideas." You can synthesize across sources to reach new conclusions, but the inputs must be grounded.
How to exit
Say "exit research mode" or switch to any other task.
