Two lenses, one pipeline: why UX and visual review are different jobs
A single rubric kept producing the same shape of answer regardless of what the agent was actually getting wrong. Splitting it in two fixed that.
When we started TheDesignAgent, we tried to build a single rubric. One score, one set of patches. It kept producing the same shape of answer regardless of what the agent was actually getting wrong. A layout-fights-workflow problem looked the same as a contrast-too-low problem. Both got "mid-fit score" and a vague set of suggestions.
The fix was to split the rubric in two. Not as a feature or a tier — as an admission that UX and visual review are answering different questions and shouldn't be averaged.
The two questions
/ux answers: does this serve the person doing their job? Its concerns are information architecture, the shape of the workflow, what the user already knows, what they need to do next. Its evidence is JTBD, cognitive load, and the affordances on screen.
/visual answers: is this design well-crafted? Its concerns are spacing, hierarchy, type, color, restraint. Its evidence is layout grids, contrast ratios, density, and the integrity of the component grammar.
Why the split: a screen can be visually beautiful and still wrong for the job. A screen can be on-spec for the job and still ugly. Averaging hides which problem you have.
Different rubrics, same envelope
Both lenses return the same response shape: a fit score, prioritized patches, and flags. That consistency matters because the agent is the one calling, applying, and looping. It expects a contract. We just have two rubrics behind the same contract.
The UX rubric scores four dimensions: jtbd_alignment, intrinsic_load, extraneous_load, germane_load. The visual rubric scores seven: critical_path, density_fit, hierarchy, contrast, typography, spacing, component_grammar. The dimensions aren't leaked to the agent — only the score and patches. The dimensions are how we ground the score, not how we communicate it.
What this means in practice
For a build that's shaped wrong for the workflow but visually competent, /ux flags it; /visual doesn't. For a build that uses the right pattern but flattens it into shadcn defaults, /visual flags it; /ux doesn't. Most builds run both, and the patches stack: the agent rebuilds the shape first, then the craft.
This is why the homepage's receipts section includes three different cases — warehouse, onboarding, inventory. Each one is primarily a UX failure or a visual failure, not both. Splitting the lenses makes that legible to the agent and to you.
What we're still figuring out
The hardest part isn't the rubrics. It's the project memory that grounds them. A persona's cognitive profile, the active job, the day-shape — these have to be inferred and updated, and they're what makes the score specific to this product instead of generic. We'll write more about that in a future note.