Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Design & UI

ui-ux-designer

How to design and review anything people see or read in this product (screens, flows, states, copy): the method, the rules, the visual system, the voice and brand, and the product's names. Use it to design or build UI, to review a screen, a plan's UI or a pull request's screenshots, to write or check user-facing copy, and for the voice and brand in marketing and on the website.

abidwaqar · Static checks on file

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

npx skills add abidwaqar/AI-Judgment-Orchestration --skill ui-ux-designer

About this skill


name: ui-ux-designer description: "How to design and review anything people see or read in this product (screens, flows, states, copy): the method, the rules, the visual system, the voice and brand, and the product's names. Use it to design or build UI, to review a screen, a plan's UI or a pull request's screenshots, to write or check user-facing copy, and for the voice and brand in marketing and on the website."

UI/UX design

The method, the system and the rules. The code is the reference for how each screen works today: read a screen's code before designing a change to it. This skill doesn't describe screens one by one.

The product.

1. Start with the sentence

Before designing or judging anything, write: for [who], doing [job], at [moment]. A screen is only good or bad for a person, a job and a moment.

  • Who: the people the product is for. Name the one who mustn't get lost (often the newcomer) and the one who mustn't be slowed (often the regular who uses it every day). A design that serves one by failing the other isn't done.

  • The job: what they want right now, such as what to do next, whether something worked, or how far along they are.

  • The moment. Most products have two kinds:

    • The glance: a person in the middle of something else. On the move, one hand, noise, a weak signal, a few seconds of attention. Big targets, values filled in, one obvious next action, almost nothing to read.
    • The sit-down: setting up, planning, reviewing. People read and compare, so explanations, detail, choices and charts belong here.

    A job that takes minutes of thought is a sit-down job wherever the person is. The commonest mistake is sit-down content on a glance screen.

  • People scan, take the first reasonable option, and muddle through. A screen that only works when read carefully doesn't work.

2. The rules

Hierarchy

  • One primary per surface: one accent-coloured element. Usually that's the main action, the current item's marker, or one accent label. Two accent things means neither leads. A button repeated on every card is plain secondary, never the accent.
  • Three levels are enough, each clearly different from the next.
  • Emphasise by de-emphasising: quiet labels, loud values. Make the competing elements quieter rather than the important thing louder.
  • The primary moves with the task. On a screen used over time (a multi-step form, a setup flow), the loudest thing is what comes next, never the last step.

Grouping, spacing and alignment

  • Close means together. The space inside a group is half the space between groups or less (8 inside, 24 between). An evenly spaced stack doesn't group.
  • The scale.
  • One left edge per screen. Table headers sit over their columns, and compared numbers are right-aligned.
  • Space before boxes: add a border only when space can't group. No boxes inside boxes.
  • Whitespace communicates certainty. Don't compress a screen to expose secondary information.

Type

  • The project's text styles only, never one-off sizes.
  • Few sizes per screen. Build hierarchy with weight and grey level (primary, secondary and muted text) before size. The biggest text is the most important thing.
  • Line height: 120–130% for headings, 145–155% for body.
  • Case: sentence case. Uppercase only for small spaced labels. Bold sparingly.
  • Never cut meaning. A cut-off name is fine; a cut-off explanation isn't. Numbers that change, like timers, use tabular figures.

Colour

  • Tokens, never raw colour values. Every surface works in every theme the product has.
  • One colour, one meaning:
    • the accent is "do this" or "you are here", never "bad";
    • success is done or good;
    • error is something that can go wrong (destructive actions, failures), never a normal action or a running clock;
    • charts and bars are neutral unless the line is the screen's one accent element.
  • Accent words need a text-safe accent. If the accent fails 4.5:1 as small text, keep a text-safe variant of it for words, and use the accent itself for fills, borders, icons and charts. A white label on an accent button is fine when it passes.
  • Error words (messages, field errors, destructive labels) use the text-safe error colour. The plain error colour is for borders, icons, dots and fills.
  • A scrim is the same dark neutral in every theme, with an alpha where it's used. A light scrim leaves a white card with no boundary.
  • Contrast: 4.5:1 for normal text, 3:1 for large text (about 24 px regular,
Read the complete source ↗