Generation is the easy half. The graded render is the product.
status built · MCP serverrole designed + built end to end
interactive · click and scroll itlive
A brief, the generated page, and the automated desktop and mobile checks that graded it pass or fail.
What it solves
A model grading its own text output ships pages that look fine in chat and break at 375 pixels. Here the grade comes from rendered checks that run separately from the author model, and the rules live in a file with version history instead of a paragraph in a prompt.
Who it serves
Anyone producing landing pages against a brand system who wants the quality bar automated.
Who it is for
Teams that treat 'looks good in chat' as unproven.
How it works
Brief inThe request arrives with the brand rules it has to satisfy.
Claude drafts to a versioned rules fileThe rules are a file with history, not a paragraph in a prompt.
Render and check, both viewportsThe page is rendered at desktop and mobile and checked against the rules automatically.
The checks decidePass or fail comes from the checks, not the author. Exposed as an MCP server so any client can call it.
Built with
Claude (Sonnet)MCP serverversioned rules filedesktop + mobile checks