s5-B1-1 pb-cover Design AI Clinic
Drill the levers · extract YOUR DS · lock M2 spec.
Design AI Clinic — drill the levers · extract YOUR DS · lock M2 spec
s05 · Betterworks · 90m · Designers ·
released
s05 → 6 blocks, 28 slides, 19 trainer notes, 5 exercises, 0 reflects, 1 quizzes, 2 asides
Pre-read
- Pre-flight your **Figma access into Claude** *(by Sunday evening)*:
- **Option A** — `claude mcp list` in terminal returns a Figma server entry
- **Option B** — Claude.ai Project shows a Figma connector active
- Either works tonight. Paste your confirmation in cohort chat so PG sees who's set up.
- Confirm your **Claude.ai plan tier supports Skills**:
- Pro / Max / Team / Enterprise with **code execution enabled** — Settings → Features
- If you see a "Skills" or "Upload" section under Features, you're set
- If not, you can still ship today via the inline-markdown fallback (we'll cover it)
- Have your **team's Figma file** open — DS components, tokens, the works
- Bring **one of YOUR real screens** the Critic can audit
- Bring **any document you have describing a BW user/segment** (persona doc, ICP note, even a Slack thread) — we'll use it to mint your Skill
- Open the **S05 shared folder** (link in your cohort home): contains the gdoc with 3 tabs (Tokens · Persona · Final Skill) and the starter Skill bundle you'll rename + repackage
Anyone whose pre-flight blocks Sunday gets a fallback `pace-tokens.json` baseline pre-shared. You'll still ship.
- **Option A** — `claude mcp list` in terminal returns a Figma server entry
- **Option B** — Claude.ai Project shows a Figma connector active
- Either works tonight. Paste your confirmation in cohort chat so PG sees who's set up.
- Confirm your **Claude.ai plan tier supports Skills**:
- Pro / Max / Team / Enterprise with **code execution enabled** — Settings → Features
- If you see a "Skills" or "Upload" section under Features, you're set
- If not, you can still ship today via the inline-markdown fallback (we'll cover it)
- Have your **team's Figma file** open — DS components, tokens, the works
- Bring **one of YOUR real screens** the Critic can audit
- Bring **any document you have describing a BW user/segment** (persona doc, ICP note, even a Slack thread) — we'll use it to mint your Skill
- Open the **S05 shared folder** (link in your cohort home): contains the gdoc with 3 tabs (Tokens · Persona · Final Skill) and the starter Skill bundle you'll rename + repackage
Anyone whose pre-flight blocks Sunday gets a fallback `pace-tokens.json` baseline pre-shared. You'll still ship.
Session goal
By end-of-session each designer has:
1. **Practiced the three Critic moves** — persona-lens critique, token validation, voice rewrite — at speed
2. **Extracted YOUR team's tokens** into a Claude-readable contract, pasted into the **Tokens ↓** tab of the S05 gdoc
3. **Minted a BW persona doc**, pasted into the **Persona ↓** tab of the S05 gdoc
4. **Packaged + uploaded a BW Critic Skill to your own Claude.ai** — renamed the starter bundle, dropped in your tokens + persona + spec, ZIPped, uploaded via Settings → Features
5. **Co-locked the M2 spec** — the 3-tab gdoc IS the M2 spec; S06 opens with it on screen
The room walks out with one shared artifact (the 3-tab S05 gdoc = M2 spec) and each designer walks out with two personal artifacts (a BW Critic Skill live in their own Claude.ai + a persona doc they can re-use).
1. **Practiced the three Critic moves** — persona-lens critique, token validation, voice rewrite — at speed
2. **Extracted YOUR team's tokens** into a Claude-readable contract, pasted into the **Tokens ↓** tab of the S05 gdoc
3. **Minted a BW persona doc**, pasted into the **Persona ↓** tab of the S05 gdoc
4. **Packaged + uploaded a BW Critic Skill to your own Claude.ai** — renamed the starter bundle, dropped in your tokens + persona + spec, ZIPped, uploaded via Settings → Features
5. **Co-locked the M2 spec** — the 3-tab gdoc IS the M2 spec; S06 opens with it on screen
The room walks out with one shared artifact (the 3-tab S05 gdoc = M2 spec) and each designer walks out with two personal artifacts (a BW Critic Skill live in their own Claude.ai + a persona doc they can re-use).
Recap five levers · "your DS not Pace's" · M2 arc
9 itemsOpen cold. Recap what S01–S04 gave the room. Frame tonight as sharpening + shifting from Pace as canon to YOUR team as the subject.
s5-B1-2 list What you walked out with from S01–S04
Five levers · you have these · we're sharpening tonight.
- Harness on purpose — Claude.ai for chat-shape work · Claude Code for file/repo-shape work · Figma Make for canvas exploration
- Claude Code in your terminal — Skills, file context, Project memory · the dev-shape design loop
- Model switching + usage tracking — Sonnet daily · Opus for judgement · Haiku for volume · know your spend
- Tokens as guardrails — the DS is the contract · Critic refuses off-system values · names the token
- … 1 more
s5-B1-3 activation Before we start — your S04 reflection
Reflection + rating on your S04 page.
s5-B1-4 section Three things you'll do today
Sharpen the Critic · build YOUR DS into Claude · co-author M2.
s5-B1-5 list Today's arc
One session · three layers.
- Sharpen — three Critic moves at speed · Pace as the dummy DS
- Build YOURS — extract your tokens · mint your persona Skill
- Co-author — the M2 spec · S06 opens with it
Persona-lens critique on a bad mock
9 itemsHand the room a known bad mock. Each designer picks a Pace persona, runs the Critic from that lens. Fast warm-up that re-grounds them in the S04 Project.
s5-B2-1 pb-section Would Devi notice what Maya would?
s5-B2-2 split The drill setup
Pace's bad mocks · five Pace personas · your Critic Project.
col 1 · The mocks
Three seeded-bad screens from S04 — already in your Project:
15-bad-today.png
16
col 2 · The personas
Consumer: Maya (Builder) · Raj (Lapser) · Sara (Consistent)
B2B: Devi (Pace for
s5-B2-3 code The critique prompt
s5-B2-4 activation Claim a persona · run the prompt · share the result
One screen · one persona · one output.
Token validation rotation
8 itemsQuick 10-min rotation. Designers paste hex/spacing values into their Project and ask "is this on-system?" Surfaces token drift, builds confidence that the Critic *refuses* unknown values, doesn't invent.
s5-B3-1 section Is this on-system?
One value · one question · one refusal. The Critic doesn't guess — it refuses or names.
s5-B3-2 code The validation prompt
s5-B3-3 activation Run the rotation · three values each
Three pastes · three answers.
Extract YOUR tokens with Figma
10 itemsThe room shifts from Pace to YOUR DS. Two paths into Claude — Figma MCP or Figma connector. Each designer extracts their team's tokens and appends to a baseline.
s5-B4-1 section Figma → Claude · two paths · same destination.
Ship a tokens file that's yours.
s5-B4-2 table Two paths · pick what you have running
Both end at the same place — a tokens contract Claude refuses against.
col 1
col 2 · Figma MCP server
col 3 · Figma connector
s5-B4-3 code The extraction prompt
s5-B4-4 activation Extract YOUR tokens
The conflicts list is the artifact · the tokens file is the muscle.
Persona doc · Skill spec · ZIP + upload
16 itemsThree steps. Pace is the reference; everything you produce is BW. By the end you have a renamed, repackaged Skill ZIP uploaded to your own Claude.ai — invocable across all your Claude conversations.
s5-B5-1 pb-section YOUR Skill in Claude.ai
s5-B5-2 split What's in the bundle (S05 folder)
Unzip · rename to your team's skill · work inside.
col 1 · What you see when you unzip
your-design-skill/ ← rename this to your skill name
ref/ — Pac
col 2 · The repackage move
1. Unzip · rename your-design-skill/ to e.g. bw-design/
2. Inside, rename pace-d
s5-B5-3 code 1. Mint your persona doc
s5-B5-4 code 2. Generate your SKILL.md from Tabs 1 + 2
s5-B5-5 code 3. Package the ZIP
s5-B5-6 code Add your Skill to your Claude Design Project
s5-B5-7 activation Three steps · ship your Skill
Persona doc → Skill spec → ZIP + upload.
The 3-tab gdoc IS your M2 spec · cross-read
9 itemsFinal 8 min. By now each designer has filled their slots across the gdoc's three downloadable tabs (Tokens ↓ · Persona ↓ · Skill ↓). That's the M2 spec. The closer is the social moment — read each other's, react, commit.
s5-B6-1 section The 3-tab gdoc IS your M2 spec.
Cross-read · react · S06 opens with it on screen.
s5-B6-2 list What the 3 tabs together give you
Same pattern as S03's M1 spec lock — co-authored, in-class, no homework.
- Tokens ↓ — each designer's tokens chunk · the DS contract
- Persona ↓ — each designer's BW persona · the lens
- Skill ↓ — each designer's SKILL.md spec · the packaged refusal rule
s5-B6-3 activation Cross-read · react
Read at least 2 other designers' rows across all 3 tabs. React 👍 to one row per tab that sparks something for your own work.
s5-B6-4 statement Walk into Wednesday
Three tabs · one gdoc · your M2 spec. Your tokens. Your persona. Your Skill. S06 opens with this on screen.
s5-B6-5 pb-thankyou (no title)
After this session
- **Test your Skill on a new screen** — pick a BW screen you haven't critiqued yet · invoke your Skill in a fresh claude.ai conversation · does the refusal hit when you ask about an unknown persona?
- **Fill in your `[?CONFIRM]` persona flags** — those are Monday's spec-harden list · brief your design lead
- **Skim 2 other designers' tabs** in the S05 gdoc before Wednesday — your pod opens S06 with this gdoc on screen
- **Brief your pod PM** on what's in your three tabs — your Tokens row + Persona row + Skill spec IS your M2 brief
- **For S06 (Wed 24 Jun):** bring your live Skill URL/name + your three gdoc tab entries
- **Failure-mode recovery (trainer-side):**
- **B4 token extraction stalls** for 5+ designers at min 50 → cut Build 2 (B5) sub-move 3 (package + upload) and let designers ZIP + upload at home tonight. The persona doc + Skill spec in the gdoc are the load-bearing artifacts; the upload is a 5-min home move.
- **Plan-tier blocks Skills upload** for 4+ designers → switch the room to the inline fallback (drop files into existing Design Project + reference in custom instructions). Same artifact, different home.
- **If BW does NOT confirm 90-min extension:** drop Drill 2 (token validation) and trim B5 sub-move 3 to "ZIP and upload at home tonight." The 3-tab gdoc closer (B6) is non-negotiable — it's what S06 opens with.
---
## Open items (for polish pass / PG review)
1. **Audience extension confirmation** — duration is set to 90 min in frontmatter; BW confirmation lands by Sunday. If they hold to 60 min, see the trainer-side failure-mode trim above.
2. **Pre-flight Sunday in cohort chat** — PG drops the `claude mcp list` / Figma connector check ask AND the Settings → Features Skills-upload check Sun evening. Sets the room up to walk in working.
3. **Starter Skill bundle in S05 folder** — PG pre-stages this Sunday at `https://drive.google.com/open?id=12Kkr71UrC2GIwdi0u1oYxhqzJVB59PRo`:
- `pace-design-critic/` folder containing:
- `SKILL.md` — scaffold with name/description/ROLE/TASK/OUTPUT/REFUSAL sections, Pace as the example
- `tokens.json` — Pace tokens as the example (designers replace)
- `personas.md` — Pace personas as the example (designers replace)
- `brand-voice.md` — Pace voice as the example (designers lightly edit)
- The S05 3-tab gdoc (Tokens · Persona · Final Skill) — pre-populated with column headers and one Pace example row per tab
- A 1-page `README.md` in the folder explaining the rename + replace + ZIP + upload moves
4. **3-tab gdoc URL** — `[?CONFIRM]` placeholder in B6 activation slide. PG creates the gdoc inside the S05 folder Sunday, drops URL in chat at session start. Each tab gets a row per registered designer.
5. **Activation count** — 6 activations (S04 reflection · persona-lens critique · token validation rotation · token extraction · persona+skill build+upload · cross-read lock) across 4 surfaces (link-click · chat-paste · chat-paste · chat-paste · chat-paste+upload · gdoc). Passes §17 floor (≥4 for 90 min · ≥3 surfaces).
6. **Pace de-emphasis** — explicit on the title and B2/B5 framing. Pace is "the reference" (B2 personas, B5 starter bundle structure); BW is "the destination" (B4 tokens, B5 persona doc + Skill upload, B6 M2 spec). Every slide says "YOUR DS / YOUR persona / YOUR Skill / YOUR M2."
7. **§29 callback in quiz** — q01 explanation invokes the §29 "file is the contract, not the model's recall" principle. After s05 delivers and if §29 isn't yet promoted to `design-principles.md`, drop it in as a cohort-derived rule.
8. **Skills upload mechanic verified** — claude.ai Skills upload via Settings → Features (ZIP with folder at root, Pro/Max/Team/Enterprise with code execution). Per-user (not workspace-shared). Per Anthropic platform docs at https://platform.claude.com/docs/en/agents-and-tools/agent-skills/overview · checked 2026-06-20. Aside in B5 captures this for the room.
- **Fill in your `[?CONFIRM]` persona flags** — those are Monday's spec-harden list · brief your design lead
- **Skim 2 other designers' tabs** in the S05 gdoc before Wednesday — your pod opens S06 with this gdoc on screen
- **Brief your pod PM** on what's in your three tabs — your Tokens row + Persona row + Skill spec IS your M2 brief
- **For S06 (Wed 24 Jun):** bring your live Skill URL/name + your three gdoc tab entries
- **Failure-mode recovery (trainer-side):**
- **B4 token extraction stalls** for 5+ designers at min 50 → cut Build 2 (B5) sub-move 3 (package + upload) and let designers ZIP + upload at home tonight. The persona doc + Skill spec in the gdoc are the load-bearing artifacts; the upload is a 5-min home move.
- **Plan-tier blocks Skills upload** for 4+ designers → switch the room to the inline fallback (drop files into existing Design Project + reference in custom instructions). Same artifact, different home.
- **If BW does NOT confirm 90-min extension:** drop Drill 2 (token validation) and trim B5 sub-move 3 to "ZIP and upload at home tonight." The 3-tab gdoc closer (B6) is non-negotiable — it's what S06 opens with.
---
## Open items (for polish pass / PG review)
1. **Audience extension confirmation** — duration is set to 90 min in frontmatter; BW confirmation lands by Sunday. If they hold to 60 min, see the trainer-side failure-mode trim above.
2. **Pre-flight Sunday in cohort chat** — PG drops the `claude mcp list` / Figma connector check ask AND the Settings → Features Skills-upload check Sun evening. Sets the room up to walk in working.
3. **Starter Skill bundle in S05 folder** — PG pre-stages this Sunday at `https://drive.google.com/open?id=12Kkr71UrC2GIwdi0u1oYxhqzJVB59PRo`:
- `pace-design-critic/` folder containing:
- `SKILL.md` — scaffold with name/description/ROLE/TASK/OUTPUT/REFUSAL sections, Pace as the example
- `tokens.json` — Pace tokens as the example (designers replace)
- `personas.md` — Pace personas as the example (designers replace)
- `brand-voice.md` — Pace voice as the example (designers lightly edit)
- The S05 3-tab gdoc (Tokens · Persona · Final Skill) — pre-populated with column headers and one Pace example row per tab
- A 1-page `README.md` in the folder explaining the rename + replace + ZIP + upload moves
4. **3-tab gdoc URL** — `[?CONFIRM]` placeholder in B6 activation slide. PG creates the gdoc inside the S05 folder Sunday, drops URL in chat at session start. Each tab gets a row per registered designer.
5. **Activation count** — 6 activations (S04 reflection · persona-lens critique · token validation rotation · token extraction · persona+skill build+upload · cross-read lock) across 4 surfaces (link-click · chat-paste · chat-paste · chat-paste · chat-paste+upload · gdoc). Passes §17 floor (≥4 for 90 min · ≥3 surfaces).
6. **Pace de-emphasis** — explicit on the title and B2/B5 framing. Pace is "the reference" (B2 personas, B5 starter bundle structure); BW is "the destination" (B4 tokens, B5 persona doc + Skill upload, B6 M2 spec). Every slide says "YOUR DS / YOUR persona / YOUR Skill / YOUR M2."
7. **§29 callback in quiz** — q01 explanation invokes the §29 "file is the contract, not the model's recall" principle. After s05 delivers and if §29 isn't yet promoted to `design-principles.md`, drop it in as a cohort-derived rule.
8. **Skills upload mechanic verified** — claude.ai Skills upload via Settings → Features (ZIP with folder at root, Pro/Max/Team/Enterprise with code execution). Per-user (not workspace-shared). Per Anthropic platform docs at https://platform.claude.com/docs/en/agents-and-tools/agent-skills/overview · checked 2026-06-20. Aside in B5 captures this for the room.
Add ?token=… to the URL.