菜单
Use this when a course already has course-level goals in course.yaml and the author needs to break it into thematically-focused modules before designing individual lessons.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use this when a course under authoring/outputs is fully designed and needs to be compiled into a runnable pack under runtime/courses. Transforms DSL into the runtime layout without inventing content.
Interview a course author and fill in the course-level section of course.yaml for a new claude-teacher course. Use this as the first step of authoring a new course, before any modules or lessons are designed. Outputs a course.yaml skeleton that /design-module and /design-lesson will extend.
Deep-dive interview to design a single lesson within a claude-teacher course. Produces the lesson.md body, rubric.md, hints.md (with a graduated hint ladder), and examples.md. Use after /design-course and /design-module, when the author is ready to flesh out a specific lesson.
Use this as a QA pass before shipping a compiled course. Checks hint ladders, rubric signals, lesson length, submission paths, and completion criteria, then files a report. Does not auto-fix.
Mid-lesson progress check for claude-teacher. Compares the learner's current artifacts against the lesson rubric, updates the progress file, and tells the learner what's still missing. Does NOT mark the lesson complete — that is /review-submission. Use when the learner says "I think I'm done", "can you check where I am", or when they run this directly.
Start a claude-teacher course. Run this once, in the Teacher Terminal, before the learner begins. Verifies the course exists, checks prerequisites, initialises the progress directory, and proposes the first lesson. Use when a learner says they want to "start a course", "begin learning X", or when they run this command directly.
| name | design-module |
| description | Use this when a course already has course-level goals in course.yaml and the author needs to break it into thematically-focused modules before designing individual lessons. |
| argument-hint | [course-id] |
| allowed-tools | Read, Edit, Grep, Glob |
Given an existing authoring/outputs/<course-id>/course.yaml that has course-level
goals (title, summary, learning_outcomes) but an empty or missing modules: array,
this skill interviews the author and populates the module breakdown. It does NOT
design the contents of individual lessons — that belongs to /design-lesson.
This skill assumes /design-course has already run and produced the course shell.
$1 (course-id) must be provided. If missing, stop and ask the author.authoring/outputs/<course-id>/course.yaml. If it does not exist, instruct
the author to run /design-course first and stop.authoring/templates/course.yaml to confirm the canonical modules: shape.learning_outcomes list. Each outcome should map to at least one module.checkout_question.lesson_ids is a placeholder list of stub ids (e.g. mod-1-lesson-1) — do
not invent lesson titles or content.Edit to update authoring/outputs/<course-id>/course.yaml in place,
replacing or filling the modules: array. Preserve all other top-level keys
(id, title, summary, learning_outcomes, etc.) exactly./design-lesson <course-id> <lesson-id> for
each stub lesson id.modules:
- id: kebab-case-id
title: Human Readable Title
summary: One or two sentences of thematic focus.
checkout_question: A single question that gates module completion.
lesson_ids:
- mod-1-lesson-1
- mod-1-lesson-2
runtime/.course.yaml.When this skill finishes:
authoring/outputs/<course-id>/course.yaml has a populated modules: array
where every entry has id, title, summary, checkout_question, and a
non-empty lesson_ids list of placeholder ids.learning_outcome in the course is covered by at least one module.