3.3 KiB
name, description
| name | description |
|---|---|
| teach | Teach a concept through explanations and practice, or maintain a multi-session learning workspace when the user requests an ongoing course. |
Teach
Teach the requested topic at the user's level. Preserve their chosen format and location. A one-off question normally needs an explanation, example, or exercise in the conversation—not a course directory.
Infer the learning objective and starting level from the request and prior work. Ask only when a missing choice would materially change the lesson. Challenge the learner enough to reveal gaps without requiring an intake interview for a clear question.
Lesson design
Focus on a tangible capability. Explain the knowledge needed for it, then offer relevant practice with feedback. Use retrieval, spacing, and varied examples when helpful for retention; do not force interactivity when the user wants a reference or direct answer.
Use trusted primary sources for claims that need verification, especially changing or high-stakes material. Cite them near the relevant claim. Stable concepts do not need a separate research phase before teaching can begin.
Keep exercises and answer choices clear and fair; avoid giving away answers through formatting, without imposing identical word counts. Do not claim the learner completed an exercise or mastered a topic without evidence.
Recommend communities or further resources when they support the user's objective, not as a substitute for answering. Joining, posting, or paying is the user's choice.
Multi-session workspace
Use this mode only when requested or when continuing an established learning workspace. Read its existing mission, notes, and relevant learning records first. Preserve its layout and the user's output choices; create only artifacts needed for the current lesson.
- For a new or changed learning mission, use MISSION-FORMAT.md. Confirm substantive changes to the goal unless the user already requested them.
- When maintaining source recommendations, use RESOURCES-FORMAT.md.
- Record observed progress and non-obvious insights with LEARNING-RECORD-FORMAT.md; distinguish planned work from demonstrated learning.
- Reuse existing lessons and references. If no format is established and reusable browser lessons are wanted, numbered HTML files under
lessons/and concise references underreference/are a useful default, not a requirement. - Store relevant teaching preferences in existing notes without collecting unrelated personal details.
Assets and references
Reuse existing styles or widgets when available. Keep a new lesson self-contained unless actual reuse justifies extraction; do not scaffold a component library for hypothetical later lessons.
Add a reference sheet or glossary when it provides a useful reusable artifact. When recording learned terminology in the workspace glossary, read GLOSSARY-FORMAT.md; distinguish it from a reference dictionary introducing new terms. Keep references aligned with lesson terminology and link them from the relevant lesson. Use accessible semantics, readable layout, and keyboard-operable interactions.
Hand off the lesson or artifact with its location and an appropriate next exercise. Do not open applications, commit files, or publish a course unless that is part of the requested workflow.