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.