01How to Use Claude to Build Dashboard Screens: The Basics

Learning how to use claude to build dashboard screens comes down to one thing: you drop your data file in a folder and send Claude Fable 5.2 one clear message. In this episode, Julian Goldie built three 3D dashboards inside his Agent OS this way, each from a single message.

Anthropic makes a few families of Claude models. Fable is the top family, and 5.2 is the newest version. It is live inside Claude and Claude Code right now.

The Agent OS is Julian's dashboard that sits on top of his AI tools. It is one place where his AI agents live, including Claude, Claude Code and Codex, with shared memory and one screen to control them.

So when Julian says he asked Fable to build a dashboard, he means this:

  • He opened Claude and picked Fable 5.2.
  • He gave it one job: build a new screen for his business.
  • He told it to use his real data.
  • He told it to make it beautiful.

Why bother? Most business dashboards are a grid of small gray numbers. People open them, then close them again.

A dashboard only helps if you actually want to open it.

02What Is New in Claude Fable 5.2

Julian covers a few reasons Fable 5.2 suits this kind of build. These are the points he shares in the episode:

  • Speed: Anthropic says it runs up to 30% faster than the version before it.
  • Fast mode: a new fast mode can make it up to two and a half times quicker on top of that.
  • Team work: it can run a team of smaller models, handing them the easy jobs while it keeps the hard thinking for itself.
  • Where it runs: it is live inside Claude and Claude Code.

For dashboards, these points matter because each build has a lot of parts. There is a 3D scene, panels, charts that draw themselves in, counters and a camera tour. A model that runs faster and handles bigger jobs gets you to a finished screen sooner.

Fable 5.2 also reads spreadsheets and exported files well. That helps, because most business data lives in a spreadsheet or a file you export from your store or reporting tool.

03Dashboard One: The Agency Command Center

The first build is for agency owners. Every website Julian runs is a glowing tower in a night city, and the taller the tower, the more people found that site on Google. In one glance, before reading a single number, you know which clients are winning and which need help today.

Here is what is on the screen:

  • A line chart of every site's daily clicks that draws itself in.
  • Each site's clicks, impressions and growth for the month.
  • A six month bar chart that grows in, so you see the trend.
  • A gold crown floating above the fastest growing site's tower.

At the bottom is a line called agent next move. This is where it gets useful:

  • If a site is growing fast, it says double down and publish more pages on the topic that is winning.
  • If a site is dropping, it says refresh the top pages and fix the titles.
  • If a site is flat, it says build internal links into the best page.

Julian says this gets your Monday meeting done in about 10 seconds. Because it is a page in a browser, you can share it with your team, put it on an office screen, or show a client their own tower growing.

04Dashboard Two: The E-Commerce Mission Control

The second build is for an online store. Julian didn't want to show private store data, so he asked Fable to make up a sample store and label it clearly. It is an outdoor gear brand called Northline Outfitters, with jackets, packs, boots, bottles and tents, 24 products in total.

The words sample store data stay at the top of the screen.

  • 3D globe: every new order is a glowing arc flying from the customer's city into a warehouse beacon. It lands with a burst of light and the order counter ticks up.
  • Product shelf: each product is a floating glass pedestal, and its height is units sold this week. Low stock items blink amber and get a restock tag.
  • Today panel: big numbers for orders today, conversion rate and returns rate, plus a donut chart of where orders came from: search, social, email or ads.
  • Agent ticker: what the store's AI agents are doing, such as a restock alert for the trail pack because only 12 are left.

To use it for your own store, export your orders and products, hand Fable that file instead of the sample data, and send the same message.

05Dashboard Three: Agent Crew HQ

The third build is for anyone using AI agents. Agents work in the background, sometimes all night, and you only see the result. So Julian gave Fable the real log of every job his agents finished over the last 10 days.

In the middle is a glowing reactor core labeled Agent OS. Around it, each agent is its own station, glowing in its own color:

  • Claude Code is orange.
  • Codex is a white blue.
  • Grok is silver and violet.

The bigger the station, the more jobs that agent finished. Every finished job flies out of its station as a small glowing card.

On the left, a panel called the crew counts jobs finished in 10 days, how many agents are active and which day was busiest. A bar chart of jobs per day grows in. When the camera dives into a station, the right panel shows that agent's name, how many jobs it did and its real jobs typing in one by one.

So if you want to know what Codex did yesterday, you don't scroll through logs. You just look. And if one agent goes quiet for a whole day, its station stops sending cards, so you catch a stuck job before you lose a morning to it.

06How to Use Claude to Build Dashboard Pages: The 5-Part Message

This is the part you can copy. Julian opened Claude Code, switched the model to Fable 5.2, put the data file in a folder and sent one message with five parts.

  1. The job. Say who the dashboard is for and what they need to see. For the agency one, it was the one screen an agency owner opens in the morning to see every client site at once.
  2. The data and the rule. Say which file holds the real numbers, and say use only these numbers, never invent any. If there is no real data, tell it to make sample data and label it on the screen.
  3. The world. Describe the 3D scene in plain words, like a scene from a film. Every website is a glowing tower, every order is an arc, every agent is a station orbiting a core.
  4. The panels and camera. Say which panels go left and right, which numbers count up, and what the camera does.
  5. The self-check line. Tell it: when you're done, open the page, take screenshots, look at every one, fix anything ugly, empty or broken, and repeat until it is genuinely stunning.

You don't need to know anything about 3D. You just describe what you would love to see.

07The One Line Most People Leave Out

Julian says part five does more work than the rest put together, and most people leave it out. It is the line that makes Fable check its own work.

Without it, you get the first draft, and the first draft of anything is rarely the best. With it, Fable opens the page itself, looks at what it built, spots the gap and fixes it.

The other key line is the data rule in part two. It keeps the numbers honest:

  • Tell it to use only the numbers in your file and never invent any.
  • The first time you build, check one or two big numbers against your original file.
  • On the agency dashboard, every count on screen matched the real data.
  • When there is no real data, make the screen say sample data so nobody is confused.

Together, these two lines solve the two biggest worries with AI dashboards. One stops made-up numbers. The other stops a rough first draft from being the final result.

08Old Way vs New Way, and Common Doubts

The old way to build a dashboard was slow. You exported numbers into a spreadsheet, built one chart, then another, then tried to make them look less ugly. You pasted screenshots into a slide.

For anything custom, you hired a developer and waited weeks. Next month, you did it all again.

The new way is to drop your file in a folder and send Fable one message. It builds a custom 3D dashboard around your business, checks its own work and fixes it. Inside the Agent OS, agents can refresh the data so it is current when you open it.

Julian answers three common doubts:

  • I'm not technical. The whole message is in normal words. You describe a scene and the numbers you care about, not code.
  • My data is messy. Fable reads spreadsheets and exported files well. Tell it what each column means if the names are unclear, and start with one file, like your orders or your Search Console clicks.
  • Will it make numbers up? That is why the data rule exists. Use it, then check a couple of numbers yourself.

09Steps to Build Your First Dashboard This Week

Julian lays out a simple plan for this week. The goal is one dashboard at a time, not everything at once.

  1. Pick one thing you check every week: your website clicks, your orders, your leads or what your agents did. Just one.
  2. Export it as a file and put it in a new folder.
  3. Open Claude Code, switch the model to Fable 5.2 and send the message: build a dashboard for my business from the file in this folder, use only the numbers in the file, never invent any, and make it a 3D world where you describe your scene. End with the self-check line: open the page, take screenshots, look at every one, fix anything ugly, empty or broken, and repeat until it is genuinely stunning.
  4. Open it every morning for a week and notice what you spot that you used to miss.

This is useful for agency owners, online store owners and anyone running AI agents. Julian notes the Fable 5.2 dashboard system from this episode, with the exact message behind each build, is inside the AI Profit Boardroom.