design trained

A design decision starts with a task, audience, surface, and existing visual authority. Select one matching guide from the design bank. Use a generator or dataset for options, then reject suggestions that miss the product's job. Review the rendered result and its interaction states in the actual target runtime.

For an existing dashboard: inspect its route, tokens, and rendered states; use impeccable for a bounded critique; change the owning component; check keyboard, narrow width, and reduced motion where affected.

For a new design direction: query UI/UX search for candidates, compare the returned pattern, palette, and type to the brief, then write the chosen rationale into the project's owning design document.

• Preserve factual content and product behavior while refining visuals; get explicit direction before replacing an established visual world.
• Match motion to the interaction's purpose. Apple asks for purposeful motion and a reduced-motion alternative: Motion, Accessibility.
• For shadcn/ui, inspect the project's selected primitive. The current project setup offers Base UI and Radix; the official Base UI update says Base UI became the default for new projects in July 2026.
• Follow the global agent rules for Codex-only image generation and MonoLisa in HTML reports, demos, and proposals.

The bank covers direction, critique, implementation, motion, brand assets, and focused reference searches without making one guide own every design task.

Some reference material carries stale runtime paths, hard-coded font picks, and broad "always" rules. Its scripts and datasets provide candidates, not product authority. Google Stitch requires an external service and account; use it only when the task calls for it. See Google's Stitch overview and official MCP codelab.

• A syntactically valid search result can combine unrelated product patterns, palettes, and fonts.
• The old "shadcn/ui = Radix" shorthand is no longer a safe assumption for new installations; inspect the selected base.
• Suggestions for product typography do not override the MonoLisa rule for HTML reports, demos, and proposals.

No version-specific defect has been reproduced for the active design tools. Do not infer one from a reference note or a search result.

• Wrong generated direction -> compare every returned field to the task and discard mismatches before implementation.
• Dead reference link -> follow the relative links from the design guide's own location.
• Design review without a visible state -> capture the target runtime before claiming visual quality.

• Ran the bundled ui-ux-pro-max 1.1.0 search with a 'small nonprofit volunteer dashboard calm readable' brief, design-system mode, markdown output, on local Python 3.13.12. The command exited 0, but returned an operations landing pattern, a dense dashboard style, blue/orange colors, Lora/Raleway wellness typography, and a Google Fonts import. The fields conflicted with one another and with a volunteer operations brief. The useful practice is to inspect each field and reject mismatched generated direction; this did not test a rendered interface.