About teach
teach is a learning skill for explaining software subsystems in a learner-paced sequence. It combines a code walkthrough with evidence-based design rationale and a prediction check.
Key features
- 01Baseline-based explanation depth
- 02Code walkthrough with file and line citations
- 03Evidence for design decisions
- 04Prediction check to assess understanding
Use cases
- 01Introducing a subsystem to a learner
- 02Explaining why code is structured a certain way
- 03Checking whether a learner can predict behavior
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ yeachan-heo/ oh-my-claudecode --skill teachAfter installing, type/teachin Claude Code to confirm it loaded.
Details
From the project READMETeach
Teaching is how and why composed for a learner: what the subsystem does
and the reasons it is shaped that way, in an order a person can absorb.
Workflow
- Ask the learner's baseline: one question — familiar with the domain, the language, or neither. Size the explanation to the answer.
- How first (
howskill): the walkthrough, entry to exit, cited to file:line, at the depth the baseline supports. - Then why (
whyskill): the 2-4 decisions that shaped it, each with its evidence and the alternative it beat. Human rulings quoted verbatim. - Check the landing: ask the learner to predict one behavior — "if X happens, what does the subsystem do?" A correct prediction ends the lesson; a wrong one names the layer to redo. The check is for pacing, not grading.
Rules
- One new concept per paragraph; jargon defined at first use in one clause.
- Cite code for behavior, cite records for reasons; label anything you inferred.
- Stop when the learner can predict behavior — completeness is not the goal, transfer is.
Comments
Markdown supported