Get an analogy that actually makes a concept click, not a generic one
Most analogies map to nothing you actually know. Anchor it to what you do know.
- Use it for
- Anyone stuck on a concept where every explanation so far hasn't landed.
A generic analogy (explaining a database index as "like a book's index") works for people who already have a rough sense of the concept, and does little for someone actually stuck — it's not wrong, it's just not anchored to anything specific to them. The analogies that actually make something click are built from something the learner already deeply understands, which means the same concept needs a different analogy for a chef than for a musician than for a parent.
This prompt asks for the analogy to be built from your specific background, not a generic one that's supposed to work for everyone.
When not to use this
If you already basically understand the concept and just want a quick refresher, a standard explanation is faster than building a custom analogy. This is for the concept that's stayed stubbornly confusing across a few explanations already.
Did this work?
The analogy uses something from your actual background, and you can point to specifically where the concept "clicked" rather than just nodding along.
Tested on claude-opus-5. Evidence status is draft; it moves to battle-tested only on recorded runs, never by hand.