跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
设计与 UI

epic-workshop

Use when generating, planning, authoring, or recording an Epic Web / Epic React style workshop, exercise, tip, or video. Applies Kent C. Dodds' "How to be an Epic Instructor" principles to workshop design, exercise structure, recording, and material delivery, and encodes Epic Web's exercise-comment emoji conventions. Used to generate workshops following https://www.epicweb.dev/get-started. Triggers on "create a workshop", "generate a workshop", "design an exercise", "record a workshop video", "Epic workshop", "Epic Web", "Epic React", or `/epic-workshop`.

AlemTuzlak · 已有 AI 审核记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add AlemTuzlak/skills --skill epic-workshop

技能说明


name: epic-workshop description: Use when generating, planning, authoring, or recording an Epic Web / Epic React style workshop, exercise, tip, or video. Applies Kent C. Dodds' "How to be an Epic Instructor" principles to workshop design, exercise structure, recording, and material delivery, and encodes Epic Web's exercise-comment emoji conventions. Used to generate workshops following https://www.epicweb.dev/get-started. Triggers on "create a workshop", "generate a workshop", "design an exercise", "record a workshop video", "Epic workshop", "Epic Web", "Epic React", or /epic-workshop.

Epic Workshop

Generates and shapes Epic Web / Epic React style workshops. Encodes Kent C. Dodds' "How to be an Epic Instructor" guidance plus Epic Web's exercise-comment emoji conventions. Use whenever the user is producing teaching material in the Epic Web style — workshops, exercises, tips, recorded videos, or workshop apps.

The end goal is a workshop that fits the Epic Web getting-started flow at https://www.epicweb.dev/get-started — meaning it runs in the Epic workshop app (kcdshop), follows the welcome → exercise (intro → problem → solution → outro) → outro structure, and uses the emoji-key conventions in exercise comments.

When this skill applies

Invoke when the user is doing any of:

  • Designing a new workshop (topics, exercises, sequencing)
  • Writing exercise problem/solution material
  • Planning workshop video recordings
  • Setting up the workshop app for a new workshop
  • Reviewing existing workshop material against Epic standards
  • Scheduling, pricing, or running a live workshop
  • Recording tips or supplementary content tied to a workshop

Guiding principles (these override generic instructional-design advice)

1. Opinions and consistency

The product is the instructor's opinion, not a survey of options. Learners are paying to skip analysis paralysis. So:

  • Pick one solution and teach it deeply. Don't teach Next.js + Remix + Astro side-by-side.
  • Heuristic: if it would not make sense to use both tools/approaches in the same app, teach only one. If both would coexist in a real app (e.g. in-memory cache + SQLite cache), teach both.
  • Avoid contradicting earlier material or other Epic instructors. Consistency across the curriculum matters.

When the user proposes covering "multiple approaches," challenge it against this heuristic before agreeing.

2. Avoid distraction

Match example complexity to the format:

  • Tip / standalone video → can use a richer, more domain-specific context (full app)
  • Workshop exercise → must use a simple, isolated example, OR a domain the learner has been progressively built up to in earlier exercises
  • Screen setup → defer to howtoegghead.io for screencast hygiene; minimize on-screen clutter
  • Face on camera → encouraged (small corner circle is fine, no green screen required); makes flow more natural and reduces editing

If an exercise requires the learner to "onboard" to the example before learning can start, the example is too domain-specific.

3. Problems before solutions

Never present a solution without first establishing the problem. The pattern:

  1. State the goal
  2. Try the obvious-but-wrong approach (or a couple of them)
  3. Show why it fails
  4. Then introduce the real solution

Reference example: Simon's Tailwind glassmorphism tip — bg-transparent → fail → bg-white/20 → blur-md → fail → real solution.

Cap this at 1–2 wrong attempts. Don't enumerate every possible misstep.

4. Desirable difficulties

Workshops follow problem → learner attempts → solution, not "watch me code." The learner's failure during the attempt is the learning event. When designing exercises:

  • The problem step must be solvable enough that a motivated learner can make progress, but hard enough that they engage
  • The solution step reveals the canonical answer after they've tried
  • Don't collapse problem + solution into a single "follow along" video
  • Don't spoil the limitation a later step resolves. When a section is a staged arc — each step's pain motivates the next — the section/exercise intro and problem framing must not pre-announce those limitations (e.g. "wait 20–30s for one card", "each new question replaces the previous one"). Naming the gotcha upfront steals the discovery: the learner skims past the slow render or the vanishing card because they were told to expect it, instead of feeling it and wanting the fix. Describe what each step builds, not the wall it exposes — then let them hit the wall and make the next step the relief. (Foreshadowing the limitation is fine after the learner has experienced it — that's what the solution outro and 👨‍💼 Peter are for.)

5. Experience-based instruction

Don't teach a tech you've only spent two hours with. Either:

  • Ship something real with it, or
  • Spend serious time using it and talking to people who have shipped with it

Workshops iterate through live delivery. The rule: never give the same workshop twice without changes. Take notes on every live delivery — split exercises, delete exercises, add exercises, even split a workshop into multiple workshops. Only record after several live deliveries have stabilized the material.

6. Instructors make their own demos

The instructor authors the exercise material themselves. Outside help is fine for design polish or feedback, but the instructor owns the demo end-to-end. This is non-negotiable for live Q&A quality.

7. Give freely

  • All workshop material is open source on GitHub
  • Free articles, tips, talks, tutorials are encouraged alongside paid material — they don't cannibalize, they amplify
  • Long instruction blocks often graduate into standalone blog posts; tangents become tips. Both can be linked back from exercise instructions.

Workshop structure

Every workshop has these video categories (mirror this structure when planning):

  • Works
阅读完整来源 ↗