Menú
Structured multi-session teaching — missions, lessons, retrieval practice.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Alpine.js adapter for @stainless-code/alpine-layers; plugin magics, x-layer-outlet, layerStack data, and JS hooks for typed layer stacks
Angular adapter for @stainless-code/angular-layers (signals + DI + imperative renderStack); use when wiring provideLayerClient, renderStack/useStackHandles, useLayerGroup, useMutationFlow, or createStackHook
UI-agnostic layer stack engine for @stainless-code/layers. Use for opening layers imperatively from anywhere, ordered named stacks, typed await or fire-and-forget calls, lifecycle control, blockers, validation, singleton updates, serial or nested layers, multi-stack orchestration, or building a library/framework adapter.
Lit adapter for @stainless-code/lit-layers; open UI from anywhere and manage ordered, named stacks with typed or fire-and-forget `open` via Reactive Controllers and custom elements
Preact adapter for @stainless-code/preact-layers — use for awaitable confirm flows, singleton toasts, nested drawers, stack subscriptions, and custom layer hosts
React adapter for @stainless-code/react-layers; open UI from anywhere and manage ordered, named stacks with typed or fire-and-forget `open`
| name | teach |
| description | Structured multi-session teaching — missions, lessons, retrieval practice. |
| disable-model-invocation | true |
| argument-hint | What would you like to learn about? |
The user wants to learn something over multiple sessions. This is stateful — progress lives in files in a teaching workspace, not in chat memory alone.
Default location: teach/<topic-slug>/ at the repo root (never inside packages/*/src/ package code). User may choose another directory — treat that directory as the workspace root.
Git: workspaces are personal by default — do not commit teach/** unless the user explicitly wants shared onboarding material in the repo (add it to .gitignore otherwise).
State files at workspace root:
| File / folder | Purpose |
|---|---|
MISSION.md | Why they're learning — grounds every lesson. MISSION-FORMAT.md |
GLOSSARY.md | Canonical terms once understood. GLOSSARY-FORMAT.md |
RESOURCES.md | High-trust knowledge + community sources. RESOURCES-FORMAT.md |
NOTES.md | User teaching preferences, scratchpad |
./learning-records/*.md | Decision-grade insights (ADR-shaped). LEARNING-RECORD-FORMAT.md |
./lessons/*.html | Primary teaching unit — one scoped win per file (0001-slug.html, increment) |
./reference/*.html | Compressed cheat sheets for revisit (syntax, flows, glossaries) |
./assets/* | Reusable lesson components (stylesheet first) |
Create directories lazily when first needed.
When the mission is this codebase (core/adapter seam, layer lifecycle, scope/gcTime, rules, skills):
Read / Grep / Glob over packages/*/src/, docs/, .agents/ before parametric guesses.docs/glossary.md and docs/architecture.md; align lesson terms..agents/skills/<name>/SKILL.md or concrete packages/*/src/ paths..agents/README.md, relevant skills, docs/architecture.md) alongside external sources.General topics (Rust, yoga, etc.): never trust parametric knowledge until RESOURCES.md is populated.
Three layers: Knowledge (trusted resources) · Skills (interactive lessons + feedback loops) · Wisdom (communities, real-world practice).
Split fluency (in-session recall) vs storage strength (long-term retention). Design for storage: retrieval practice, spacing, interleaving (skills only).
MISSION.md.open ./lessons/0001-….html on macOS).Before authoring: read ./assets/; reuse is default. Shared stylesheet is the first component every workspace earns — every lesson links it so the course looks consistent. When a lesson needs something reusable (quiz widget, diagram helper), add it to ./assets/ and link — never inline code a second lesson would duplicate.
If MISSION.md is empty or vague, interview the user (one question at a time; recommend an answer) before writing lessons. Revise mission only after user confirms — record shift in a learning record.
Read learning-records/, mission, and glossary → teach the next thing that challenges just enough. User may name a topic directly.
Lessons target a skill; include only knowledge required for it. Knowledge from RESOURCES.md with citations. Skills via quizzes / guided steps with tight feedback loops. Quiz options: equal word count when possible (no formatting clues).
For questions needing real-world judgment, answer then point to communities in RESOURCES.md. Respect if user opts out of communities — note in RESOURCES.md.
Compress lesson essence into ./reference/*.html for revisit. Glossaries live in GLOSSARY.md at workspace root — adhere to terms in all lessons.
grillinggrill-with-docsdomain-modeling