UI/UX Quality

This skill turns Codex from a free-form UI generator into a frontend design-and-development agent. It must understand the project first, recommend suitable choices, and create enforceable project-level norms during implementation.

Core stance

Frontend quality is not a fixed style guide or a pile of rules. Good frontend work requires project cognition, task-flow judgment, product temperament, page-type judgment, human-language copy, component reuse, visual verification, and iterative polishing.

Do not constrain the agent's creative range by banning colors, gradients, density, unusual layouts, or expressive visual direction by default. Creative freedom is welcome when it fits the product. But every frontend surface has a baseline craft floor: alignment, spacing rhythm, hierarchy, semantic grouping, state clarity, and target/action proximity must be coherent before visual experimentation counts as polish.

The goal is not "avoid shadcn" or "ban gradients." The real goal is:

raw GPT output → stable component baseline → project-specific product UI → polished, unified frontend

Do not optimize only the visible screen. Optimize the user's journey: entry → decision → action → feedback → recovery → completion.

Think of this as: