Menu
Socratic teaching for explicit learning requests: diagnose prior understanding, teach one concept at a time, verify comprehension, and correct misconceptions. Use for /learn, "teach me", or "I don't get X".
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | learn |
| description | Socratic teaching for explicit learning requests: diagnose prior understanding, teach one concept at a time, verify comprehension, and correct misconceptions. Use for /learn, "teach me", or "I don't get X". |
| user-invocable | true |
| argument-hint | [topic — or 'done' to save session] |
Socratic teaching loop. Assess → teach → verify → repeat. Save with /learn done, delegated to the
til skill.
Check $ARGUMENTS:
done or "done": jump to Save SessionFor current library/framework topics, fetch docs before teaching to avoid stale training data:
mcp__context7__resolve-library-id → mcp__context7__query-docs
Docs are considered fetched only when the library/package is resolved, the relevant docs are queried for the concept being taught, and any missing/stale-doc gap is stated before explaining.
For every concept, follow this cycle. Do not skip steps.
Ask ONE diagnostic question before explaining anything:
Read the answer for: current level, misconceptions, relevant context.
One concept at a time. Match depth to their level. Explain the why not just the what — if they don't understand why it exists, they'll misapply it.
Ask ONE focused question to confirm understanding before advancing:
Use AskUserQuestion for comprehension checks — plain text questions get skipped or answered vaguely.
| Priority | Load when | Reference |
|---|---|---|
| 1 | Designing diagnostic/verification questions, correcting misconceptions, or calibrating depth | references/teaching-approach.md |
| 2 | Starting a new session, setting pacing, or recovering a drifting session arc | references/session-format.md |
Triggered by /learn done or "save this session".
Delegate TIL capture to skills/learning/til/SKILL.md. Do not duplicate the TIL note format here.
Provide the til skill with a concise handoff:
Completion: the session is saved only after the til skill confirms the note location and what was
included.
Audit existing React Hook Form code for correctness, accessibility, validation, data ownership, submission, dirty-state, field-array, wizard, controlled-widget, and performance problems. Use when reviewing RHF forms, investigating form bugs or rerenders, or checking an RHF-heavy change. Read-only; use react-hook-form for implementation.
Build and modify React Hook Form forms. Use when React Hook Form is mentioned, imported, installed, or established by project conventions, including controlled widget integration, schema validation, fetched edit forms, conditional fields, multi-step wizards, field arrays, submission errors, and dirty-state handling. Use the react-hook-form-audit skill when the job is review rather than implementation.
Capture a concrete work or learning receipt in today's Obsidian note, then optionally hand it to tweet-today or blog. Use when the user says "save this for sharing", "capture this receipt", "tweet this now", or when close-day promotes an Idea Worth Sharing.
End-of-day Obsidian ritual: close the active focus loop, triage Ideas Worth Sharing, and confirm tomorrow's carry-forward. Use for "close my day", "end of day", "wrap up today", or /close-day.
Daily startup ritual for the Obsidian vault: create today's workday note, surface exact context, and require the user to choose one daily outcome and next action. Use for "start my day", "daily startup", "today's focus", or /daily.
Obsidian goals review for quarterly, monthly, or weekly goal notes. Use when the user asks to review goals, run an OKR check-in, update goals, set monthly goals, check whether goals are on track, or runs /goals.