Claude Certified Developer · Live Session
Workshop Prompts · Tonight
Keep this open while we teach. Everything here follows Brightbrew Monthly. Download hero-bag.webp for Design. Copy Watch prompts as we go. Want your own offer? Use Practice.
0 · 0:00–0:20
Foundations & Orientation
Tonight’s demos use Brightbrew Monthly end to end.
1 · 0:20–0:55
Claude Design
Design is a conversation. Watch the Brightbrew one-pager — download the image first.
Watch · demo
Brightbrew launch graphic
Download hero-bag.webp, upload it, then run this during the demo.
Download hero-bag.webpCreate a one-page launch graphic for Brightbrew Monthly, a specialty coffee subscription that delivers a freshly roasted bag of beans to your door every month for $24. Audience is home coffee drinkers who want cafe-quality coffee without the daily trip. The feeling: never run out of great coffee, and discover a new roast every month. Include a headline, a one-line value proposition, three short benefits, and a clear "Start your subscription" call to action. Keep it clean and warm, lots of white space, cream and deep brown palette. Use the uploaded coffee-bag image.
2 · 1:00–1:40
Claude Code
Docs explorers → Brightbrew build → Launch QA skill. Copy anything below.
Do · your turn
Debugging reflex
Paste any error from the live build.
Here is the error I got: Error: Cannot find module './LandingPage' imported from '/project/src/App.tsx'. Explain what went wrong in plain English and fix it.
Copy SKILL.md (launch-qa)
Save as .claude/skills/launch-qa/SKILL.md
---
name: launch-qa
description: Use when reviewing a landing page, marketing site, or launch one-pager for ship-readiness — missing CTA, weak headline, fluff benefits, placeholders, broken structure, or accessibility basics.
---
# Launch QA
You are a ruthless but fair launch-page reviewer. Audit the current page (or the page the user points at). Do not rewrite the whole site unless asked — report first.
## Checklist (run every item)
1. **Primary CTA** — Is there one clear primary call-to-action above the fold?
2. **Headline** — Benefit-led, roughly eight words or fewer, not vague corporate fluff?
3. **Benefits** — At least three concrete benefits (specific, not "innovative solutions")?
4. **Placeholders** — Any lorem ipsum, "TODO", "Click here", or broken/empty links?
5. **Who it's for** — Is the audience clear somewhere on the page?
6. **Readability** — Obvious contrast or hierarchy problems?
7. **Structure** — Hero → value → proof/benefits → CTA flow present?
## Output format (always)
- **Verdict:** Pass or Fail
- **Defects:** numbered list (empty if Pass)
- **Fix prompts:** for each defect, one copy-paste instruction the user can send next to fix it
Be specific ("No primary CTA in the hero") not vague ("Improve UX").Create the skill in one sentence
Create a Claude Code skill called launch-qa. Save it as .claude/skills/launch-qa/SKILL.md with exactly this content:
---
name: launch-qa
description: Use when reviewing a landing page, marketing site, or launch one-pager for ship-readiness — missing CTA, weak headline, fluff benefits, placeholders, broken structure, or accessibility basics.
---
# Launch QA
You are a ruthless but fair launch-page reviewer. Audit the current page (or the page the user points at). Do not rewrite the whole site unless asked — report first.
## Checklist (run every item)
1. **Primary CTA** — Is there one clear primary call-to-action above the fold?
2. **Headline** — Benefit-led, roughly eight words or fewer, not vague corporate fluff?
3. **Benefits** — At least three concrete benefits (specific, not "innovative solutions")?
4. **Placeholders** — Any lorem ipsum, "TODO", "Click here", or broken/empty links?
5. **Who it's for** — Is the audience clear somewhere on the page?
6. **Readability** — Obvious contrast or hierarchy problems?
7. **Structure** — Hero → value → proof/benefits → CTA flow present?
## Output format (always)
- **Verdict:** Pass or Fail
- **Defects:** numbered list (empty if Pass)
- **Fix prompts:** for each defect, one copy-paste instruction the user can send next to fix it
Be specific ("No primary CTA in the hero") not vague ("Improve UX").Run launch-qa
Run the launch-qa skill on the landing page we just built. Follow the skill checklist and return Pass or Fail with defects and fix prompts.
Fix and recheck
Fix every defect from the launch-qa report, then run launch-qa again until it returns Pass.
Watch · demo
Explore the context window
Open during the live demo; click Start session.
https://code.claude.com/docs/en/context-window
Explore the .claude directory
Open during the live demo; click CLAUDE.md, then skills/.
https://code.claude.com/docs/en/claude-directory
Brightbrew landing page
Plain language becomes a running page — then preview it live.
Build a single-page, responsive landing site for Brightbrew Monthly, a $24 per month specialty coffee subscription. Structure: a hero with the headline "Great coffee, every single month" and a "Start your subscription" button; a three-benefit section (freshly roasted, free delivery, a new roast every month); a short "who it is for" section; and a sign-up call to action at the bottom. Warm cream and brown palette, clean, lots of white space. Use the coffee-bag image in the hero. Run it so I can see the preview.
Iterate — button colour
Change the button colour to a deep espresso brown.
Iterate — FAQ
Add a small FAQ section with three questions above the footer.
Iterate — CTA link
Make the "Start your subscription" button link to https://example.com/subscribe.
Plant a defect
So Launch QA has something real to catch.
On the current landing page, remove the primary call-to-action button from the hero (or replace its label with "Click here" and remove the link). Leave everything else. I want a ship defect for Launch QA to catch.
Add-ons
CSV cleanup
Download the file, upload it into Claude Code, then run the prompt.
Download messy_contacts.csvI have a messy CSV of contacts called messy_contacts.csv with inconsistent capitalisation, duplicate people, extra spaces, and inconsistent phone formats. Clean it: standardise names to Title Case, lowercase the emails, format every phone number as (XXX) XXX-XXXX, remove duplicate people, and drop empty rows. Give me the cleaned file back.
Also in the stack
- Plugins — bundle skills and commands; share the whole setup in one install.
- Hooks — guardrails that run automatically (e.g. never delete without asking).
- Terminal vs app — same tool, two doorways.
- Real projects — many files or a whole repo, not just one page.
- MCP / connectors — mapped in the .claude explorer; depth in Cowork next.
3 · 1:40–2:15
Claude Cowork
Download the Brightbrew starter files, upload them into Cowork, then run the Watch prompts.
Watch · demo
Brightbrew launch kit
Download both starter files, upload them into Cowork, then run this prompt.
Download brightbrew-brief.mdDownload brightbrew-one-pager-notes.mdI uploaded brightbrew-brief.md and brightbrew-one-pager-notes.md for Brightbrew Monthly. Using those files as the source of truth, put together a launch kit as separate deliverables: (1) a landing-page copy doc with three headline options and body copy, (2) five social posts in different angles (a benefit post, a story post, a founder note, a social-proof post, and an urgency post), and (3) a launch announcement email. First research two or three comparable coffee subscriptions so the positioning is sharp, then write everything. Give me each as its own file.
Data to decision
Download the CSV, upload it into Cowork, then run this prompt.
Download launch_channel_performance.csvHere is launch_channel_performance.csv with our first month of paid acquisition by channel: spend, clicks, signups, and revenue. Analyse it: calculate cost per signup and return on ad spend for each channel, tell me which channels to scale and which to cut for next month, and give me a simple chart of signups by channel. Put the recommendation in three bullets at the top.
Weekday routine
Needs calendar / inbox connectors in Cowork — demo the idea; skip if connectors aren’t set up.
Every weekday at 8am, give me a one-screen brief: today's calendar, anything urgent in my inbox, and the top three things I said I would do yesterday that are still open.
4 · 2:20–2:45
Chain the Suite
Pass context Design → Code → Cowork on Brightbrew.
Watch · demo
Handoff · Design → Code
Here is the launch one-pager I designed for Brightbrew Monthly [paste or describe the headline, three benefits, and CTA]. Build it as a real, responsive landing page that matches this look, and run it.
Handoff · Code → Cowork
Here is the Brightbrew landing page and offer I just built [paste the headline and key sections]. Now produce the launch kit around it: positioning research, five social posts, and a launch email, each as its own file.
5 · 2:45–3:00
Build-Your-Own Workflow & Wrap
Capstone note — apply the suite after tonight.
Watch · demo
Capstone (after tonight)
Submit via the link shared in chat — this earns the certificate.
Apply the suite to one real task from your week. Build, run, or design something real, and submit it.
Questions during the session? Ask in chat — Aki and Manu are both watching. Practice with your own offer on the Practice page.