TL;DR: Stop letting the model guess your architecture. Feed it the actual type definitions and force a contract-first approach for async mocks. Over the years, I've seen devs lose their minds trying to debug hallucinations in async mocks. In my experience, the secret isnt just the prompt, its the context window management. If youre getting garbage back, you probably arent giving it the source of truth. Try this: feed Claude your specific interface definitions or DTOs as a raw text file before you even ask for the test suite. If it doesnt know exactly what the shape of the service response is, it just guesses and breaks your build. I personally started using Keychron Q1 QMK Custom Mechanical Keyboard to keep my typing speed high while iterating through these test definitions, but the real game changer was strictly enforcing a TypeScript setup where the types are the law. Tell Claude to 'only output tests that satisfy these specific interface signatures' and watch the hallucinations drop off a cliff. When you stop treating it like a creative writer and start treating it like a compiler, things just work. Also, if youre running these in a massive dev environment, grab a reliable Logitech MX Master 3S Wireless Performance Mouse so you can navigate those split-screen diffs without losing your place. Honestly, keep the prompt focused on the input/output schema rather than the logic flow and you'll be golden.

Building on the earlier suggestion, I actually think focusing on your hardware workflow helps too! Sometimes these async glitches feel worse when you're fighting your gear. Honestly, grabbing a Logitech MX Master 3S 8K DPI makes navigating massive test files way faster.

• Stop over-relying on the AI for logic
• Map out dependencies manually first
• Use a solid mouse for quick code jumps It makes a huge difference, trust me!

Honestly, stop letting it write mocks from scratch. I had the same issue with async services until I switched my approach. You gotta focus on prompting Claude to use existing test utilities instead of inventing its own logic. I started forcing it to stick to Jest JavaScript Testing Framework patterns, which totally killed those weird hallucinations. Basically, prioritize teaching it to read your service definitions first. If you dont explicitly point it to the interface files, it just guesses and breaks. I usually keep a Logitech MX Master 3S Wireless Mouse right next to me while I watch the output so I can interrupt it the second it drifts. Tell it to use manual dependency injection every time and things get way more stable. Just keep it simple.