Design and implement web or iOS interfaces using the product’s existing components and design rules. Define required screen states and responsive behavior, consult optional visual references when useful, and inspect the rendered result when supported.
Stop coding agents from shipping generic UI. Extend the product's design system, use UIZZE evidence only when useful, cover required states, and inspect the rendered result.
Run score Not tested
See how to installThis skill supports designing, building, improving, and reviewing web or iOS interfaces in line with a product’s goals and existing design. It helps clarify the main user actions and information, then prioritizes existing components, typography, spacing, and interaction patterns. It also considers loading, empty, error, success, disabled, and permission-specific states. When the environment allows, it renders the screen so visible clipping and overlap can be checked.
Use it when adding screens to an existing service or aligning appearance and interaction during a major redesign. For visual questions that are hard to resolve, optional UIZZE reference screens can help assess information hierarchy and layout density.
The free skill and public catalogue work without an account or token. The authenticated UIZZE MCP is optional. Using reference screens does not grant permission to copy another product’s brand or assets. Product validation, accessibility and security reviews, and project-specific tests are separate needs.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI checked the SKILL.md for operations that need care and for setup requirements. The score comes only from actually running the skill (hands-on test).
Not counted in the score. Rated by AI (OpenAI Codex) as of Oct 24, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
Build product-specific UI with 800,000+ real web and iOS screens via UIZZE.
Use the product brief, existing interface, components, and local design system before reaching for outside references. UIZZE evidence is optional: it should answer a concrete visual question, not turn every interface task into a research project.
Use this skill when designing, implementing, redesigning, critiquing, or doing a pre-ship review of a web or iOS interface.
The free skill and public catalogue work without an account, token, dependency, script, or executable. If a concrete unresolved visual question would benefit from evidence, use the smallest relevant set of screens or materials.
The optional authenticated UIZZE MCP exposes exactly find_ui_references and
find_ui_materials. Use it only when those tools are actually available. If a
search returns nothing, continue silently from repository evidence. Never claim
an MCP-backed result that was not returned by the host.
Treat references as evidence, not templates. Transfer useful decisions about hierarchy, density, navigation, controls, responsive behavior, and state handling; never copy another product's branding, proprietary text, imagery, or exact layout.
Install the current free skill directly from its canonical source:
npx skills add https://uizze.com --skill anti-ui-slop
When the environment supports it, render and inspect the result once. Fix observable breakage such as clipping, overlap, distorted media, inaccessible or inert controls, missing required states, and unintentional responsive behavior. Run the project's normal checks and keep the handoff concise.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Assess a new or existing AI project by examining its code, goals, and constraints. Recommend skills confirmed to exist in the available registry, then outline tasks and implementation phases with dependencies, completion criteria, and checks.
Review code and infrastructure for security risks, map potential threats, and plan stronger defenses. The skill covers OWASP checks, attack and defense exercises, and incident response, with validation required for each environment.
Turn a repeatable task into an Andru.ia skill with clear inputs, outputs, examples, and limits. Draft SKILL.md, check the folder structure and required validations, and prepare a pull request describing the changes for review.
Prepare an industry briefing once a project's sector is defined. It covers sector context, potentially applicable regulations, familiar interface patterns, technology choices, and risks, while separating verified evidence from hypotheses and questions requiring further review.
Create presentation drafts from text, outlines, or documents through the 2slides API. Match a reference image's style, choose themes, add AI voice narration, and export slide images or audio for review and use.
Plan a 360-degree or peer feedback process and create empty response templates from confirmed requirements. Produces consistent CSV, SQL, JSON Schema, or Notion property mappings while keeping visibility choices and scoring configuration separate.