Loading...
Loading...
Found 8 Skills
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.
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'.
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.
Giải thích MỘT thứ (một file, hàm, tính năng, cơ chế, khái niệm, lỗi, hay hệ thống) theo cấu trúc cố định BẢY BƯỚC — Tên gọi → Nguồn gốc → Lý do tồn tại → Cơ chế hoạt động (+ sơ đồ hệ thống & code) → Trade-off → Giới hạn → Vị trí trong toàn bộ hệ thống — và CĂN THEO NGƯỜI NGHE (engineer, sếp/manager, designer, PM, sinh viên, bố mẹ, trẻ 5 tuổi…): cùng bảy bước, đổi độ sâu, từ vựng, phép so sánh, giọng. CHỨNG bước "Cơ chế hoạt động" bằng RUNTIME thật — chạy code với đầu vào cụ thể, thêm instrument/breakpoint (pdb/debugpy · node --inspect · print/log), quan sát state THẬT — thay vì đọc-rồi-đoán, rồi dọn sạch instrument. Gọi khi user nói "teach me", "giải thích", "dạy tôi", "cái này chạy thế nào", "sơ đồ hoá", "ELI5", "explain like I'm…", "giải thích như cho trẻ 5 tuổi", "nói dễ hiểu", "giải thích cho sếp/manager/designer/bố mẹ/vợ tôi…", "làm sao nói với sếp cái này", "/teach-me". KHÁC /onboard-codebase và /join-project (cả dự án → wiki): teach-me phạm vi MỘT thứ, sâu, có sơ đồ, chứng bằng chạy thật, không ghi wiki.
Explains bugs, code flows, protocols, and concepts in a Markdown document with SVG diagrams generated from small text specs, adapted to the reader's level. Use when the user asks for an explanation with diagrams or drawings, says "explain like I'm 5" or "me explica com desenhos", wants an illustrated explanation after not understanding text alone, or wants to change how Doodle explanations look or read (theme, colors, audience, depth).
Deconstruct complex technical concepts, architecture, or code into intuitive physical analogies and beginner-friendly mental models.