design
The tool for screen-level design verdicts, the corpus behind it, and what it returns while no design verdict is published.
design is recommend pointed at a different slice of the corpus: it searches verdicts of kind design, so it answers "what should this screen be built from" rather than "which library solves this problem". Call it before writing UI, when the choice of system and tokens is still cheap to change.
Arguments
| Name | Type | Limits | Required | Default |
|---|---|---|---|---|
screen | string | 1 to 200 characters | yes | none |
constraints | array of strings | up to 8 items, each 1 to 60 characters | no | none |
screen and every constraint are joined into one full-text query against design verdicts, with a fallback to context-tag overlap. Constraints are where the framework, the direction, and the platform go: "React", "RTL", "dark and light", "mobile first".
Request
{
"name": "design",
"arguments": {
"screen": "settings page for a developer tool",
"constraints": ["React", "dark and light", "keyboard first"]
}
}Response
A design verdict renders as the same compact block recommend returns, with the design system in the PICK line and the anti-patterns in AVOID.
No design verdict is published today, so every call currently answers with the miss:
no verified design verdict yet for "settings page for a developer tool React dark and light keyboard first". Browse https://wellworn.dev/verdicts or request one at https://wellworn.dev/request
remaining: 50The quoted text is your screen and constraints joined with spaces, which is a useful way to see what the search actually looked for.
The design systems behind it
wellworn.dev/design serves the curated design-system rows the verdicts will be written against: licence, frameworks, styling approach, whether tokens are exposed, and what first-party agent tooling each one publishes. That list is readable now and needs no MCP call. Design systems covers where the rows come from and how a system is described.
Limit and error lines
| Line | Cause |
|---|---|
no verified design verdict yet for "…" | No design verdict matched. Normal result, not an error, and it costs a call. |
MCP error -32602: Input validation error: … | screen missing, empty, over 200 characters, or more than 8 constraints. |
limit reached: … | The window is spent. Limits. |
What to do with the answer
Until design verdicts are published, spend the call on recommend instead and read the design list on the site. When one does come back, treat the AVOID line as the important half: screen-level design verdicts are mostly a record of what looked reasonable and did not survive contact with a real user.