Welcome

You already know AI coding tools can ship code. That’s not the problem.

The problem is that most teams use them like autocomplete instead of like a design partner. They type “make this dashboard better,” get a slightly cleaner version of what they had, and ship something that still feels like a prototype.

This course flips that.

The shift

Before this course	After this course
”Make the dashboard better."	"Inspect the dashboard. Diagnose the layout, navigation, and data display. Give me 3 directions before coding.”
One mediocre output.	Three meaningful options + tradeoff analysis + recommendation.
You point vaguely at “menus.”	You name the pattern: dropdown menu, command palette, toolbar, context menu, split button.
Claude invents a new button component.	Claude reuses your existing components and tells you which to extend.
You ship and hope.	You verify with typecheck, lint, responsive review, and a11y review.

What you’ll walk away with

A master prompt you paste at the start of every UI session.
A vocabulary cheat sheet that names every pattern you’ve been pointing at.
A prompt library of 10 expert prompts for the situations you keep hitting.
A CLAUDE.md template that bakes the workflow into your repo.
A Claude Skill (ui-pattern-picker) that maps vague requests → real patterns automatically.
Four demonstrations showing the full loop: vague idea → shipped UI.

What this course is not

It’s not a UI library. It’s not a Figma tutorial. It’s not a course on React.

It’s a course on how to talk to Claude Code so it does the work of a product team — and how to learn the language of UI/UX while you ship.