John Constable, Wivenhoe Park, Essex, 1816 · National Gallery of Art
Your agent gets a screen 80% of the way. palate does the last 20%: every state, every detail, checked against your taste.
A live demo of one run in Claude Code. You ask for the team page of Fieldnote, a CRM for studios. palate plans one build from your 38 rules, with no variants, and three Claude subagents build the page. Then the last 20%: palate snaps its spacing, radii and type, and adds the empty, loading, error and long-name states the build left out. You point at a role badge and ask for it calmer; the pin goes from working to done and the badges change. Because you have asked for calmer badges before, palate proposes a rule, scoped to team pages, and you keep it.
Every state of the team pageAll 4 added
Garvit’s taste
Team and settings pages
Rule kept· Team pages only
Keep badges calm: grey by default, colour only where it means something.
From 3 pins like it
DiscardKeepWorks inside your stack, with the components you already have.
Each film is the real feature, recorded as it ran. The paintings are public domain, hung here to frame them.
01
Its palette
Claude Monet · French, 1840–1926
Water Lilies, 1906
Oil on canvas · The Art Institute of Chicago
Exhibit 01
Point at anything on your running page and say what should change. palate sizes the request first: a one-line fix is changed where it is, in seconds, with a before and after. No loops.
02
Its palette
George Inness · American, 1825–1894
The Lackawanna Valley, c. 1856
Oil on canvas · National Gallery of Art, Washington
Exhibit 02
Your agent's screen renders and typechecks. palate opens every part of it empty, loading, failing, with long text and fifty rows; your agent builds what's missing, and palate checks each one again.
03
Its palette
Thomas Cole · American, born England, 1801–1848
The Oxbow, 1836
Oil on canvas · The Metropolitan Museum of Art, New York
Exhibit 03
For a new product, palate looks at the category's best pages live and measures them, then proposes three art directions. Your own references come first: screenshots or URLs, with what you like about each.
04
Its palette
Vincent van Gogh · Dutch, 1853–1890
Wheat Field with Cypresses, 1889
Oil on canvas · The Metropolitan Museum of Art, New York
Exhibit 04
AI screens look alike because they come from the same defaults. palate remembers every layout it made for you, and its judge drops near-duplicates before you ever see them.
05
Its palette
Claude Monet · French, 1840–1926
The Japanese Footbridge, 1899
Oil on canvas · National Gallery of Art, Washington
Exhibit 05
A designer’s review of your page, laid out on a board. Agree or disagree with each finding; palate fixes what you agree with and keeps what you don’t as a rule you can approve.
One of one, for every member
Every member gets a one-of-one proof made from their invite link: a composition and palette on the front, a foil-stamped flower on the back. Post it, and every designer who joins with your link moves you up.
Join the waitlistThree sample proofs. Yours is composed when you join.
It records what won and why, by type of screen, so the next design starts closer to what you want. Here, the founder’s own picks replay into his profile.
3 of 3
Three blind picks, one landing page. Each time the founder chose the calm centred hero with the product right under it. palate wrote that down, so his next landing page starts there.
Garvit Joshi
Taste profile · 4 rules
Landing page
Calm centred hero, the product right under it
Followed his reference, plane.so. Warmer, editorial takes won 0 of 3.
3 of 3 blind picks
Features
Dense: everything at once
The whole picture at a glance. Density of content wins; density of chrome loses.
Picked blind
Pricing
Calm, all plans visible
Nothing hidden behind a tab or a step. The opposite of features, so palate learns per screen.
Picked blind
Brand colour
Deep emerald
A premium colour instead of black.
2 of 2 blind picks
palate opens invite-only, designers first.
Works inside Claude Code, Codex, Cursor and any agent that runs MCP servers. Your references, picks and rules stay on your machine.
Design intelligence that runs inside the coding agent you already use, as an MCP server. Your agent gets you most of the way; palate does the last 20%: critique, polish, and the fixes you point at, checked against your own rules.
No. It works inside Claude Code, Codex, Cursor, Windsurf, Gemini CLI or any agent that runs MCP servers, and builds with your own components, tokens and data, in your codebase.
Only when you ask. By default it builds once, from your references and rules, then finishes the screen. It explores several directions only when you ask to, or for a kind of screen it hasn't seen you choose before.
From what you pick, what you agree or disagree with in a critique, and what you point at to fix. palate turns them into proposed rules, per type of screen; the ones you keep are checked on every build. Nothing changes your builds until you keep it.
Nowhere. Your references, picks, rules and taste profile stay on your machine in ~/.palate. Screenshots are taken locally and the picker runs on localhost.
Next.js, Vite, Astro, Nuxt, Remix and React Router, Angular, SvelteKit (through Vite) and Create React App. It starts your own dev server.
Yes. Checking and finishing screens you already have needs no invite: the guard that stops your agent calling UI work done before palate has looked at it, the copy check, screenshots of every state, and the quality gate. Building from your taste, research, options and pointing at what's wrong are invite-only.
palate is in private preview, invite-only, designers first. Join the waitlist and you'll get an invite code by email. palate checks the code when you activate it and now and then after that; everything else runs on your machine. Each designer who joins with your link moves you up the list.
This page was designed with palate, from the founder’s blind picks, a critique he agreed with, and the rules palate learned from them.
