wonder-pill

---

Ask Claude for ideas and you get a list. Install Wonder Pill and you get a map of the questions you didn't know you were standing on — plus an interactive mind map you can drag around, showing where every thought came from and which ones got thrown away.

Not an answer. A different kind of side effect.

---

Read this part first

Wonder Pill does not generate good ideas. It is not supposed to.

This matters enough to say plainly, because the failure mode of tools like this is someone installing it, reading the output, thinking "half of this is nonsense," and concluding it's broken. It isn't broken. Half of it being nonsense is the design.

What Wonder Pill produces is raw material for your own thinking. A stepping stool. Some of what comes out will be wild. Some of it will be impractical. Some of it will be, honestly, dumb — the kind of thing you'd be embarrassed to say out loud in a meeting. That's the cost of reaching past the obvious, and it's a cost worth paying, because the obvious answers are the ones you'd have found anyway without any tool at all.

Here's the reasoning. Language models are trained to predict likely continuations. Ask one for "ideas" and you get the statistically likeliest ones, which is another way of saying: the ideas everyone else already got. Every tool built on top of a model inherits that pull toward the center of the distribution. The only way out is to deliberately aim at the tails — and the tails contain both the genuinely novel and the genuinely stupid, because that's what "unlikely" means. You cannot filter for one without losing the other.

So Wonder Pill doesn't try. It generates loosely, marks how far each thread has drifted from reality, and hands you the whole spread. You are the filter. That's not a limitation being apologized for — it's the correct division of labor. You know your budget, your deadline, your skill level, your taste, and what would actually be interesting to you. The tool doesn't and can't.

A few honest expectations:

• Roughly a third of any given map will be useless. Expected. Look at it and move on.
• A third will be interesting but not usable — right shape, wrong context. Still valuable: it usually tells you something about the problem.
• A third will be worth pulling on. That's a good yield for something that took thirty seconds.
• The most useful output is often not a what-if at all but a gut-check line — the note about where the real difficulty hides. Several times in testing, that line reframed what a project actually was. Watch for those.
• If everything on the map seems sensible, something went wrong. That means it collapsed back toward the consensus answers, which is the exact thing this exists to escape.

Judge it by whether it got you thinking somewhere you wouldn't have gone. Not by whether every branch was correct.

---

The problem it solves

Ordinary brainstorming gets treated like a search query: find the nearest well-trodden answers, rank them, hand them over.

> give me science fair ideas

1. Build a solar oven
2. Test which paper towel is most absorbent
3. Grow plants under different colored lights
...

Three things just went wrong:

1. You became the chooser, not the thinker. Your job is now to evaluate someone else's list — which is a much smaller job than the one you actually wanted.
2. You got anchored. Everything you think next is a variation on "solar oven." The first answer eats the space.
3. It never left the training distribution. Those are the likeliest answers. That's not a bug in the model, it's what the model is for — which is precisely why you need something pushing the other direction.

Wonder Pill attacks all three by changing the deliverable. Instead of ideas, you get provocations to think with.

---

What it actually does

> give me science fair ideas

seed: nobody grades a project that isn't finished
   ↓
assumes: a project has to be finished to be judged
→ what if the project were a thing still running — measurements
  arriving during the judging, no known result yet?
   ├─ and the judges watched it change while they stood there
   ├─ and "the result" was whatever it happened to be at 2:47pm
   └─ and you genuinely didn't know if it would work
        └─ so what does a poster board even show?
  gut-check: only interesting if the hard part is the
  unfinishedness, not the topic

scrapped: what if it ran for a year?
  derivation: inverts the deadline
  flaw: the deadline is a hard wall, not a thing you can invert
  judgment: scrapped for generativity — there's nowhere for
  the thread to go once you're standing in "no deadline"

Every what-if is derived by inverting a named assumption — never invented freely. That single constraint is the whole trick, and the reason the output isn't the usual vague "what if you thought bigger?" filler.

The three-part deliverable

And then it stops. No ranking, no "here's my favorite," no quiet convergence back into a recommendation. If you want to land on one, you say so — and then it re-runs the whole audit on just that branch.

---

What's on the map

The map is deliberately not a tidy tree radiating evenly from a center. Real thinking isn't uniform, and a map that pretends otherwise throws away the most interesting information.

• Seed nodes sit outside the branch they caused, further from the center than their own consequence. This is where "why did it think that" lives — a real fact, a historical precedent, an oddity it found while looking around. The map reads inward as well as outward.
• Uneven depth. One branch gets a single hop because the thread ended there. Another goes four deep because it kept opening. A map where every branch is exactly three deep is a map that stopped thinking on a schedule rather than when it ran out of thread.
• Scrapped what-ifs float detached at the edges, struck through, showing where it came from, what's wrong with it, and why that was judged disqualifying — three separate fields, not one blended reason. Kills can only happen