Zero Hallucination Coder
Runs a disciplined Discuss -> Map -> Decompose -> Execute -> Verify loop that grounds every line of code in verified project structure, never invented APIs or assumed imports.
Before & after
Same prompt, same agent — the only difference is the skill.
I can help you build a payment page. You'll need to handle form input for card details, integrate with Stripe's API, and store the transaction details. I'd write code that calls the Stripe API, handles the response, and updates your database. Let me get started on the implementation. I might use a Stripe SDK for the frontend and backend integration. Here's how I'd approach building the page with form handling and API calls.
PHASE 1: VERIFY EXISTING STRUCTURE ✓ Checked database schema: users table, payments table (has stripe_customer_id, stripe_payment_intent_id) ✓ Checked Stripe keys location: process.env.STRIPE_SECRET_KEY exists, STRIPE_PUBLISHABLE_KEY in env.local ✓ Confirmed existing Stripe methods: stripe.customers.create(), stripe.paymentIntents.create() already used in /api/subscribe PHASE 2: MAP REQUIRED PIECES • Frontend: Stripe Elements (CardElement), no custom card field invention • Backend: PaymentIntents workflow (create → confirm → webhook) • Database: Link to existing payments table on success • Error gates: Decline handling, duplicate prevention via idempotency key PHASE 3: DECOMPOSE (YAGNI ladder) Remove: Custom Luhn validation (Stripe does this) Remove: CVV storage (Stripe tokenizes) Remove: PCI compliance code (using hosted Elements) Keep: Error boundary around failed intents Keep: Retry logic for network failures (3 attempts) PHASE 4: EXECUTE /* app/components/PaymentForm.tsx */ Uses Stripe Elements CardElement, handlePayment() calls /api/payment Intents recovery on component unmount, no orphaned intents /* app/api/payment/route.ts */ Validates existing customer_id, creates intent with idempotency_key Confirms intent server-side, writes to payments table only on success Webhook handler at /api/stripe-webhook catches payment_intent.succeeded PHASE 5: VERIFY ✓ Unit test: Duplicate payment intent + idempotency key → same intent returned ✓ Integration test: Payment flow end-to-end with test card ✓ Error case: Network timeout → payment retried, never duplicated ✓ Database check: All payments wrote payment_intent_id for audit
About this skill
name: zero-hallucination-coder description: Use when Runs a disciplined Discuss -> Map -> Decompose -> Execute -> Verify loop that grounds code in verified structure — no invented APIs, no assumed imports, no placeholder code — with a lazy-senior-dev...
Zero Hallucination Coder
Runs a disciplined Discuss -> Map -> Decompose -> Execute -> Verify loop that grounds code in verified structure — no invented APIs, no assumed imports, no placeholder code — with a lazy-senior-dev YAGNI ladder that deletes unnecessary code before it is written. Use when a coding task is high-stakes, complex, or spans existing code (auth, databases, migrations, multi-file features), or when the user explicitly asks to plan carefully before coding, avoid hallucinated code, or work rigorously. Not for trivial edits, typos, or throwaway one-off scripts — those do not need the full loop.
What you get
- Public GitHub repo (alirezarezvani/claude-skills)
- the zero-hallucination-coder skill folder with SKILL.md. Part of a 337-skill / 30-agent / 70-command install.
Customize your output
- Fork the repo and adapt the skill's instructions and references to your workflow.
Example output
Activates automatically when your request matches Zero Hallucination Coder; chains with the other skills, agents, and commands in the collection.
Best for
Creators, builders, and teams using Claude Code.
SKILL.md preview
---
name: zero-hallucination-coder
description: Use this skill for high-stakes or complex coding tasks spanning existing code — auth, databases, migrations, multi-file features — or whenever the user asks to plan carefully and avoid hallucinated code.
version: 1.0.0
category: Development / Engineering
author: AgentVolt
license: proprietary
tags:
- development
- engineering
---
# Zero Hallucination Coder
Runs a disciplined Discuss -> Map -> Decompose -> Execute -> Verify loop that grounds every line of code in verified project structure, never invented APIs or assumed imports.
## When to use
… (sign up to view the full skill)More development skills
View all Development skills →Generate
Scaffold code, tests, and boilerplate from a short spec.
Performance Profiler
Systematic performance profiling for Node.js, Python, and Go applications.
Threat Detection
Use when hunting for threats in an environment, analyzing IOCs, or detecting behavioral anomalies in telemetry.
Agent Harness
Turns a domain folder of skills into a bounded agentic loop: compile a goal into a task plan, execute with the domain's tools, verify every task, retry within a budget.