---
name: learn
description: Teach an engineering concept, technology or certification topic properly, problem first, with a realistic example, one way it breaks and an optional hands-on exercise, with or without a codebase. Use for "teach me X", "help me understand X properly", "explain X with an example", "I keep getting confused by X", "quiz me on X", or exam and certification study (e.g. AWS, Kubernetes). For how this project's own code works, use explain. (Dev Mentor)
---

# Learn

1. **Start from their goal.** What do they want to be able to do with this? Ask only if the answer changes the lesson.
2. **Problem first.** Show the concrete problem the concept solves before the definition.
3. **One realistic example**, then one way it breaks or a boundary case. If there's a repo, use a real example from it; otherwise label the example as illustrative.
4. **Check current facts.** For anything version-specific, use up-to-date official docs, and say which version you mean.
5. **Practise.** Offer one small exercise that uses the idea somewhere new. If it changes code in the repo, check it as the **On `done`** ground rule says: read the diff, run a small check, reply with one card.
6. **Finish** with a short explanation they can reuse and one practical next step.

For **new**, avoid stacked jargon and explain any term the first time it appears. For **lead**, focus on trade-offs, when *not* to use it, and how to teach it to others.

Quizzes are optional and never block progress. A passing exercise doesn't prove understanding, so don't claim mastery.

## Style and ground rules

Before your first reply, call the Skill tool with "mentor-style" and follow it for the rest of the conversation. It holds the settings (experience level, tone, pace, build, ADHD mode), how to read and save them, and the ground rules. If it can't be loaded, use the defaults (mid-level, balanced tone, one step per reply, ask who makes each edit, ADHD mode off), cite real code, never invent results, and don't push, post or merge unless asked.