Fill in these first
- Topic: [e.g. how DNS works, what an API is, how UPI payments settle]
- Reader: [who they are, e.g. small shop owner, first-year student]
- What they already know: [e.g. uses a smartphone daily, no coding]
- Why they need it: [the decision or task this helps with]
- Length: [e.g. 600 to 900 words]
Task
Write an explainer that a reader with the stated background can follow from start to finish without searching for any term.
Output format
- One-line definition: under 25 words, no jargon.
- Everyday analogy: 60 to 100 words comparing the topic to something the reader already knows, followed by one sentence on where the analogy stops being accurate.
- How it works: four to seven numbered steps, each one or two sentences.
- Why it matters for this reader: a short paragraph tied to the reason given above.
- Glossary:
| Term | Plain meaning |
Include only terms used in the article, at most eight.
- Common misconceptions: three bullet points, each a wrong belief and the correction.
- Check your understanding: three questions with answers written below them.
Quality rules
- Define every technical term the first time it appears.
- Sentences under 20 words on average.
- Accuracy comes first: simplify, but never state something false.
- Use examples from the reader's daily life and region where possible.
- No condescending phrases such as "simply" or "obviously".






