whata.design
Early access

The design skill, MCP and book

Be first to use them. One email when they open, nothing else.

whata.design skill · early access

The design skill for Claude Code.

A designer's process, measured sections from real sites and rules it can check, so the pages your agent builds stop looking like every other AI-built page.

The design skill, MCP and book

Be first to use them. One email when they open, nothing else.

Why AI-built pages look alike.

Asked for a website, a model reaches for the same defaults every time: the same hero, the same card grid, the same palette. Telling it to be distinctive helps a little. Giving it a real reference to work from, with numbers it can copy and rules it can check, is what changes the result.

What's inside.

  • A designer's process

    40 steps in 7 stages, from the client's need to launch, with shorter tracks for a sprint or a single day. The client's taste is asked for at two gates, never assumed.

  • Sections from real sites

    17 finished sections taken from library sites and measured: every size, colour and motion timing, and exactly what may change.

    See them
  • Rules it can check

    242 testable rules for accessibility, usability, craft, copy, components and distinctiveness, each with what to do while designing.

  • Recipes for bold styles

    30 recipes that keep a stylish look (glass, brutalist, bento, editorial…) and still pass the rules.

    See them
  • An audited base kit

    14 page parts that already work at every width and at 200% text: header with a real mobile menu, heroes, features, FAQ, forms, footer.

  • Named principles

    44 principles from Rams, Nielsen, Norman, inclusive design and Gestalt, each with how to apply it and how to check it.

How a run goes.

The default track: five steps, with the client deciding at each fork.

  1. Step 1

    Need

    What the page must achieve, for whom, and how you will know.

  2. Step 2

    References

    Real sites from the library that fit the brief, shown to the client to pick from.

  3. Step 3

    Sections

    The page assembled from measured library sections, changed only where their specs allow.

  4. Step 4

    Build

    Code from the audited kit and the project's own design tokens.

  5. Step 5

    Review

    The page checked at desktop and phone sizes against the rules, then fixed.

Better with the MCP server.

The skill is the method. The MCP server gives it the library: 36 tools to search real sites, pull measured sections and review a page in a real browser.

Explore the MCP server

Read: Anthropic's frontend-design skill, and what it leaves out

Questions.

When can I use it?

The skill is in early access. Join the list and you will get one email when it opens; nothing else is sent.

Which agents does it work with?

It is written as a Claude Code skill. The same guide is plain Markdown, so Codex, Cursor and other agents can follow it too, and the MCP server works with any client that speaks MCP.

Do I need the MCP server as well?

No. The skill carries the process, rules and recipes on its own. The MCP server adds the live library (search, measured sections, design briefs) and the reviewer that checks a page in a real browser.

How is it different from Anthropic's frontend-design skill?

frontend-design tells Claude to avoid generic choices and critique its own work. The whata.design skill adds what that leaves to the model: real references to build from, measured numbers, rules it can test and a reviewer that runs the checks.

Will it make every site look the same?

The opposite is the point. It starts from the client's own picks among real sites, and its distinctiveness rules flag the defaults AI-built pages fall into.