The argument in one line.
Splitting data analysis from design generation — using CoWork to build the data layer and design brief, then Design to render it — is what makes AI-produced dashboards genuinely agency-grade rather than generic one-shot outputs.
Read if. Skip if.
- You work with financial or ecommerce data and need to present findings to clients, boards, or teams without a dedicated BI team.
- You are a consultant, agency owner, or freelancer who builds client-facing reports and wants to cut production time dramatically.
- You are already using Claude and want to understand how CoWork and Design work together in a real client workflow.
- You want a clear, honest answer on when Fable 5 is worth the 2x cost premium over Opus 4.8.
- You need dashboards connected to live databases or real-time APIs — this workflow produces static HTML exports.
- You already have a mature BI stack (Tableau, Looker, Power BI) and have no need for a faster AI prototyping path.
The full version, fast.
The workflow is a deliberate two-stage handoff: Claude CoWork ingests raw CSV files and a brand style guide, structures the data into clean JSON files, and writes a design brief as a README; Claude Design then reads that brief and generates three fully interactive HTML dashboard prototypes in a single pass. The host demonstrates all three prototypes — Bold Data Studio, Dark Command Center, Summit Altitude — plus a standalone board report, all produced without any manual design work. The key insight is that CoWork handles the analytical and structural thinking so Design only has to render, eliminating the prompt iteration that usually degrades output quality.
Chat with this breakdown — free.
Sign in and you get 23 free chat messages on us — ask for the hook, quote a framework, find the exact transcript moment, generate a markdown action plan. Bring your own key when you want unlimited.
Create a free account →Where the time goes.

01 · Hook and Fable 5 benchmarks
Three dashboards in 15 minutes introduced. Fable 5 vs Opus 4.8: 80% vs 69% agentic coding, 78% vs 40% cybersecurity, 38% vs 14% spatial reasoning.

02 · Workflow overview
15 min manual work plus 15-20 min wait. Three dashboard prototypes plus a full board report. Dataset: ecommerce sales, cashflow, and expenses CSVs plus brand style guide.

03 · Claude CoWork prompt
Exact prompt shown: data exploration, analyze, and data-validation skill invocations, Big Four analyst persona, output structured for Claude Design, board accuracy requirement, ask-if-questions close.

04 · CoWork execution and output folders
CoWork produces analysis folder (cash flow, channel performance, discount analysis JSON files) and design folder (brand design tokens, README for Claude Design).

05 · Prototype selection and Design upload
Three prototypes proposed: Earthy Editorial, Dark Command Center, Bold Data Studio. Editorial rejected and swapped for Summit Altitude. Files uploaded to Claude Design with Fable 5 active.

06 · Dashboard showcase
All three prototypes demonstrated: Bold Data Studio (Profitable on paper, bleeding cash), Dark Command Center (neon/dark aesthetic), Summit Altitude (clean topographic theme). Each fully interactive with month-range filters.

07 · Board report
Separate CoWork prompt generates a board report. Same handoff pattern: CoWork writes prompt, Design renders standalone HTML report with executive summary, findings, and action steps.

08 · Cost context and Design edit tools
Fable 5 is 2x cost of Opus 4.8. Recommendation: reserve for high-stakes outputs. Design edit tools: chat tweaks, markup click-to-edit, font and color panels.

09 · Export and handoff to Claude Code
Export options include share link, PDF, PowerPoint, standalone HTML, project archive. Send to Claude Code hands off full project context to terminal for backend work.

10 · CTA and community pitch
AI Impact School community on Skool, Infinite Brain OS system, price increase June 15. Subscribe and comment CTA.
Lines worth screenshotting.
- The key to clean AI-generated dashboards is not prompting Design better — it is having CoWork write the design brief as a file so Design only needs to execute.
- Asking Claude to produce a prompt for the next tool in the chain eliminates manual re-prompting and preserves analytical context across tool boundaries.
- Three genuinely different prototype themes produce more useful options than three variations of the same aesthetic.
- The ask-if-questions close on a CoWork prompt surfaces missing context before a long-running task begins rather than after it fails.
- Fable 5 costs 2x Opus 4.8 — the practical rule is to reserve it for client deliverables and board presentations, not routine iteration.
- Attaching a brand style guide to the analysis pass rather than the design pass lets CoWork extract tokens and embed them in the brief so Design inherits them automatically.
- Claude Design's Send to Claude Code export hands off the full project context to a terminal agent, making prototype-to-production a one-click operation.
- A fictional brand dataset is a legitimate way to demo client workflows publicly without exposing real client data — the workflow is identical.
- Interactive month-range filters in a static HTML export give stakeholders exploration capability without any backend infrastructure.
- Financial narrative headlines like Profitable on paper, bleeding cash and Plug the leak. Then build. came from the AI — the host did not write them.
The two-stage handoff that makes AI dashboards work.
Splitting analysis from rendering — letting one agent build the data layer and brief, then passing that brief as a file to a design agent — is what separates clean AI output from iterative prompt mess.
- Let the analysis agent write the design brief as a file; the design tool reads and executes it without manual re-prompting, preserving the full analytical context across tool boundaries.
- Attaching a brand style guide to the analysis pass rather than the design pass means the AI extracts the tokens and embeds them in the brief automatically — Design inherits the brand without a separate instruction.
- Requesting three prototypes with genuinely different themes forces visual divergence; editorial, dark command center, and topographic produced options that were actually different, not just recolors.
- The ask-if-questions close on a long-running prompt is a deliberate technique to surface missing context before the agent begins, not a politeness habit.
- Reserve Fable 5 for high-stakes deliverables — client presentations, board reports — and use a lighter model for iteration and routine tasks to stay cost-efficient.
- Claude Design's Send to Claude Code export is the bridge from prototype to production: it hands off the full project context so a Code agent can continue backend work without re-explaining the design.
Terms worth knowing.
- Claude CoWork
- A Claude interface mode that can read and write directly to local folders, enabling agentic workflows that produce and consume files rather than just chat responses.
- Claude Design
- A Claude interface mode for generating visual artifacts — dashboards, web pages, presentations — with live preview and iterative editing via chat or markup tools.
- Fable 5 (Claude Fable 5)
- A Mythos-class Claude model one tier above the Opus series, with substantially higher scores on agentic coding, frontier code, spatial reasoning, and cybersecurity benchmarks.
- Brand design tokens
- A structured file (usually JSON) that encodes a brand's color palette, typography, spacing, and other visual rules in a format that design tools and AI models can consume programmatically.
- Agentic coding benchmark
- A standardized test measuring how well a model can complete multi-step software tasks autonomously, including tool use, file manipulation, and error recovery.
Things they pointed at.
Lines you could clip.
“This is one of the three dashboards that I just made in about fifteen minutes using Claude's brand new Fable five.”
“Profitable on paper, bleeding cash.”
“Plug the leak. Then build.”
“It's two x the cost of Opus 4.8. I would probably keep Fable five usage to the minimum, only for hard or very important tasks.”
Word for word.
Don't just watch it. Burn it in.
See every word as it's spoken — crank it to 2× and still catch all of it. The same dual-channel trick behind Amazon's Kindle + Audible.
The bait, then the rug-pull.
Three production-ready financial dashboards, built in fifteen minutes, from raw CSV files — no designer, no developer, no BI specialist. That is the opening claim, and the next twelve minutes walk through every step of exactly how it was done.
Named ideas worth stealing.
Two-Stage AI Handoff (CoWork to Design)
- Stage 1: CoWork as analyst
- Stage 2: Design as renderer
CoWork ingests raw data plus brand guide, produces structured JSON and a README design brief. Design reads the brief and renders interactive HTML prototypes. The design prompt lives as a file — no manual re-prompting.
CoWork Prompt Anatomy
- Folder context (what files are in scope)
- Skill invocations (data-exploration, analyze, data-validation)
- Analyst persona (Big Four, 10 years experience)
- Output spec (structured for the next tool)
- Accuracy requirement (board-ready)
- Ask-if-questions close
The six components that make a CoWork data analysis prompt complete and reduce mid-task interruptions.
How they asked for the click.
“We do have a full AI Impact School community with full Claude courses. We give away starter repos. We are increasing the price on June 15.”
Soft community pitch after a clean tutorial. Urgency via price increase date. No hard sell during the tutorial content itself.






































































