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.
From context-groundingnpx claudepluginhub a-ariff/ariff-claude-plugins --plugin context-groundingThis skill uses the workspace's default tool permissions.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Details PluginEval's skill quality evaluation: 3 layers (static, LLM judge), 10 dimensions, rubrics, formulas, anti-patterns, badges. Use to interpret scores, improve triggering, calibrate thresholds.
Read first. Quote second. Claim third. Never skip a step.
Before making any claim about code, follow this sequence:
Read the actual file. Don't work from memory.
Pull the exact text that supports your claim. Include line numbers.
Now state what you believe, citing the quote as evidence.
Wrong approach: "The auth middleware checks for JWT tokens and returns 401 if invalid." (No evidence. Could be hallucinated.)
Grounded approach: "Reading src/middleware/auth.ts:15-25, the middleware does:
const token = req.headers.authorization?.split(' ')[1];
if (!token) return res.status(401).json({ error: 'No token provided' });
So it extracts the Bearer token from the Authorization header and returns 401 if missing."
Always ground when:
For files over 100 lines:
For files over 500 lines:
Before sending a response, test each factual statement: "Could someone verify this by reading the file I'm referencing?"
If yes: the statement is grounded. If no: you need to add the file reference and relevant quote. If you don't have a file to reference: either find one or mark as unverified.