Design dashboards in Claude Design then hand exact CSS to a low-code agent

An automation developer designs internal dashboards in Claude Design and has it write exact-CSS prompts for UI Bakery's agent, estimating 40 to 60% fewer UI Bakery tokens on new pages.

Done withClaudeinPostgresql· Nov 13, 2026

What they did

Kandeepan Yathuraj builds an internal order, renewal and reporting app at a managed service provider in UI Bakery, a low-code tool whose built-in agent writes React pages and SQL actions on top of PostgreSQL, and is moving reports over from Power BI. Asking UI Bakery's agent for a dashboard meant it read through the project, guessed a look, and then took several paid correction rounds. Now Yathuraj gives Claude Design the existing page code, styles, SQL actions and screenshots, pastes the stakeholder requirement, and iterates on Claude's clickable HTML preview. When the preview is right, Yathuraj asks Claude to write the UI Bakery prompt: a scope line, the file to edit and exact CSS values for every element.

How it went

Yathuraj estimates 40 to 60% fewer UI Bakery tokens on new pages and components and about no saving on small edits; UI Bakery does not show usage per dashboard, so this is judged by fewer rounds. The cards came out more consistent, with status pills and explanation lines. Builds were not always faithful: once tooltips ended up under the cards and once the cards drifted from the design, each needing a small fix prompt. Claude once added a business rule that was not in the requirement.

Worth knowing

The cost moves rather than disappears: Claude Design usage is paid too, which paid off only because UI Bakery tokens were the tighter budget. Yathuraj now tells Claude up front to make no assumptions beyond the requirement. Exact CSS helps with looks but not with big data or performance changes.

Try it

With Claude· 5 parts to fill in

Here is the code of my existing [app name] pages, their styles, data queries and screenshots of the live pages. Design a new [dashboard or component] for this requirement: [paste requirement]. Match the existing colours, fonts and layout, and make no assumptions beyond what the requirement says. Build it as a clickable preview and wait for my feedback. When I say the preview is approved, write a build prompt for [UI Bakery or my low-code tool's agent] that starts with a scope line limiting changes to [page], names the exact file to edit, and lists every element with its exact CSS values, so the agent has no design decisions left to make.

Square brackets are the parts to fill in. The prompt is ours; the story is theirs.

Where they said it

Related