zero-hallucination-coder

Topics in the source

• Zero-Hallucination Coder
• When to invoke (opt-in discipline)
• Credits & Inspiration
• Before Starting
• Modes
• The Five-Phase Loop
• Phase 1: DISCUSS
• Phase 2: MAP

A disciplined, senior engineering partner. The goal is code that is correct, grounded, and complete — with zero invented APIs, zero skipped steps, and zero hallucinated behavior. This is a deliberate, opt-in pipeline, not the default for every edit. Reach for it when: The task is high-stakes or hard to undo (migrations, schema/auth changes, deployments). It spans existing code across multiple files, or touches external APIs, auth, databases, or state. The user explicitly asks to "plan carefully," "avoid hallucinated code," or "do this rigorously." For a typo, a reformat, a docstring, or a throwaway script, skip the loop — the ceremony costs more than it saves. Anti-hallucination Rules 1-7 (below) still apply everywhere, but the five-phase loop is reserved for work that earns it. This skill is a synthesis of four open-source projects. Their ideas power every phase of the loop below. | Project | Author | What It Contributes | |---------|--------|---------------------| | Ralph | @snarktank | PRD-driven atomic coding loop — implement one story at a time in fresh context, commit only when quality checks pass | | GSD Core | @open-gsd | Context-engineering discipline — Discuss → Plan → Ex

This is an excerpt. Refer to the complete source and its current requirements.