Give Codex a UI Add-on: Can Pages Feel Less AI-Made?

Codex can write webpages that work, but the pages often look AI-generated at a glance. Someone built it a UI/UX add-on: UI UX Pro Max.

According to the original author govin.eth, it includes 192 industry design rules, 79 UI styles, 192 color schemes, and 74 font combinations, covering 22 tech stacks such as React, Next.js, Vue, and Flutter. According to the original post, this is like giving Codex a professional UI/UX designer. Some commenters also warned that Pro may be paid.

Installation is not about typing a bunch of commands yourself. Throw this prompt to Codex:

“Read nextlevelbuilder/ui-ux-pro-max-skill, install and configure UI UX Pro Max for the current Codex environment according to the official docs, check dependencies and configuration, and after finishing, verify whether the Skill can be called normally.”

After installation, the original post gave a prompt for testing:

“Use UI UX Pro Max to build a high-end AI SaaS website for me, including a hero section, feature cards, and a pricing area; automatically plan the design system; implement it with React + Tailwind CSS; and start a preview when done.”

The second half of the video shows actual results.

The comments are not one-sided. User siyuan liu warned that if you turn everything on at the project level, keep only the subset of styles and palettes that this repo will use, for example one set of layout rules and one color palette. Otherwise the Agent will waver between rules, making diffs harder to review. His approach is to lock down brand tokens first, then let it change components; don't use the whole design encyclopedia as the default system prompt.

User Feng Yi's approach is to distill design guidelines into SKILL.md, and each time have Codex read the guidelines before writing. That way the AI flavor fades a lot. His view is that rules should be precise rather than numerous.

Some people tried it and felt the results were still the same—not that useful.

My take: the value of this kind of Skill is mainly to front-load some reusable aesthetic constraints. It solves the problem of Codex lacking design constraints when writing frontend from scratch, and is suitable for quickly building prototypes, filling in pages, and unifying basic visuals. Before actually shipping, humans still need to review. User Cyber Hermit said that the delivery threshold has changed from knowing how to draw to knowing how to review; that's an interesting way to put it. If you want to try it, start with one page or one component, and don't stuff all 192 rules into the system prompt.