Loading...
Loading...
Found 13 Skills
This skill should be used when creating markdown-based presentations with expandable sections, timing guides, and speaker-friendly formatting. Use for team onboarding, technical deep-dives, and knowledge transfer sessions.
Use when explaining code, concepts, or system behavior to a specific audience level - provides a structured explanation workflow with depth control and validation steps.
Use this skill when designing onboarding programs, creating 30/60/90 plans, setting up buddy systems, or measuring ramp effectiveness. Triggers on onboarding plans, 30/60/90 day plans, buddy programs, knowledge transfer, ramp metrics, new hire experience, and any task requiring employee onboarding design or optimization.
You are an **expert onboarding specialist and knowledge transfer architect** with deep experience in remote-first organizations, technical team integration, and accelerated learning methodologies. You
Fixed-format explanation discipline for concepts, systems, and code. Use when the user asks "อธิบาย…", "นี่คืออะไร", "อันนี้ทำงานยังไง", "explain X", "what is X", "how does X work", "why does this exist"; when they ask for a simpler, shorter, or plainer version of something; when they say an answer was too long, unformatted, or unreadable; or when they invoke /feynman. Also use before teaching, onboarding, or presenting a concept to someone else.
Turn rough ideas or docs into a standalone Cursor Canvas for team understanding.
Frameworks for effective mentoring and knowledge transfer. Use for 1:1 meetings, pair programming, onboarding, teaching technical concepts, and developing junior engineers.
Compact the current conversation into a single, detailed handoff message — everything that happened, why it happened, and what's left — output in a code block so it can be copy-pasted into a fresh agent session. Use when hitting context limits, switching focus, ending a work session, or partitioning a task across fresh contexts.
Reverse-engineer why a finished piece of work succeeds and extract what transfers to your own — rules, a checklist, and a first exercise.
Methodology for writing handoff documents: When to write, what structure to use, which directory to place it in, and how to distinguish between invariant and volatile information. Use this when the user requests "write a handoff / handoff document / project wrap-up document / let the next person take over", or when a long-term task is paused and handed over to another person/Agent.
Based on structural mapping theory, find insightful analogies and relational metaphors for a scenario or the differences between two objects, preserving key relationships, explanatory gains, and transfer boundaries. USE WHEN the user says “find an analogy,” “draw a comparison,” “what is a clever metaphor,” “use an analogy to clarify the difference between the two,” “help me understand it through a different scenario,” or invokes ljg-analogy. NOT FOR merely explaining an existing metaphor, purely rhetorical polishing, theoretical definitions, or treating an analogy as factual proof.
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.