القائمة
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.
التثبيت باستخدام 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 | pedagogical-compaction |
| description | 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. |
Generic compaction can preserve chit-chat and destroy course state. This
skill applies instructor/compaction-policy.md instead.
Flush durable state first. Anything that must survive but exists only in conversation goes to disk now:
node scripts/progress.mjs complete-activity ...node scripts/progress.mjs add-question "..."node scripts/progress.mjs add-context --topic T --note NCompact with explicit instructions. Run /compact with instructions
drawn from the policy's priority list, for example:
Preserve: course identity and version, current module/lesson/activity, remaining learning objectives, established project facts, exercise state, learner-specific context, unresolved questions. Compress every tangent to one line. Discard conversational narrative. Output a briefing in the shape given by instructor/compaction-policy.md.
Re-ground from files afterwards. The SessionStart hook re-injects the
authoritative summary after compaction; verify against
node scripts/progress.mjs status and the current lesson file before
continuing to teach. Trust files over summarized memory.
Compaction is a resilience mechanism. The durable record is
state/progress.json; if compaction ever loses conversational nuance, the
course continues correctly from disk.