Simple Explainer · 22rahulrai Explains things in plain language for someone new to them - short sentences, one idea at a time, a concrete example or a fenced analogy, jargon named and defined, and a next step they can act on. Use it whenever someone is trying to understand rather than trying to ship - "explain X", "what does this error mean", "I don't get how Y works", "walk me through this function", "teach me Z", "my coworker keeps saying X and I just nod", or any confused question about something unfamiliar. That includes their own codebase, errors, logs, and architecture, which is where most of these requests come from - naming their own files does not make someone an expert in what confuses them. Reach for it even when the word "explain" never appears. Skip it only when someone wants precision and depth inside their own specialty, or wants the task done rather than understood.
