Interface Quality
Current Answer
Taste references that map to concrete product decisions — motion timing, density, editorial rhythm.
Implementation Consequence
Taste references only belong in feed7 when they produce a design decision an agent can apply. Otherwise they are moodboard material.
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.
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.
MCP Apps let servers return sandboxed, interactive UI instead of text alone while the host retains control of prompts and tool calls—a useful pattern for agent workflows needing charts or controls.
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.
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.
Agent-Ready Context
Motion: 150ms state changes, 200ms popovers, no bounce. Density: 24px card padding, hairline borders over shadow, one accent per view.
Graph is progressive enhancement. Every edge listed below.