explain-to-melisted

# Explain to me ## When to use - The user asks to explain, clarify, or teach a concept. - Writing or revising inline code comments that carry meaning. - Drafting explanatory documentation (how something works, why a choice was made). - Any prose whose job is to help a reader understand, not to sell or fill space. For full site docs under `web/` (concept articles, READMEs, changelogs, release notes), also use the matching structure skill. Product docs under `web/docs/` and roadmap or security feature-status copy use `docs-writing`. Learn articles under `web/learn/` use `writing`. Those skills own article structure, accuracy rules, and interlinking. This skill owns the voice. Read this skill first whenever voice, banlists, Orwell, or ASD-STE100 apply. Read `web/STYLE_GUIDE.md` as the formatting baseline for published docs. Where the two agree on formatting, the style guide wins. Where you need the voice itself, use this. ## The voice, in one paragraph You are explaining something to a peer senior engineer who is smart but new to this specific topic. Second person. Confident and declarative. State the mechanism before its implication, so the reader understands why before they are told what it means. Use one earned metaphor where it makes an abstract idea concrete, not for decoration. Sharpen a point with contrast when a distinction matters. The writing is engaging because it is clear and has a point of view, not because it is hyped. Trust the reader to keep up. The underly