Using ui-ux-pro-max with your own design skill: who decides what
ui-ux-pro-max is very good at usability and very broad on style. Run it next to a design skill and you get both, if you decide in advance which one owns the look.
ui-ux-pro-max is one of the most installed Claude Code skills, and for good reason: it knows a great deal about what makes an interface usable, from contrast ratios to touch targets to what a loading state should do. It also carries a broad catalogue of styles, palettes and font pairings. The first half is exactly what a design skill lacks. The second half is where the two collide.
Install it from its own repository
It is an open-source project by nextlevelbuilder, published on GitHub as nextlevelbuilder/ui-ux-pro-max-skill under the MIT licence. In Claude Code:
/plugin marketplace add nextlevelbuilder/ui-ux-pro-max-skill
/plugin install ui-ux-pro-max@ui-ux-pro-max-skillIt is not ours and it is not bundled in anything we sell. Our design skills tell you how to install it and how to run it alongside them, because the pairing is worth having.
The split that keeps both useful
| Question | Who answers it |
|---|---|
| Palette, fonts, radius, shadows, motion character | The design skill |
| Which components exist and how they look | The design skill |
| Contrast, focus rings, tab order | ui-ux-pro-max |
| Touch targets and layout at 375px | ui-ux-pro-max, inside the tokens |
| Loading, empty and error states | ui-ux-pro-max, in the design skill's look |
| Which chart fits the data | ui-ux-pro-max, coloured from the tokens |
The rule underneath the table: when they disagree about how something looks, the design skill wins; when they disagree about whether a person can use it, ui-ux-pro-max wins, and the fix happens inside the design system. A darker step from the same colour ramp, not a new colour.
Where it goes wrong
The failure is letting the catalogue choose. A broad catalogue is a feature when you have no system and a problem when you do: ask for a page and a recommended style gets picked, and a recommended style is by definition one many pages already use. The generic look comes back through the side door. Say it in the design skill explicitly: never take a palette, style or font pairing from the catalogue while this skill is active.
One exception worth writing down
Usability guidance is written for the web, so it will flag a 26px button as below the touch target. On a website it is right. Inside a desktop app driven by a pointer, dense 13px controls are correct, and forcing 44px targets makes the app look like a web page. If your design skill targets a native-feeling app, as macOS Native Dark UI does, say where the rule does not apply.
Every skill in our catalogue ships a short setup guide for exactly this pairing, with the anti-generic checklist from why AI-generated UI all looks the same.
Questions
What is ui-ux-pro-max?
An open-source Claude Code skill by nextlevelbuilder, MIT licensed, with a large catalogue of UI styles, palettes and font pairings plus usability guidelines on accessibility, touch targets, layout and performance. It is a separate project; we did not write it.
Can I use ui-ux-pro-max and a design system skill at the same time?
Yes, and it works well, as long as they are not both choosing the look. Let the design skill own palette, type and components, and let ui-ux-pro-max check contrast, focus, touch targets, loading states and layout inside those choices.
Why does my UI still look generic with ui-ux-pro-max installed?
Usually because its style catalogue is doing the choosing. A catalogue offers many good styles, and picking the recommended one is how a page ends up looking like other generated pages. Give the look to a design skill and keep ui-ux-pro-max on usability.
Keep reading
Or skip the afternoonand drop one in.
Every skill in the catalogue is a folder you drop into your skills directory. Each ships with its design rules, worked examples and a troubleshooting table, and downloads the moment you pay.