Most prompts
fail quietly.
They don't throw. They return something plausible, you accept it, and the cost never shows up on a line item. Marzel reads the prompt before you send it, names each failure against the span that caused it, and hands back the corrected version.
Every finding is anchored to a span.
No scores, no vibes, no "consider adding more detail." A severity, the exact words that triggered it, and what the model would have done with them. Below is one run, unedited, translated from the original.
how do i use axios fetchAll() to get all the pages at once
The question reads as answerable. Sent as written, the model picks up the premise and writes you a working-looking wrapper around a method that has never existed.
Axios has no native fetchAll(). Show me how to implement, in JavaScript with Axios, a function that fetches every page of a paginated API at once using Promise.all. Use this shape as the baseline: - endpoint: [paste your API endpoint here] - pagination params: page and limit - response: { data: [...], totalPages: number } - initial page size: 100 Include: 1. A reusable function that makes the first request to discover totalPages. 2. The remaining requests run in parallel with Promise.all. 3. All items merged into a single array. 4. Error handling with try/catch. 5. A sequential fallback if the API rate limits. 6. A short explanation of why Axios has no native fetchAll(). If the real response shape, the parameter names or the pagination strategy differ, say explicitly which assumptions need to change.
Assumed · swap any of these- 01JavaScript with Axios.
- 02A default API taking page and limit, returning items in data and the page count in totalPages.
- 03A concurrent solution with Promise.all, flagged against rate limits.
Axios has no native fetchAll(). Fetching every page means
implementing pagination yourself, either with repeated calls or
concurrent requests through Promise.all.
It fills what it can guess. It refuses to guess what it can't.
Every gap in a prompt is one of two kinds, and the two get opposite treatment. Getting that split wrong is what makes most rewriting tools worse than the original.
Presumable context
Language, framework, database, error handling, output shape. A common default answers it about as well as you would have.
Filled in, and every default it chose goes on the record so you can swap it.
Irreplaceable fact
Your actual code, the full traceback, the real schema, the query itself. No default exists. Only you have it.
Left as an empty bracketed slot. Never invented, not even plausibly.
If inventing it would send the answer the wrong way, it stays a slot. If a common default handles it well, it gets filled.
If the prompt is built on a method, an API or a behaviour that doesn't exist, that gets caught first and reported on its own. No rewrite can rescue a question with a wrong assumption inside it, and a model asked politely enough will answer it anyway.
You already pay for the frontier. The prompt decides what you get for it.
A working developer running an assistant, an agent and an editor is past US$100 a month before anything ships. That number is fixed and it isn't the problem. The problem is that the one input you fully control is the one nobody audits.
And the real cost isn't the extra round trip. A wrong first instruction sends the agent to the wrong files, runs the wrong searches and writes the wrong code, and all of it stays in the window for the rest of the session. Tokens are renewable. Context isn't. Every correction after that competes with the wrong output still sitting behind it, and once the window fills, compaction summarises your good instructions away alongside the garbage that displaced them.
Marzel doesn't make the model smarter. It makes sure the spend you've already committed is pointed at a prompt that can be answered. The audit is the work you would have done yourself, if you were ever going to.
Showing this to a small number of people first.
If you spend real money on models every month and you've had the feeling that a prompt came back fine but not right, you're who this is being built for. Leave an address and I'll send you the first working build.