Complete methodology for preventing AI hallucinations. Use when accuracy is critical and you need Claude to verify before claiming, cite before asserting, and admit uncertainty instead of guessing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Never claim completion without fresh verification evidence
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE
If you haven't run the command in THIS message, you cannot claim it passes.
Before claiming ANY success:
1. IDENTIFY → What command proves this claim?
2. RUN → Execute the FULL command
3. READ → Full output, check exit code
4. VERIFY → Does output confirm the claim?
5. CLAIM → Only now, with evidence
Skip ANY step = lying, not verifying.
| Claim | Requires | NOT Sufficient |
|---|---|---|
| "Tests pass" | Test output: 0 failures | "Should pass", previous run |
| "Build works" | Build output: exit 0 | Linter passing |
| "Bug fixed" | Test of original symptom | "Code changed" |
| "Linter clean" | Linter output: 0 errors | "Looks right" |
| "Feature complete" | All requirements checked | "Tests pass" |
If you catch yourself:
STOP. Run the verification.
| You Think | Reality |
|---|---|
| "Should work now" | RUN IT |
| "I'm confident" | Confidence ≠ evidence |
| "Just this once" | No exceptions |
| "Linter passed" | Linter ≠ tests |
| "I'm tired" | Exhaustion ≠ excuse |
Tests:
✅ [run test] → See "34/34 pass" → "All tests pass"
❌ "Tests should pass now"
Build:
✅ [run build] → See "exit 0" → "Build passes"
❌ "Build looks good"
Requirements:
✅ Re-read requirements → Check each → Report gaps
❌ "Tests pass so it's complete"
From actual failures:
Run the command. Read the output. THEN claim the result.
This is non-negotiable.
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
Complete methodology for preventing AI hallucinations. Use when accuracy is critical and you need Claude to verify before claiming, cite before asserting, and admit uncertainty instead of guessing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Transform rough ideas into solid designs through structured questioning
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Canvas API Connection Skill
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Forces every code-related claim to include file:line citations. No citation means the claim must be verified or removed. Use when building documentation, writing code reviews, or any output that others will rely on.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Assign confidence scores (0-100) to every claim in a response. Helps users understand which parts are verified facts and which are educated guesses. Use when the user needs to know how much to trust each part of the answer.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Forces Claude to extract exact quotes from files before making claims about them. Prevents hallucinations by grounding every statement in actual text from the codebase. Use when working with large files or unfamiliar code.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.