Roast — The Taste Layer for AI Agents. Design review, critique, and evaluation for coding agents.

DESIGN
D.O.C.S — MCP

A native design collaborator for your coding agent. Roast holds the brief, tracks progress across iterations, adapts how it delivers critique, and closes the session when the design meets the goal. Not a request-response tool. A partner.

Crafted by a design veteran, because a taste layer must be built on real human design intuition to teach AI agents how to build beautifully.

One endpoint.
three response modes.

Agents get terse, actionable diffs. Designers get scores and narrative. Both run against the same eval engine.

[Mode “Diff”] Actionable Diff

Fixes, not feedback.

Element-level fixes with exact replacements your agent can apply immediately. No prompt engineering, no guesswork.

[Mode “Score”] Score summary

A grade, not a vibe.

One score across the dimensions that matter — typography, color, spacing, hierarchy. Know exactly where your design stands, and why.

[Mode “Profile”] Design Profile

Identity, not inspection.

Read your design’s aesthetic, its audience, and the direction that takes it from good to unmistakable.

ROAST.A.URL
Enter any live URL to run a real-time aesthetic evaluation. Also accepts images, and Figma frames.

CORE.VISION.

At Roast, design is not decoration — it’s the difference between something that works and something that’s loved. We think of Roast as the design conscience of AI coding agents: a collaborator that holds the brief, tracks progress across every iteration, and only signs off when the design earns it.

INDEXED.AGAINST.
PERFECTION.

50,000+ validated UI patterns from the world’s most precise interfaces. Every pixel a reference point.

REAL.CREATIVE
EXPERTISE.

Built by practicing creative professionals with real market experience. Every evaluation is grounded in proven design principles, not subjective opinion.

STRUCTURED.
DESIGN.CORPUS.

Powered by a structured corpus of 50,000+ DESIGN.md files and 400k+ design assets, giving Roast the context to evaluate designs with consistency and evidence.

WHAT.GETS.
ROASTED.

Roast evaluates every design across six core dimensions: typography, color, spacing, components, layout, and composition, delivering consistent, explainable feedback.

NATIVE.TO.YOUR.AGENT.

One JSON block. Roast connects to Cursor, Claude Code, Windsurf, Opencode – any MCP client. Start a design session, iterate across versions, and close when the goal is met. Proactive mode built in.

  • roast_start_session Start a design review session. Collects the brief, captures v1, evaluates against goals, and returns critique.
  • roast_iterate Continue a session with a new iteration. Evaluates delta against history, tracks what persisted and what resolved.
  • roast_close_session Close a session. Returns final report with score progression, agent response pattern, and goal achievement.

WARNING!!!

Roast is not a
“taste” package…

I know there are lots of taste packages and I get it if you mistake
roast to be one of those. But, roast is not one.
Roast is a design agent that works alongside your dev/design agents to make sure that whatever is built/designed
is up to par. It makes sure that everything your agent ships is visually solid and clearly usable.
Your agent doesn’t need to call roast to clean up after it’s made a mess.
roast works alongside your agent
to prevent the mess from happening in the first place.
Think of it as a design lead who has and is being trained on a regular on what good design is.

Roast was built from the ground up by designers
who’ve spent the last decade creating some of
your favorite products. The same attention to
detail that shaped those experiences is what
powers Roast. Possibly better.

ROAST VS. THE
TASTE INDUSTRY.

Taste packages hand your agent rules. Taste labs sell you an API call. Roast is the only one that evaluates what you actually built, tracks it across iterations, and returns fixes your agent can act on.

Roast Taste packages Taste labs
What it is A design agent that evaluates real work Free skill & rule libraries (OPTIK, Kern, EDT) Eval APIs & taste infra (tastellm, Taste Labs)
Evaluates your actual build YES NO — opinions, not measurement Some — per-call evals
Tracks iterations to a goal YES — sessions NO NO
Runs natively in your agent YES — MCP YES — skills/rules MCP (tastellm) or REST-only
Reference-grounded verdicts YES — 50k+ corpus NO tastellm cites corpus; others don’t
Veteran designer oversight YES — a team of veteran designers reviews, trains & improves the data NO NO
Self-training system YES — built to learn from every eval NO NO
Cost 1–2 credits per eval Free $0.05/call (tastellm), $14.99/mo (Taste)

Taste packages give you rules. Taste labs give you a meter. Roast gives you a working, measured result — tracked across every iteration, inside the loop that builds it.

What exactly does Roast do?

Roast is a design evaluation agent. Point it at a live URL, an image, a Figma frame, or a design-token file, and it captures the actual interface, screenshots it, and runs it through a visual evaluation engine. You get back structured critique across six dimensions — typography, color, spacing, components, hierarchy, and anti-patterns — with severity ratings and concrete fixes. It is not a set of rules you bolt onto a prompt; it is a system that looks at what you built and tells you, and your agent, what to change.

How does it work with my coding agent?

Roast connects through MCP (Model Context Protocol), so it plugs into Cursor, Claude Code, Windsurf, or any MCP-compatible client with one JSON block. Once connected, your agent can call it on its own: roast_url, roast_image, roast_figma, and roast_tokens each run an evaluation. For bigger jobs, roast_start_session opens a review loop that captures your v1, checks it against your stated goals, and keeps scoring every iteration until the design meets them — then roast_close_session writes the final report. The agent does not need to be a designer; it just needs to read a structured result and apply it.

What does it evaluate — and what does it not?

It evaluates anything visual it can see: rendered URLs, screenshots, Figma frames, and token files. The engine scores typography, color and contrast, spacing and rhythm, component consistency, visual hierarchy, and common anti-patterns, then checks the result against a corpus of 50,000+ validated UI patterns so every verdict is anchored to real references. It does not write your code, and it does not enforce brand opinion — it flags what is objectively weak and returns the exact replacement so your agent can decide how to apply it. Context matters: pass a short context string (e.g. "fintech dashboard") and the evaluation calibrates to the right expectations for that kind of product.

What do the three modes mean?

One endpoint, three shapes of output. Mode "Diff" returns element-level fixes with exact replacements — the fastest thing to hand an agent. Mode "Score" returns a numeric breakdown across dimensions so you can see where the design stands and what is dragging it down. Mode "Profile" returns a full read of the design's aesthetic and identity and where it should go next. Same evaluation engine underneath; you pick how much detail you need. If you are not sure, start with diff — it is the default and the most actionable.

How does it know what "good" looks like?

It is trained on a structured corpus of 50,000+ design references from some of the most precise interfaces in production. Every evaluation returns the closest corpus match as a reference point, so a verdict is never just an opinion — it is an evidence-backed comparison against real design work. That is the difference between a taste prompt that regurgitates rules and a system that measures your actual output against a reference set.

How much does it cost?

Evaluations run on a simple credit model: 1 credit per roast_url, roast_image, roast_figma, or roast_tokens call, and 2 credits to open or iterate a session. Searching the design corpus and getting brand guidelines are free. Credits are tracked against your API key and you can top up from the dashboard at designroast.cc/billing. Compared to a human design review that takes days, a full evaluation costs pennies and returns in seconds.

Is my code or data sent to Roast?

Roast sees only what you explicitly evaluate. For a URL eval it captures a screenshot of the page; for an image or Figma eval it sees that image or frame. It does not read your repository, your prompts, or anything you have not asked it to look at. The design agent evaluates the artifact you hand it, not your codebase.

Damn you're curious... I don't blame you. Aren't we all?