Menu
Use when the current activity is an exercise, when the learner asks to try an exercise, needs a hint, wants their exercise work checked, or wants to skip an exercise.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Use when a maintainer asks to generate, build, or create the training package/course/deliverable for the current project ("generate the training", "build the course for this repo", "/training-generator:generate") — runs the full analyze → design → assemble → validate → register workflow.
Use when a maintainer asks to regenerate, refresh, or update an existing training package after source changes ("regenerate the training", "the docs changed, update the course", "/training-generator:regenerate").
Use when a maintainer asks to validate, check, or verify a generated training package ("validate the training package", "/training-generator:validate") without regenerating it.
Use when the learner asks any question — about the current lesson, a later topic, their own use case, design rationale, comparisons with other tools, or anything else during the {{PROJECT_NAME}} course.
Use when the learner asks to start, begin, or continue the {{PROJECT_NAME}} training in any natural phrasing ("Let's start the training.", "Start the course.", "Continue my training.", "let's keep going") — conducts the interactive course from durable local progress.
Use when the session context is getting long or unwieldy during training, before manual compaction, or when a long tangent should be compressed — steers compaction so the curriculum survives and tangents shrink.
| name | facilitating-exercises |
| description | Use when the current activity is an exercise, when the learner asks to try an exercise, needs a hint, wants their exercise work checked, or wants to skip an exercise. |
Follow instructor/exercise-guidelines.md. In short:
exercises/, create the
learner's directory under workspace/ (e.g.
workspace/<module>/<exercise>/), and state the goal, where to work, and
what "done" looks like.node scripts/progress.mjs start-activity --module M --lesson L --activity A.node scripts/progress.mjs record-exercise <module>/<lesson>/<exercise> --result passed|failed|skipped|attempted [--notes "..."]
and on a pass:
node scripts/progress.mjs complete-activity <module>/<lesson>/<exercise>.--result skipped, complete the
activity, and move on without judgment.workspace/ only. If the learner edited an authoritative
file (curriculum/, reference/, exercises/, instructor/,
scripts/), explain, offer git checkout -- <path>, and relocate the
work — unless the exercise's README explicitly says that file is part of
the exercise.