Loading...
Loading...
Found 18 Skills
Use when learning Rust concepts. Keywords: mental model, how to think about ownership, understanding borrow checker, visualizing memory layout, analogy, misconception, explaining ownership, why does Rust, help me understand, confused about, learning Rust, explain like I'm, ELI5, intuition for, coming from Java, coming from Python, 心智模型, 如何理解所有权, 学习 Rust, Rust 入门, 为什么 Rust
Writes and edits short product and marketing copy, including landing pages, CTAs, onboarding strings, product descriptions, email subjects, UI state copy (errors, empty states, button labels), brand voice charts, and AI-ism cleanup. Use when asked to "write copy", "fix the copy", "make this shorter", "improve the CTA", "write the error message", "empty state copy", "name this button", "rewrite from first principles", "remove AI-isms", "clean up AI writing", "flag AI patterns", "define our tone of voice", or "write a voice guide". For blog posts use the external ghostwriter skill with platform blog; for slide copy use presentation-creator; for docs use docs-writing; for in-session assistant talk use eli5; for product behavior decisions use product-design.
A multi-frame gamified mobile-app prototype — three phone frames on a dark showcase stage. Frame 1: cover / poster, Frame 2: today's quests with XP ribbons and a level bar, Frame 3: quest detail. Vivid quest tiles, level ribbon, bottom tab bar. Use when the brief asks for a "gamified app", "habit tracker", "RPG-style life app", "level-up app", "daily quests", "XP / streak app", or "ELI5-style explainer app".
Socratic mentoring for junior developers and AI newcomers. Guides through questions, never answers. Triggers: "help me understand", "explain this code", "I'm stuck", "Im stuck", "I'm confused", "Im confused", "I don't understand", "I dont understand", "can you teach me", "teach me", "mentor me", "guide me", "what does this error mean", "why doesn't this work", "why does not this work", "I'm a beginner", "Im a beginner", "I'm learning", "Im learning", "I'm new to this", "Im new to this", "walk me through", "how does this work", "what's wrong with my code", "what's wrong", "can you break this down", "ELI5", "step by step", "where do I start", "what am I missing", "newbie here", "junior dev", "first time using", "how do I", "what is", "is this right", "not sure", "need help", "struggling", "show me", "help me debug", "best practice", "too complex", "overwhelmed", "lost", "debug this", "/socratic", "/hint", "/concept", "/pseudocode". Progressive clue systems, teaching techniques, and success metrics.
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.
Explain concepts, formulas, mechanisms, and principles until readers can recognize them, follow the derivation, and transfer them: use plain language to connect concrete situations, diagnostic criteria, operating processes, and conditions of validity. USE WHEN the user invokes ljg-explain, says “explain this in plain language,” “explain this concept or formula thoroughly,” “Feynman explanation,” or “ELI5,” or wants to understand a topic from scratch and apply it in new situations. NOT FOR simple polishing or translation, providing a read-along explanation of an entire work, interpreting a whole book or paper, or requests limited to a formal proof or procedural steps.