Loading...
Loading...
Found 5 Skills
What the? Use when the user wants a plain-English breakdown of something technical — the who, what, where, why, and when.
Explain a body of work plainly so a person actually understands it. Runs the `how` and `why` skills and weaves what they find into one clear explanation. Use for 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.
Rewrites assistant talk into plain language a smart adult can follow on the first read: one-sentence gist, one everyday analogy, sentences under 25 words, next action first, and no AI writing tells. Use when asked to "ELI5", "explain like I'm 5", "wait what", "re-pitch that", "in plain English", "dumb it down", "I don't get it", "that didn't land", "I'm lost", "what does that mean", "too technical", "talk to me like I have ADHD", "stop using jargon", or "eli5 mode". For product or marketing copy use copywriting; for docs use docs-writing; for PR titles and bodies use pr-creator.
Explain how something actually works — code, a type, an error, a fix, a design — by tracing the mechanism on concrete values instead of describing it. Also checks whether the user's own account of something is correct.
Use when the user wants an interactive step-by-step HTML walkthrough explaining a complex technical problem (DB error, race condition, design issue, conceptual blocker) using concrete data and manual navigation. Triggers on phrases like "make me a walkthrough", "explain step by step with data", "interactive explanation", "make an animation", "walk me through with real examples", "อธิบายแบบ step by step", "ทำ animation/walkthrough/visualization", "ทำเป็น diagram", "วาด diagram". Do NOT use for one-line clarifications, conceptual Q&A answerable in a paragraph, or simple "what does X mean" questions — only when an interactive HTML artifact would clearly help.