UIZZE · Better UI for Coding Agents

What does this agent do, and when should you use it?

UIZZE is a repository of UI design skills and checks aimed at coding agents rather than at hand-written design work. Its free core is three installable skills: ui-design for building or redesigning a screen, anti-ui-slop for fixing a generic first draft, and ui-radar for investigating a specific UI decision against references. Skills install through `npx skills add` from the uizze.com domain packaging, with uizze/uizze on GitHub mirroring the same three skills, and they work without an account. An optional paid MCP server adds two tools, find_ui_references and find_ui_materials, that retrieve up to three full-screen web or iOS references and up to three fonts, icons, animated icons or requested material packs per call. The repo also ships a free UI Slop Gate GitHub Action that scans changed frontend source in pull requests for inert controls, missing state markers, hardcoded colors and combinations of generic dashboard cues. It does not generate your interface for you: agents still implement screens using your own components and design tokens.

The repository contains three skill packages under skills/ui-design, skills/anti-ui-slop and skills/ui-radar, installed with npx skills add https://uizze.com --skill <name> or, from the GitHub mirror, npx skills add uizze/uizze --skill ui-design. Once installed, you hand the agent a real task as a prompt; the skill guides it through information hierarchy, reuse of existing components and design tokens, coverage of loading, empty, error and permission states, and inspection of the result at desktop and mobile sizes. With the optional paid MCP connected, the agent can call find_ui_references for up to three full-screen references per result and find_ui_materials for up to three hosted fonts, icons, animated icons or explicitly requested packs; when a search returns no useful evidence, work continues from the project. Separately, the UI Slop Gate Action (uses: uizze/uizze@v1) reads changed frontend source in a pull request, reports findings inline and in the workflow summary, and can fail the run with fail-on: error. Supporting distribution includes a Next.js starter, a Storybook integration, and Gemini CLI and Antigravity plugins.

1. Redesigning a billing settings page in an existing SaaS codebase so the current plan, payment method and invoices scan quickly, with loading, empty, error and permission states covered by ui-design.
2. A landing page just came out of an agent looking like a template; install anti-ui-slop to push product-specific content, deliberate layout and a finish review.
3. You are about to build a team permissions screen with inherited roles and restricted actions and want to see how real products handled it, so you connect the MCP first and implement second.
4. You want to catch inert buttons and hardcoded colors before merge, by adding the UI Slop Gate Action to a frontend repository without any account or API key.
5. You are trying your first screen in Claude Code, Cursor or GitHub Copilot and want a guided path, using the billing-screen walkthrough to verify the skill actually changes output.
6. You are designing an iOS onboarding and account-recovery flow and want the native SwiftUI starter and browser prototype the repo points to.

How do you install or deploy this agent?

Install the free UI design skill (no account needed; skills work without an MCP connection):

npx skills add https://uizze.com --skill ui-design

For a focused anti-slop review instead:

npx skills add https://uizze.com --skill anti-ui-slop

Prefer installing from GitHub? Use the mirror path:

npx skills add uizze/uizze --skill ui-design

To add the pull-request gate, put this in your workflow:

permissions:
  contents: read

steps:
  - uses: actions/checkout@v7
    with:
      fetch-depth: 2
      persist-credentials: false
  - uses: uizze/uizze@v1
    with:
      fail-on: error

The optional paid MCP requires creating an agent token in UIZZE first, then following the MCP setup guide under integrations/mcp.

How do you use this agent?

After installing ui-design, give your agent a real task and tell it to reuse your components and tokens:

Use ui-design to improve our billing settings page. Make the current plan,
payment method, and invoices easy to scan. Reuse our components and design
tokens. Include loading, empty, error, and permission states. Inspect the
result at desktop and mobile sizes and fix what breaks.

With the MCP connected, ask for evidence before implementation:

Find references for a team permissions screen with inherited roles and
restricted actions. Explain which decisions would help our workflow,
then implement them using our existing components and visual language.

To reproduce the pull-request check locally, follow the source, findings and local command documented in the pull-request-check example.

What are this agent's strengths and limitations?

How does this agent compare with similar options?

Key facts side by side with the most closely related agents.

How does FollowAgents rate this agent?

FAQ