zero-hallucination-coder — Claude Code plugin: how to install
Enforces a verified workflow before code generation starts, blocking imagined imports and placeholder functions. Intended for multi-file systems, not small edits.
/plugin marketplace add alirezarezvani/claude-skills
/plugin install zero-hallucination-coder@claude-code-skillsWhat zero-hallucination-coder does
The plugin forces Claude Code to inspect repository structure before touching any files. The workflow moves methodically from discussion and codebase mapping to decomposition, execution, and verification. It follows a lazy-senior YAGNI ladder that strips out redundant components ahead of new implementation. Phantom APIs and placeholder stubs are rejected.
The pipeline merges ideas from the Ralph, GSD Core, Graphify, and Ponytail open-source projects. It categorizes code entities into known, inferred, and unknown groups to prevent hallucinations. For quick one-line changes, this rigorous approach creates unnecessary overhead.
What it helps with
- prevent hallucinated imports and fabricated APIs
- map repository architecture before modifying files
- strip unnecessary code following YAGNI principles
- break complex refactoring into verified steps
Example prompts for the agent
- Refactor the auth service with zero-hallucination-coder without creating phantom imports
- Map repository structure and decompose tasks before altering payment files
- Apply zero-hallucination-coder to clean unused code and implement webhooks
How to install zero-hallucination-coder
Plugin marketplace
/plugin marketplace add alirezarezvani/claude-skills/plugin install zero-hallucination-coder@claude-code-skillsStep by step, with commands for each platform: Claude Code plugins: marketplaces, installing, and building your own
Questions about zero-hallucination-coder
How do I install zero-hallucination-coder in Claude Code?
Add the repository by running /plugin marketplace add alirezarezvani/claude-skills. Next, install the package using /plugin install zero-hallucination-coder@claude-code-skills.
What does the zero-hallucination-coder plugin do?
It enforces a disciplined cycle moving through discussion, mapping, decomposition, execution, and verification. This structure prevents Claude Code from making up missing methods or unverified imports.
When should this coding pipeline be avoided?
Skip it during trivial edits or single-line fixes. The mapping and verification steps are designed specifically for complex multi-file changes where hallucinations cause damage.
Source text
zero-hallucination-coder · MIT
A disciplined coding pipeline that grounds code in verified structure before a line is written: Discuss -> Map -> Decompose -> Execute -> Verify, with a lazy-senior-dev YAGNI ladder that deletes unnecessary code first. No invented APIs, no assumed imports, no placeholder code. Opt-in for high-stakes, complex, or multi-file work; not for trivial edits. Synthesizes four MIT/open-source projects (Ralph atomic loop, GSD Core context engineering, Graphify KNOWN/INFERRED/UNKNOWN mapping, Ponytail lazy-senior hierarchy). Contributed via PR #854.
© Alireza Rezvani · MIT · alirezarezvani/claude-skills
