القائمة
Use when the learner or a maintainer asks to verify this training package's integrity ("validate the training", "is this package intact?"), or when files seem missing, links broken, or authoritative content accidentally modified.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف 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 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.
| name | validating-training |
| description | Use when the learner or a maintainer asks to verify this training package's integrity ("validate the training", "is this package intact?"), or when files seem missing, links broken, or authoritative content accidentally modified. |
node scripts/selftest.mjs
It verifies structure against training-manifest.json, validates the
curriculum, version, and progress-template files against their schemas in
schemas/, checks that every curriculum path and relative Markdown link
resolves, that identifiers are unique and stable-format, and that no
template placeholders survive.git status --porcelain — anything modified outside workspace/ and
state/ is suspect. Offer git checkout -- <path> to restore, after
confirming the change wasn't intentional.state/progress.json is implicated, use
node scripts/progress.mjs read / recover rather than editing state by
hand.