Skip to content

How to use this course

There are three paths. Pick one.

Path 1 — “I have a screen to fix tonight” (60 min)

Section titled “Path 1 — “I have a screen to fix tonight” (60 min)”

You’re shipping a feature this week. You don’t have time to read everything.

  1. Read 02-master-prompts/master-prompt.md. Copy it.
  2. Open Claude Code in your repo. Paste the master prompt.
  3. Open 03-ui-ux-vocabulary/full-cheat-sheet.md in a side window.
  4. When Claude proposes 3 directions, use the cheat sheet to understand the patterns it names.
  5. Pick one. Implement. Verify with the QA prompt.

Done. You’ve used 5% of the course and gotten 60% of the value.

Path 2 — “I want to install this in my team” (one weekend)

Section titled “Path 2 — “I want to install this in my team” (one weekend)”

You want this workflow to be the default for everyone in your repo.

  1. Read all of 01-foundations and 02-master-prompts.
  2. Copy templates/CLAUDE.md to the root of your real project.
  3. Copy 07-skills/ui-pattern-picker/SKILL.md to .claude/skills/ui-pattern-picker/ in your real project.
  4. Walk your team through 08-demonstrations. Pick one to redo on your own product as a team workshop.
  5. Add the 10 prompts to your team’s snippet manager (Raycast, Alfred, Notion).

Path 3 — “I want to actually master this” (one week, 2 hours/day)

Section titled “Path 3 — “I want to actually master this” (one week, 2 hours/day)”

You want to be the person on your team who can name any UI pattern, propose 3 directions for any screen, and direct Claude Code like a staff designer.

Day-by-day:

After day 7, you can name any pattern, propose any direction, and ship UI 100x faster than before.

The numbered folders are a recommended order, not a hard requirement. The vocabulary module (03) is the load-bearing one. If you’re skipping anything, don’t skip that.