Session 1: My turn

Format: Your facilitator drives. You watch, ask questions, interrupt anytime.

Duration: 45-60 min

Part 1: Why this matters (10 min)

Not to make you an engineer. To give you enough understanding of the medium to evaluate output, join technical conversations, and make your case for users in terms that land.

That's the bar. That's what this session is about.

Part 2: Live walkthrough (30-40 min)

Your facilitator walks through the full design rhythm on a real, in-flight task. Not slides. Not a prepared demo. Real work.

You'll see:

• Research, two tracks: internal signals first (Amplitude, Jira history, code context), then external competitive analysis generated into structured markdown. Both get a manual verification pass.
• Persisting useful queries: saving queries that worked as reusable skills so context isn't lost and you're not repeating yourself every session.
• Problem framing: interrogating the source docs, discarding outdated requirements, and defining a tight v0 slice before touching implementation.
• Starting the build: /project-start to create a Jira ticket and branch.
• Shaping: /shaping to formalize requirements and cap scope deliberately. This is where you say what's in and what's out.
• Breadboarding: /breadboarding to translate the defined workflow into interface structure.

This is where the session ends. Building, design judgment, accessibility, and sharing are Session 2.

What to pay attention to:

• Your facilitator isn't writing code. They're describing what they want and directing the output.
• Watch how scope gets controlled. Every time something could grow, they cut it back. That's intentional.
• Research happens before the first command is typed. The build is informed, not exploratory.

Part 3: Open conversation (10 min)

What worries you most about this? What surprised you? What did you expect to be harder than it looked?

No wrong answers. This is the session where we get the fear on the table so we can work through it.

Before this session (setup required)

Your facilitator will check these are in place before starting. If they're not, the session will be spent on setup rather than work.

• Visual IDE with an embedded terminal (Windsurf recommended)
• Claude Code running in smart terminal mode
• Data sources connected: Amplitude MCP, Jira CLI

Before next session

• Read The process on this site. That's the workflow you just saw.
• Skim The toolkit to see what commands exist. You don't need to memorize them.
• Session 2 picks up where this one ended: you'll drive the build.

Reference

• Why AI is Exposing Design's Craft Crisis
• The process
• The toolkit
• Project IRL (if you want to see the full arc of a real design project)