UIZZE · Better UI for coding agents

Build interfaces that look like your product. Give Codex, Claude Code, Cursor, and GitHub Copilot a focused UI workflow, with optional references from 800,000+ real web and iOS screens.

Explore UIZZE → · Try a workflow · Connect MCP · Add the PR check

Watch UIZZE before and after

30-second mobile UI comparison: No skills on the left, MCP + Skills on the right.

https://github.com/user-attachments/assets/0137638f-d963-4e6b-a1a6-d7e2dce87600

Build your next screen with UIZZE →

Try a billing screen in Claude Code, Cursor, or Copilot: install, copy the brief, connect optional reference search, and check the result.

Start with your next screen

Install the free UI design skill:

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

Then give your agent a real task:

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.

The skills work without an account or MCP connection. Start in an existing project: your brief, components, and design system guide the work.

For a focused review, install anti-ui-slop instead:

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

Prefer installing from GitHub? Use npx skills add uizze/uizze --skill ui-design. The domain packages remain canonical; this repository mirrors all three skills.

Bring real product references into the conversation

Use UIZZE when the agent needs to see how real products handle a specific design problem: a dense settings page, a permission flow, an invoice table, or an iOS onboarding screen.

The optional paid MCP connects your agent to focused reference and material search:

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.

Create an agent token in UIZZE, then follow the MCP setup guide. References inform the design; the agent builds the interface in your own product's style. If a search returns no useful evidence, continue from the project.

Use it where you already build

Catch unfinished UI in pull requests

The free UI Slop Gate checks changed frontend source for inert controls, missing state markers, hardcoded colors, and combinations of generic dashboard cues. Findings appear next to the code and in the workflow summary.

permissions:
  contents: read

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

No account, API key, or source upload. Watch the published Action check a before-and-after example, then copy the complete workflow. This is a conservative source check; use rendered inspection and your normal accessibility and usability checks alongside it.

Build a screen with a worked example

• Free UI task-brief builder: describe the task, user, and outcome; copy or download a concrete agent prompt. No account required.
• SaaS dashboard walkthrough: compare information hierarchy and try loading, empty, error, and assignment states.
• DESIGN.md template: download a design contract and apply it across settings and billing.
• Empty-state examples: distinguish first use, no matches, service failure, and unavailable access.
• iOS onboarding and recovery: try a small browser prototype and explore the native SwiftUI starter.

These are original UIZZE teaching examples with fictional data. Browse all guides for agent-specific setup, comparisons, and review workflows.

Explore the repository

• Practical agent workflows: billing settings, data tables, permission screens, and native iOS.
• Reproduce a pull-request check: source, findings, and a local command.
• Next.js starter: an existing starting point for a product-specific interface.
• Storybook integration: review UI states alongside your components.
• Public distribution: maintained install and catalog paths.

Production metadata: skills index · MCP manifest · server card · documentation.

License

Uizze-authored repository code and text use MIT unless a more specific notice applies. Bundled skill playbooks retain their Apache-2.0 license and third-party notices. See the license map before redistributing a skill package.