Debugging a broken RAG pipeline at 2am, staring at outputs that make no sense, is a very specific kind of frustration. Most of us learn how to handle it through painful trial and error. What if there was a structured, interactive way to sharpen those instincts instead? That’s exactly what this side project is going after. The Redditor behind it, u/Easeac, built a small interactive challenge that simulates real AI system failures and asks you to figure out what went wrong.
The concept is refreshingly focused. Instead of another tutorial or another course, this is a debugging sandbox. You get dropped into broken prompt engineering and RAG scenarios and have to work through fixing them yourself.
What the challenge actually covers
🔧 The creator designed it around problems that LLM developers and prompt engineers actually run into:
- Diagnosing broken prompt setups
- Debugging RAG pipeline failures
- Working through realistic AI system issues
- Applying genuine reasoning, not guesswork
It’s scoped deliberately. No bloat, no gamification theater. Just the core debugging scenarios.
The twist that makes it interesting
Here’s the part that caught my attention: the author specifically asks you NOT to use AI tools while solving it. That’s a bold constraint, and it’s the whole point. The creator wants to see how real people actually reason through these problems, not how well they can prompt GPT-4 to solve it for them.
That single rule turns this from a fun distraction into a genuine skills test. If you’ve been working with LLMs and RAG systems for a while, this is a chance to find out where your mental model actually holds up.
How to get involved
🎯 The pilot is small by design. Here’s the process:
- Head to the original Reddit post in r/PromptEngineering
- DM u/Easeac directly to express interest
- The creator will send you the link if capacity allows
- Work through the challenges without AI assistance
- That’s it, your feedback helps shape whether this idea goes further
A quick note on expectations
This is early-stage. The post is honest about that: the author is running a small pilot to test whether the concept even makes sense. There’s no polished product page, no waitlist funnel, no launch campaign. Just a developer testing an idea with a handful of people who work in this space.
💡 Pro tip: If you work with RAG pipelines regularly, this kind of low-stakes challenge is actually a solid way to audit your own debugging process. Most of us never get structured feedback on how we approach these problems.
It won’t take much of your time, and if the idea has legs, your early input helps shape what it becomes. Check out the original Reddit post to find the discussion and reach out to the creator directly. 🙌
Built a small prompt engineering / rag debugging challenge — need a few testers
by u/Easeac in PromptEngineering