Teach: Build a Persistent Learning Workspace

What it does

The source treats teaching as a multi-session workspace rather than a single explanation. It separates the learning mission, resources, numbered learning records, numbered HTML lessons and reference material, with reusable assets and notes. The learner’s current understanding shapes the next activity. Retrieval practice, spacing and interleaving inform lesson design; trustworthy references support factual claims. Mission changes require agreement so the tutor does not quietly substitute its own goal for the learner’s.

When to use it

• Create a continuing TypeScript learning plan for a beginner.
• Practice domain vocabulary through short interactive lessons.
• Resume study using prior errors and learning records.

Step-by-step workflow

1. Agree the mission, starting level and practical learning goal.
2. Collect trustworthy resources and preserve their citations.
3. Prepare a small interactive lesson with feedback appropriate to the learner.
4. Record observed performance and misconceptions in the learning workspace.
5. Choose later retrieval and practice activities from evidence, confirming mission changes.

Example request

Use teach to help me understand SQL joins for analytics work. Start by checking my current knowledge and agreeing a mission. Use cited database documentation. Build a short HTML lesson with two small tables, prediction questions and feedback that explains wrong answers. Record what I actually demonstrate, then propose a later retrieval exercise. Keep the workspace reusable and do not treat fluent reading as proof of mastery.

Worked example

A learner who can repeat the definition of LEFT JOIN may still incorrectly predict which unmatched rows survive. A useful lesson asks for the result of a tiny query before revealing the answer, then explains the retained rows. The learning record should capture the observed misconception, not label the learner as having mastered joins. A later session can mix a new example with a retrieval question from that earlier error. Reference pages remain distinct from the interactive lesson.

What you get

A persistent learning workspace with an agreed mission, cited resources, HTML lessons and evidence-based progress records.

How to evaluate the result

• Verify citations support factual explanations.
• Check activities require retrieval and give useful feedback.
• Ensure records distinguish observed performance from assumed mastery.

What you need

A learner who can participate, a writable workspace, reliable resources and a browser for interactive HTML. Companion format files define the collection’s expected records.

Setup and activation

The publisher documents plugin setup for Claude Code, Codex and Copilot, and manual Agent Skills setup for Gemini CLI and other clients. Choose one distribution method per client to avoid duplicate skills. The engineering collection expects project-specific tracker, triage-label and document-location settings from setup-matt-pocock-skills. Keep referenced companion skills and files available. This catalogue review does not install or run them; scan the exact source before any later installation. Client tools, permissions and subagent support still need separate validation.

Limits and considerations

Generated lessons need factual and accessibility review. A learning record is an observation, not a validated qualification or medical assessment. Respect the learner’s decision to skip a method; do not invent progress or change the mission without agreement.

Related workflows

• Use handoff when changing teaching sessions or clients.
• Use wayfinder only when a large curriculum needs unresolved decisions mapped.

License and reuse

MIT at repository level (Copyright 2026 Matt Pocock). Preserve the copyright and permission notice when redistributing substantial source material; inspect any separately licensed dependencies or assets.

Further reading

• Reviewed SKILL.md (immutable commit)
• Publisher README: setup and compatibility
• Reviewed MIT license