Skill/Coding/Original by Mehansh

Zero Hallucination Coder

Enforces verified reasoning before any code is generated.

What It Does

Requires the model to complete a five phase sequence (Discuss, Map, Decompose, Execute, Verify) before writing code, inspecting installed dependencies and local source rather than inventing hypothetical APIs.

Architecture and Design Rationale

Hallucinated methods and speculative abstractions consume substantial debugging time. Forcing structural discovery eliminates invented syntax at the source.

Attribution: Original engineering by Mehansh Barthwal. Officially merged into the community repository alirezarezvani/claude-skills under Pull Request #870.

When to Activate

•User asks to build, architect, or implement a code feature
•User requests refactoring or structural debugging
•User wants production grade code with zero speculative dependencies

When to Avoid

•Purely theoretical explanations of basic concepts
•Casual syntax questions with no implementation intent

Skill Specification and Runtime Setup

Full Instruction Specification

# Zero Hallucination Coder Specification

## Overview
Requires the model to complete a five phase sequence (Discuss, Map, Decompose, Execute, Verify) before writing code, inspecting installed dependencies and local source rather than inventing hypothetical APIs.

## Rationale
Hallucinated methods and speculative abstractions consume substantial debugging time. Forcing structural discovery eliminates invented syntax at the source.

## Core Principles
* Always verify environment constraints and dependencies before executing.
* Enforce negative constraints and reject speculative abstractions.
* Validate output against stated acceptance rubrics.

## Execution Workflow
1. Discovery: Map requirements and inspect active context.
2. Decomposition: Break down the task into discrete, verifiable phases.
3. Execution: Implement surgical changes preserving existing code architecture.
4. Verification: Test all criteria before declaring completion.