Course outline design
Skill Ivor-NCUT/course-producer/skills/course-outline-design
面向 Codex Goal 长时运行的课程制作 Agent Skill：课程定位、专家访谈、材料加工、逐字稿、审校与课程海报。
npx -y skills add Ivor-NCUT/course-producer --skill course-outline-designAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 20 days oldThe repository was created 20 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
根据课程定位与证据化知识卡设计成果优先、螺旋递进的课程模块和章节蓝图。Use when the user says 课程大纲、课纲重排、模块设计、成果优先课纲、系统课结构，或 Course Producer 完成知识萃取后进入 outline 阶段。
SKILL.md
2.3 KB, 765 tokens by cl100k_base, as published. Nobody here has run it
成果优先课纲
只生成课程蓝图，不批量写逐字稿。开始前读取定位、知识卡，以及 知识库/方法论/成果优先课纲.md。
执行流程
- 按学员的紧迫程度和使用场景分组，不按知识分类或专家讲述顺序分组。
- 为每组确定最短可用成果：学员学完这个模块能交付什么、采取什么动作、用什么标准判断完成。
- 让第一模块服务最紧急学员并交付独立成果；第二模块必须再交付另一阶段性成果。学员只学前一或前两模块，也能向前行动。
- 把行业背景、长期影响力和创业准备后置，除非定位证据明确要求理论优先。
- 为每章建立教学卡：认知起点、认知终点、挑战情境、所需知识卡、案例/原话、行动和与前后章的桥接。
- 设计螺旋复用：后章明确调用哪些前章概念或产物，并在更复杂情境中升级它们；不要把章节平铺成知识点 1、2、3。
- 检查每个章节所需证据。缺关键案例、方法步骤或事实时引用 knowledge card 的
unknown/claim_to_verify并列为待补，不编造。 - 生成
.course-producer/artifacts/course-blueprint.md，同时写出章节产物清单，供逐字稿阶段按章检查点执行。
模块契约
每个模块必须写清：面向对象、迫切问题、独立成果、完成标准、章节、进入下一模块的条件。每章必须引用支持它的 knowledge_card_id。
完成检查
- 第一模块能让最紧急学员独立拿到可见成果。
- 前两个模块分别解决短期行动与阶段性方向问题。
- 每个模块都有对象、问题、成果、验收标准和下一步。
- 后章对前章概念或产物有明确复用，结构不是分类目录。
- 课程承诺、章节内容与定位边界一致。
- 缺失证据被标记，不存在虚构案例、数字和背书。
完成后把蓝图交给 course-lesson-writing。
What ships with it: 1 file
276 B alongside SKILL.md
agents/
- openai.yaml276 B
Gives 0 of the 12 instructions most design frontend skills give in 765 tokens
Counted across 1,169 of the 1,878 authors here whose files we hold, read 2026-08-07
- Use CSS variables for color consistencyin 72 of 1169, across 23 files
- Commit to one bold aesthetic direction before codingin 72 of 1169, across 27 files
- Match implementation complexity to the aesthetic visionin 70 of 1169, across 20 files
- Add atmospheric background effects and texturesin 57 of 1169, across 9 files
- Use unexpected spatial compositions and layoutsin 56 of 1169, across 8 files
- Implement real working codein 55 of 1169, across 7 files
- Vary themes and aesthetics across different designsin 48 of 1169, across 7 files
- Launch chromium in headless modein 47 of 1169, across 4 files
- Close the browser when donein 47 of 1169, across 4 files
- Run provided scripts with help flag firstin 47 of 1169, across 4 files
- Wait for network idle statein 47 of 1169, across 4 files
- Use descriptive selectors for elementsin 47 of 1169, across 4 files
Said here and by no other author read
- read positioning knowledge cards and methodology before starting
- group modules by learner urgency and use scenario
- define shortest usable outcome for each group
- make first module serve most urgent learners
- deliver independent outcome in first two modules
- postpone industry background and long-term impact
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.