Design Engineering
Current Answer
No editorial synthesis yet — the evidence below is collected automatically from source labels. A current answer lands here once an editor approves one.
Evidence
Generative UI needs more than a component catalog: agents require explicit layout rules, schemas, and design-system constraints to produce stable interfaces across repeated requests.
Vercel found that prose alone produced inconsistent agent-made pages, then paired design.md with fixed CSS primitives and repeatable evals to encode brand judgment.
As coding agents make implementation easier to copy, builders should spend more judgment on problem choice and preserve claims, evidence, and limits as AI remixes work across product and GTM.
Treat an agent’s first UI as a draft: encode recurring design dislikes, supply visual references, split work into focused prompts, and reserve time for iteration.
For subjective agent output, replace vague requests for quality with decomposed brand constraints, then reserve human preference data for style and creativity that resist deterministic checks.
A set of portable SKILL.md files that push coding agents past generic frontend output: it infers a design language from the brief and tunes variance, motion, and density dials. 850 stars in a day.
Diagram Design gives coding agents a reusable system for branded, accessible HTML and SVG diagrams, including draw.io and Mermaid redraw workflows.
This repository treats visual direction as agent-readable project context: drop in a DESIGN.md containing tokens, component rules, and guardrails to reduce inconsistent generated UI.
Hallmark turns interface taste into an installable coding-agent skill: it selects page structures and themes, critiques output, and checks common generated-UI patterns before emitting code.