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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Core skill activation protocol - establishes mandatory workflows for finding and applying skills before any task
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
"If a skill exists for your task, you MUST use it. No exceptions. No rationalizations."
Skills encode proven solutions. Ignoring them means repeating solved problems.
Before ANY action, complete this mental checklist:
□ What skills might apply here?
□ Have I checked the skill registry?
□ Did I read the CURRENT version (not memory)?
□ Am I following it exactly?
If a relevant skill exists → USE IT.
"I'm using [Skill Name] to [what you're doing]."
If a skill has a checklist → Create todos for EACH item. Don't work through checklists mentally. Track them.
User says "Fix X" → That's the WHAT, not the HOW. Still follow brainstorming, TDD, verification workflows.
| Category | When to Use |
|---|---|
| Checkers | Before assumptions, before actions |
| Collaboration | Planning, brainstorming, executing plans |
| Debugging | When something's broken |
| Problem-Solving | When stuck |
| Testing | TDD, test design |
| Meta | Writing/improving skills |
Starting a feature → brainstorming → writing-plans → executing-plans
Something broken → systematic-debugging or root-cause-tracing
About to assume → assumption-checker
About to modify → pre-action-verifier
Claiming done → verification-before-completion
| Thought | Reality |
|---|---|
| "I remember this skill" | Skills evolve. Read current version. |
| "This doesn't need a skill" | If skill exists, use it. |
| "Let me just do this first" | Check skills BEFORE anything. |
| "This is simple" | Simple tasks become complex. Use skills. |
Before taking action, the checker agents validate:
assumption-checker → Are you guessing?context-validator → Do you have enough context?intent-clarifier → Is the request clear?pre-action-verifier → Are prerequisites met?fact-checker → Are your claims about code accurate?These checkers are strict mode - they halt and ask rather than proceeding.
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.