How I Stopped My AI Coding Assistant from Hallucinating (and Saved My Token Budget)

Krishna kant singh — Sun, 17 May 2026 07:04:59 +0000

Every developer using tools like Claude Engineer, ChatGPT, or Lovable eventually hits the exact same wall.

You start a new project, and everything feels like magic. The AI understands your vision, writes clean components, and you’re moving at warp speed. Then week two hits. The codebase gets larger, you add a few nested directories, and suddenly, the AI goes sideways. It forgets how your routing works. It tries to reinstall dependencies you already settled days ago. Worst of all, it accidentally overwrites a feature you already fixed.

If you like switching between models—say, bouncing from Claude 3.5 Sonnet to Gemini 1.5 Pro depending on usage limits—onboarding the new model becomes an absolute nightmare. You waste hundreds of tokens just trying to explain, "No, don't use that database library, use this one."

To solve this, I built a lightweight framework in my root directory called the .ai_context protocol. It keeps the AI grounded, enforces strict guardrails, and drops token bills significantly.

Here is exactly how it works and why you should steal it for your current projects.

The Core Fix: A Router for AI Context
Most people let their AI tools blindly scan their whole workspace or pass massive chunks of code back and forth in the prompt. This burns through your token limit and clutters the LLM's working memory with noise it doesn't need for simple tasks.

The .ai_context protocol changes that by introducing five simple Markdown files at your project root:

Plaintext
your-project-root/
├── .ai_context/
│ ├── README.md <-- The "Router" & Rules
│ ├── completed_features.md <-- Read-only historical log
│ ├── future_roadmap.md <-- The strict backlog
│ ├── architecture_map.md <-- File tree & structural flow
│ └── secrets_manifest.md <-- Tracking env variables safely
The real magic here is the README.md. It acts as a traffic controller. Instead of the AI loading all files simultaneously, the README explicitly dictates when the agent is allowed to open the other files.

If you are just asking for a small CSS bug fix, the AI reads the README, realizes it doesn't need to touch the roadmap or secrets log, and stops right there. Huge token savings.

Why This Actually Works (From a Human Perspective)

Zero-Friction Model Handoffs
When you switch to a brand new AI agent, you don't need to write a massive explanation. You simply prompt it: "Read the .ai_context/README.md and tell me what our next task is." The new model is instantly on track without guessing.
Guardrails Against Hallucination
Because the AI maintains a read-only ledger of what is already built (completed_features.md), it stops inventing weird, duplicate utility functions. It knows exactly what tools are available in the codebase.
Bulletproof Security
We’ve all seen AI agents accidentally hardcode a secret token or an API key right into a client-side file. The secrets_manifest.md keeps a strict map of environment variable locations without ever exposing the actual values. It forces the AI to check your .gitignore configuration before writing backend logic.

How to Set It Up Instantly
If you want to try this out, I made a single-prompt setup script. You just copy the prompt, drop it into your workspace AI agent, and it generates the entire folder structure and populates your current repository layout automatically.

full promt link

If you are building legacy projects, maintaining side hustles, or fully embracing the AI-assisted development loop, this is the missing manual. It takes two minutes to set up, but it completely changes how reliably your AI handles your code.

How are you keeping your workspace agents from drifting out of context? Drop a comment below—I’d love to see how other people are organizing this.

Why I Started Using Anti-Gravity with Supabase and Clerk for My Projects

Krishna kant singh — Sat, 16 May 2026 08:24:05 +0000

While working on modern web projects, I realized that setting up authentication, backend services, and databases separately takes a lot of time. That’s when I came across Anti-Gravity. It made the whole workflow much simpler by working smoothly with Supabase and Clerk.

Instead of spending hours configuring everything manually, I could focus more on building the actual project. The integration felt clean, beginner-friendly, and surprisingly fast. Whether you are building a SaaS product, dashboard, or personal project, Anti-Gravity helps reduce unnecessary setup work and keeps development organized.

DEV Community: Krishna kant singh

How I Stopped My AI Coding Assistant from Hallucinating (and Saved My Token Budget)

Why I Started Using Anti-Gravity with Supabase and Clerk for My Projects