Menu
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").
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional 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 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 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.
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 | regenerating-training |
| description | 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"). |
Regeneration updates the clean training repository for future learners. It never touches existing learner clones — they keep the version they started.
<sourceRoot>/<submodulePath> must contain
training-manifest.json and a .git history. Read its
training-version.json and compare sourceCommit with the current
source HEAD; if identical and no config changed, report that regeneration
is unnecessary and stop.node ${CLAUDE_PLUGIN_ROOT}/scripts/register-submodule.mjs --source <sourceRoot> --path <submodulePath>