Not specified.
Illustrative baseline
A generic request leaves the design work ambiguous.
This is deliberately not an OMH recommendation. It shows the information a generic “make it nice” handoff usually leaves unresolved.
No hierarchy or reference contract.
No selected executor or boundary.
What is missing
A card wall cannot answer the critical design questions.
The request has enough intent to start a conversation, but not enough structure to guide a design decision, a coding handoff, or later visual evidence.
Project context
Existing tokens, components, routes, and brand constraints are unknown.
Design direction
Typography, palette, layout, and the thing that makes this surface distinct are unspecified.
Specialist lane
Quality, frontend, accessibility, and screenshot QA responsibilities are blended together.
Evidence
There is no viewport, state, capture freshness, or honest “not observed” boundary.
Completion
A polished-looking sentence can be mistaken for implementation or QA that never happened.
Next move
The executor has to infer the actual decision model from a vague adjective.