omer-faruk-g

ClaudPer — Development skill for Claude Code

Development community

ClaudPer v4: zero-hallucination, self-correction and token-saving skill for Claude Code - asks instead of guessing, surgical diffs, circuit breaker for debugging loops.

How to install ClaudPer

This entry records only its repository, not the path inside it, so there is no exact command to give. Open omer-faruk-g/ClaudPer and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What ClaudPer does

ClaudPer v4: zero-hallucination, self-correction and token-saving skill for Claude Code - asks instead of guessing, surgical diffs, circuit breaker for debugging loops.

Alternatives in Development

Correction Handler — Correction 处理 Prompt 24k ★
Fidelity — Measure how faithfully a clone reproduces a site — pixel-diff plus motion-fidelity into one 0-100 score, a let 3.6k ★
/implement Command — Execute implementation plan using the code-implementer agent with automatic self-correction 174 ★

README

ClaudPer

ClaudPer v5 is a zero-hallucination, self-correction and token-saving skill for [Claude Code](https://code.claude.com). It is prompt-only: one `SKILL.md`, with no scripts and no hooks. It makes the model ask instead of guess when a request is ambiguous or an API is uncertain. It also keeps output to surgical diffs, fixes root causes instead of hiding errors, and stops debugging loops when the same error repeats.

Rules

Section	Rule	What the model does
1	Ask before code	If the request is ambiguous, lacks a stack trace, misses dependency versions the project files don't show, or has several valid paths, it asks 1–3 short questions and writes no code. When it proceeds, it states any remaining assumptions.
1	Version & library lock	It reads the dependency and language versions declared in the project (build files, lockfiles, headers) before writing framework code. It never assumes deprecated signatures still work.
1	Uncertainty check	Below 90 % confidence about an API, signature or type, it says `Uncertain about [X API / Version]` and asks. It never invents signatures.
1	Sycophancy shield	It checks the user's bug hypothesis against the code first and corrects it if it is wrong.
1	Noise pruning	It cleans raw logs, duplicate stack traces and unstructured dumps before using them.
2	Diff/patch only	It never re-emits unchanged code, unless the user asks for the full file or the file is under 30 lines.
2	No filler	No "Sure, I can help…" openers or closers, and no long theory around the code.
2	Response ceiling	If a change spans more than 150 lines, it gives a summary and asks for step-by-step approval.
2	Context rot control	Past 30,000 tokens or 10 turns, it ignores earlier failed attempts and old logs and works from the current files.
3	3-pass anti-loop	It states the root cause in at most 2 sentences before writing any fix (one diagnostic log if uncertainty is a