Make Claude and Cursor build in your taste.

Turn any Figma frame or website into a design.md — then build in that taste. Tastefile keeps Claude and Cursor on-brand from the first prompt.

Tastefile

Paste a Figma frame's CSS or a website URL, and I'll reply with a design.md your coding agent can follow.

One free generation — no signup. Sign in to save tastes to a reusable library.

Why Tastefile

A source of truth, not a guess

Everything in a design.md comes from your real design — so the AI builds in your taste from the first prompt.

design.md
Tokens
Search tokens…⌘K
◨▦Colors
Read from your frame
Colors, type, spacing & radius — real values, pulled locally.
Tokens[6]
Primary#00A7F5
Surface#F4F4F5
AaRadius12px
AaFontInter

Real values, not guesses

Every color, type size, spacing step, radius, and shadow is read from your actual frame — locally, before any AI.

Tastefile· design.md loaded
Design a settings page for my app.
On it — staying inside your design.md rules:
No invented colors
No random gradients
No emoji as icons
Keep the spacing scale
Message Tastefile…

Anti-slop rules built in

design.md tells the model what not to do — no invented colors, random gradients, or generic template cards.

escApply design.md to a screen…
Recently applied
ClaudeSettings page
On brand
CursorDashboard
OpenAIAuth flow

Reusable across your app

One taste spans dashboards, settings, and tables. Add more frames and it grows with your product.

How it works

From a frame to finished screens

Four steps from a design you admire to new screens that match it. Everything up to design.md runs locally on your machine — real values pulled from the source, no guessing, no template slop.

Find

Pick a Figma frame — or any design you admire — with real UI to learn from.

Copy

Copy the frame's CSS. Tastefile reads the real values, locally, before any AI.

Generate

Compile a clean design.md — colors, type, spacing, and anti-slop rules.

Build

Hand it to Claude or Cursor and ship new screens in the same taste.

Find

Find a frame whose taste you like

  • ✓Dashboards, settings pages, and table views carry the most signal.
  • ✓Look for real nav, cards, buttons, inputs, badges, and icons.
  • ✓One detailed screen is worth more than ten sparse ones.
Copy

Copy the CSS from the frame

  • ✓Colors, typography scale, spacing rhythm, radius, shadows, borders.
  • ✓Repeated component patterns — buttons, cards, inputs, nav items.
  • ✓Parsed locally in your browser before any AI is involved.
Generate

Generate your design.md

  • ✓One portable file — no plugin lock-in, reusable in any AI session.
  • ✓Includes the rules AI usually misses, so it stays on-brand.
  • ✓Copy, download, or save it to your library.
Generate yours
Build

Build new screens in the same taste

  • ✓New dashboards, settings, auth flows, and tables — on-brand from the first try.
  • ✓The screenshot anchors layout; the tokens anchor the visual language.
  • ✓Start with a real identity on day one, then grow into it.
The problem

Why this exists

Most people starting something new don't have the budget for a designer yet. So they ask AI to build the UI — and it guesses colors, invents spacing, adds random gradients, and makes every product feel like the same SaaS template.

Tastefile gives the model a source of truth before it starts building, so you can begin with a real visual identity from day one — and grow into it as you scale, instead of starting generic and fixing it later.

More than CSS variables

A good design.md captures the parts AI usually misses, so when you ask for a new dashboard, settings page, auth flow, or table view, the model has rules to follow.

ColorsTypographySpacing rhythmRadius systemShadow styleComponent patternsLayout rulesInteraction feelAnti-slop rulesAI builder instructions
Guardrails

Anti-slop rules, built in

Every design.md ships with rules that keep the AI from drifting into generic template land.

✕Do not add random gradients.
✕Do not invent new colors.
✕Do not use emoji as icons.
✕Do not use oversized generic SaaS cards.
✕Do not use glassmorphism unless it exists in the source.
✕Do not use monospace labels unless the design uses them.
✕Do not change the spacing rhythm.
✕Do not make the UI feel like a template.
Loved by builders

Made for people who ship

First time AI-built screens actually looked like my design instead of a bootstrap template. Pasted a frame, got a design.md, done.

🧑🏻‍💻Maya Chen@mayabuilds

Handed the design.md to Cursor and it just… stayed on-brand for a whole feature. First time I didn't have to babysit every color.

🧑🏽‍🚀Dev Patel@devships

The anti-slop rules alone save me an hour a day fixing random gradients and off-brand colors. This should be built into every agent.

👩🏼‍🎨Sofia Ramos@sofiadraws

Finally a source of truth I can give the model on day one. No more 'guess my spacing scale and get it wrong.'

🧑🏾‍💻Marcus Lee@marcuscodes

Website import is scary good. Pointed it at our marketing site and it read the whole system — type, spacing, radius — in seconds.

🧑🏻‍🔧Priya Nair@priyamakes

One taste now spans our dashboard, settings, and tables. Every new screen just matches. Our design debt basically stopped growing.

👩🏾‍💼Elena Volkov@elenaships

Shipped a settings page with Claude that matched our app on the first try. My reviewer thought I'd hand-built it.

🧑🏼‍🎤Tom Becker@tombuilds

This is the missing piece between Figma and my coding agent. It's the layer I kept wishing existed.

🧑🏿‍💻Aisha Khan@aishacodes

No more invented colors or mystery gradients in PRs. The output reads like a senior dev already set up the design system.

🧑🏻‍🚀Ryan O'Neil@ryanbuilds
Pricing

Start free. Go Pro when you're ready.

Free while Tastefile is in beta. No card required.

Free

In beta

Full access while Tastefile is in beta.

$0/month

No card required. Ever, during beta.

Start free
  • 5 AI generations a day
  • Figma CSS + website sources
  • Parsed locally in your browser
  • Rendered design.md inspector
  • Save tastes to your library

Pro

Coming soon

More power for when you outgrow the free limits.

Soon

Pricing announced at launch.

Coming soon
  • Everything in Free
  • Higher daily generation limits
  • Priority AI interpretation
  • Bigger libraries & organization
  • More import sources

Compare features

What you get in each plan.

Free
Pro soon
AI generations5 a dayHigher daily limits
Import sourcesFigma CSS + websiteMore sources
Local CSS parsingIncludedIncluded
Rendered design.md inspectorIncludedIncluded
Taste librarySave tastesBigger & organized
AI interpretationStandardPriority
SupportPriority support
PriceFreeAnnounced at launch
Best forTrying it outTeams & heavy users
FAQ

Questions & answers

What does Tastefile actually do?

It reads the real values from a design you like — colors, type, spacing, radius, shadows — and compiles them into a design.md your coding agent follows, so new screens come out on-brand from the first prompt.

Do I need Figma?

No. Paste any Figma frame's CSS, or point Tastefile at a website URL and it reads the whole system straight from the source.

Is it free?

Yes — Tastefile is free while it's in beta: a few generations a day, no card required. Pro pricing will be announced at launch.

Is my data private?

Your CSS is parsed locally in your browser before any AI is involved. Nothing is stored unless you choose to save a taste to your library.

Which AI tools does it work with?

design.md is a portable markdown file — drop it into Claude, Cursor, or any coding agent that reads text. No plugin or lock-in.

Can I reuse one taste across my whole app?

That's the point. One design.md spans dashboards, settings, tables, and more — add frames and it grows with your product.