Labsco
Labsco/Plugins/nextlevelbuilder/ui-ux-pro-max-skill
PLUGIN / NEXTLEVELBUILDER

UI UX Pro Max

Looks up a style, a palette and a type pairing to fit whatever is being built, then holds the assistant to them as the screens go together.

OFFICIAL★ 101.3k GitHub starsMITView on GitHub ↗

Labsco Summary

ShowHide
Request a screen and you get design decisions first — layout, style, colours, fonts, things to avoid — with the markup coming after.

A spa landing page, decided before it is written.

Ask for a landing page for a beauty spa and the first thing back is not code. It is a set of decisions, looked up rather than invented:

  • a page structure, and the order the sections run in
  • a named visual style, with the colours and the two fonts that go with it
  • the effects and transitions that suit it
  • what to avoid in that trade — no harsh animation on a wellness brand, no purple-pink gradients on a bank
  • a checklist to clear before handing it over: drawn icons rather than emoji, visible focus states, hover states, four screen widths

Only then does it start on the markup.

Seven skills, cut by what they decide.

Seven skills, and the line between them is what they decide rather than what they make:

  • Deciding what it should look like — 2
  • Turning the decisions into code — 2
  • Making the logos, banners and decks — 3

Taken in that order: settle the look, fix the values the code reads, then produce the artwork.

One skill claims what the others do.

One of the seven, design, claims its siblings' ground inside its own scope — brand identity, design tokens, interface styling and banners are all in its description — and adds logos, icons, a corporate identity set and social images on top. Nothing in the repository says whether to start from design or from the narrower skill that covers the same ground.

Logos, icons and the corporate identity set need a Gemini key, though Atlas Cloud or MuAPI can stand in for logos; social images need no key, because they are HTML screenshots. What a logo costs to generate is not stated anywhere.

The authors' route: an installer, run in your project.

The repository recommends its own command-line installer over the marketplace pair. Run it from inside your project folder, because uipro init sets the skill up in the folder it is started from:

  • for another assistant, change claude in uipro init --ai claude to cursor, windsurf, copilot, codex or gemini
  • add --global to have it in every project

The authors say the installer carries the current templates and lays the files out the way each assistant expects. One thing it will not supply: the search underneath all of this runs on Python 3, which has to be on the machine already.

What gets installed: 7 skills

Skills

Design choices get settled before any markup exists. A bundled reference of style names, palettes, type pairings and usability rules is searched for whatever matches the product in hand; separately, a brand's own voice, colours and type are set down once, so that every later answer stays inside them.

brandA brand only stays consistent if its voice, colors, and type live somewhere other than people's memory; this is that somewhere, and it feeds the same values into the code the product is built from.ui-ux-pro-maxDesign decisions — which colors, which typeface, how big a tap target has to be — get looked up in a bundled reference of what works, instead of being invented on the spot.