How to get better UI designs from Claude Code
Updated 2026-11-16
chort is a design canvas for coding agents: Claude Code, Codex and any MCP agent draw on it in real HTML and CSS, and you direct. Its check_design tool reports problems such as overflow and low contrast as text, so the agent needs fewer screenshots.
You end with Claude Code drawing boards that you can comment on and undo. The maker of chort wrote this page.
Before you start
You need Claude Code on a paid Claude plan (Pro, Max, Team, Enterprise or Console) and chort, a macOS app for Apple silicon (arm64). Google Chrome must be installed; screenshots and export run in headless Chrome. chort costs $0, with no account and no call limits. The chort details here are for version 0.1 as of 16 November 2026.
Make Claude Code design on a chort canvas
chort gives the agent a board to draw on and tools to fix what it drew. Files live in a folder on your own disk, with no server and no sync, and Git works on them as the history.
- Connect Claude Code to chort as an MCP client. The agent gets chort's tools, and the full list costs about 6k tokens of its context.
- Ask Claude Code for one screen. It writes the board with write_html, using HTML it already knows, and you see real HTML and CSS laid out by the browser on the canvas.
- Have the agent run check_design on the board. The tool reports problems such as overflow, low contrast, misalignment and tiny text as text, so the agent needs fewer screenshots.
- Comment on whatever still looks generic, directly on the canvas. Agents read the comment threads and mark them resolved.
- Undo what you dislike. Every agent write is all-or-nothing, and an agent's whole turn undoes in one step. The agent can also call list_checkpoints and restore_checkpoint.
- Move repeated styling into tokens and components. Tokens are CSS custom properties in the Tailwind v4 theme namespaces, so changing one token changes every use. With create_component and create_instance, every instance follows its main component.
- Ask for get_jsx once the board is right. It returns JSX with inline styles or Tailwind classes. Export covers PNG, JPG, WebP, SVG and PDF, plus a combined PDF and a handoff export.
The tool set was cut from 75,953 agent calls in its maker's own design sessions with similar MCP tools.
Other ways to make Claude Code's UI less generic
Without guidance, Claude tends toward generic, conservative designs. The Claude Cookbook offers a prompt to append to your system prompt or CLAUDE.md. It tells Claude to avoid fonts such as Arial and Inter and purple gradients on white, and to use CSS variables.
Give each request the screen and state, the real text, the components to reuse and what must not change. An @ reference such as @src/components/Button.tsx puts a file in the conversation. Name the empty, loading and error states too, since most defects in generated screens live in states nobody asked for.
Keep rules in a CLAUDE.md, which loads at the start of every session. Short rules you can verify work, such as "use the Button component". A DESIGN.md can go further: "cards use 16px padding, 8px radius, no shadow, and a 1px neutral-200 border" is a rule, and "cards should feel clean" is not.
When words fall short, drag an image into the window or give its path, then say what to take from it, such as the layout only. The frontend-design plugin targets generic-looking UI, though it is one example and not a quality guarantee.
To close the loop, build one screen with all its states per pass. Screenshot each state at 390 px and 1440 px, and cap automated revisions at three rounds before you review the remaining differences yourself.
Other tools that give the agent a design surface
Rival features and prices below are as stated in pages dated 24 September 2026 to 16 November 2026, with prices as each vendor listed them in October 2026.
| Product | Where it runs | Price |
|---|---|---|
| chort | macOS app for Apple silicon, with Google Chrome installed | $0, no account, no call limits |
| Claude Code /design | CLI and Claude Code Desktop, Claude Code 2.1.265 or later | Included in Pro ($20/mo) and up |
| Claude Design | claude.ai | Every plan per one source; Pro and up, sharing Claude usage limits, per another |
| Figma with Figma MCP | Figma, reached through the Figma MCP server | MCP: 20 calls/month on Starter or View/Collab; 200-600/day on paid Dev/Full |
| Mowgli | Web canvas | Free to start (300 credits); credit packs from $12; plans from $15/mo |
Which to pick
Start with chort when you want the agent to draw on a canvas where check_design reports problems as text and the agent reads your comments. Pick a rival when the job matches:
- Claude Code /design is best for one feature or screen.
- Claude Design is best for on-brand prototypes and decks.
- Figma with Figma MCP is best for teams with designers.
- Mowgli is best for a whole product kept in sync with code.