跳到主内容
智客 ZICQ

技能库 智客分类:设计创意 anti-ui-slop

Anti Ui Slop

停止运输通用UI的编码代理. 使用UIZZE的80万+正版网络和iOS屏幕来构建产品专用界面,定义设计合同,覆盖需要的状态,并运行一个硬尾门. 在设计,执行,重新设计,克流,或预发任务时使用,在Codex,Claude Code,Cursor,Copilot,或另一个编码代理中审查网络或iOS接口. 触发器有"反取出"(Anti-ui-slop),"停止UI slop","将UI打入真实屏幕",或"运行UI完成门"等.

13 安装量

官方网址:skills.sh

技能介绍

先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。

做什么

停止运输通用UI的编码代理. 使用UIZZE的80万+真网络和iOS屏幕来构建产品专用界面,定义设计合同,覆盖所需的状态,并运行一个硬完成门

何时用

设计、实施、重新设计、克勒提克或预发式审查Codex、Claude Code、Cursor、Copilot或其他编码代理中的网络或iOS接口。 触发器有"反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反一反

代理如何加载

按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:Stop Making UI Slop、Overview、Quick path、Prerequisites、Authentication、Work from the product。 其中含规范建议的小节:分步指令。

文件分析

文件分析:除 SKILL.md 外,正文引用了 scripts/count-finish.mjs、references/uizze-critique.md、references/uizze-image-to-ui.md、references/uizze-reference-policy.md、references/uizze-visual-verification.md,属于带资源的技能包,这些文件按需再读。

官方 description(原文)

Stop coding agents from shipping generic UI. Use UIZZE's 800,000+ real web and iOS screens to build product-specific interfaces, define a design contract, cover required states, and run a hard finish gate. Use when designing, implementing, redesigning, critiquing, or pre-ship reviewing a web or iOS interface in Codex, Claude Code, Cursor, Copilot, or another coding agent. Trigger with "anti-ui-slop", "stop UI slop", "ground this UI in real screens", or "run the UI finish gate".

Stop Making UI SlopOverviewQuick pathPrerequisitesAuthenticationWork from the productResearch before choosing the targetImage first, then implementSelect the workflowOptional Uizze evidenceFinish

· 许可:Apache-2.0; see LICENSE and NOTICE for attribution · allowed-tools:Read, Glob, Grep, WebFetch

来源分类:skills.sh agent-skill

SKILL.md 与 Agent 调用

官方规范 ↗
name
anti-ui-slop
description
Stop coding agents from shipping generic UI. Use UIZZE's 800,000+ real web and iOS screens to build product-specific interfaces, define a design contract, cover required states, and run a hard finish gate. Use when designing, implementing, redesigning, critiquing, or pre-ship reviewing a web or iOS interface in Codex, Claude Code, Cursor, Copilot, or another coding agent. Trigger with "anti-ui-slop", "stop UI slop", "ground this UI in real screens", or "run the UI finish gate".
allowed-tools
Read, Glob, Grep, WebFetch实验字段,支持情况取决于客户端;字段声明本身不会授予工具权限。
许可
Apache-2.0; see LICENSE and NOTICE for attribution
  1. 发现技能客户端向 Agent 提供名称与描述目录。
  2. 匹配与调用用户指定或任务匹配后,载入 SKILL.md 指令。
  3. 按需加载按步骤读取参考文档、使用脚本与素材。
指令中引用的文件 · 5
  • scripts/count-finish.mjs
  • references/uizze-critique.md
  • references/uizze-image-to-ui.md
  • references/uizze-reference-policy.md
  • references/uizze-visual-verification.md

以下路径提取自原文;文件是否齐全请以来源仓库中的完整目录为准。

具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗

安装这个技能

Skills CLI ↗

先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。

该技能引用了附属文件,请从来源获取完整目录;仅复制 SKILL.md 可能缺少依赖。

交给 Agent 安装

复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。

把 Agent Skill「anti-ui-slop」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-c661d01c08d0f2da-Anti-Ui-Slop.html
请存为 .cursor/skills/anti-ui-slop/SKILL.md 或 .claude/skills/anti-ui-slop/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。
该技能还带 scripts/、references/、assets/ 等文件,请从 https://skills.sh/uizze.com/anti-ui-slop 取完整目录,不要只建一个 SKILL.md。

当前没有明确的 GitHub 技能包地址,请按来源页面的安装器说明操作。

skills.sh ↗

阅读排版
--- name: anti-ui-slop description: Stop coding agents from shipping generic UI. Use UIZZE's 800,000+ real web and iOS screens to build product-specific interfaces, define a design contract, cover required states, and run a hard finish gate. Use when designing, implementing, redesigning, critiquing, or pre-ship reviewing a web or iOS interface in Codex, Claude Code, Cursor, Copilot, or another coding agent. Trigger with "anti-ui-slop", "stop UI slop", "ground this UI in real screens", or "run the UI finish gate". license: Apache-2.0; see LICENSE and NOTICE for attribution allowed-tools: Read, Glob, Grep, WebFetch metadata: version: "1.4.0" author: "UIZZE " compatibility: "Designed for Claude Code, Codex, Cursor, and GitHub Copilot; works in any agent that can read project files and fetch a URL." tags: "ui-design, design-system, design-review, frontend, web-ui, ios-ui" --- > **Stop AI coding agents from shipping generic UI.** # Stop Making UI Slop Build product-specific UI with 800,000+ real web and iOS screens via [UIZZE](https://uizze.com). ![Stop Making UI Slop with UIZZE](https://uizze.com/landing/anti-ui-slop-skill-banner.png) ## Overview Use the product brief, existing UI, components, and local design system to make intentional interfaces. Uizze supplies focused design guidance and, when useful, a small number of relevant visual references. ## Quick path For one web page or screen, this is enough. Read the playbooks below only when the task needs them. 1. **Contract:** write down the audience, the primary task, this category's default page and its predictable opposite. Choosing the opposite is still a rut, so name what this product does that neither one shows. When the Uizze MCP is connected, fetch one real screen of this kind and keep it as the comparison target for step 5. 2. **Show the product in the default view:** the first screen should prove the product's own idea without a click. Never invent customers, testimonials, statistics or capabilities. 3. **Build the real states:** loading, empty, error and success where they exist. Keep destructive actions quiet until they are needed. Long values such as email addresses must stay readable on a phone. 4. **Count before you finish:** 1 accent hue, every corner radius from one stated scale, 0 emoji in UI chrome, 0 gradients without a brand reason, 0 duplicate labels for one intent, 0 inert controls, every data view with loading, empty and error states. Run `node /scripts/count-finish.mjs --radius ` when Node is available and feed its output to the critique; a failed count is a fix, not a judgment call. 5. **Critique in a separate context, fix one thing, stop at three:** render desktop and phone width (headless Chrome will not lay out below about 500px with `--window-size` and crops instead, so load the page in a 390px-wide iframe). Then run [the critique round](references/uizze-critique.md): a fresh subagent or a second model, given the contract, the render and the comparison target, names the single highest-impact difference. Fix that one thing, render again, at most three rounds, and keep the best candidate rather than the last. Do not grade your own render: the agent that wrote the code anchors on what it produced. Skip what you cannot use: no image tool means no image target, and a task that allows no extra files means no receipt. Say what you skipped in the handoff. ## Prerequisites - A screen or component to build, redesign, or review — a file path or a short description. - The product's existing components, design tokens, and visual language, so the build extends them instead of inventing a new system. - Optional access to the paid Uizze MCP for focused references and hosted materials. ## Authentication - The free skill and public catalogue work without an account, token, MCP connection, dependency, script, or executable. - The optional full UIZZE MCP may use the host's normal connection and authentication flow. Never claim it is connected without an actual host result. ## Work from the product Read the brief, existing UI, components, tokens, assets, and any PRODUCT.md or DESIGN.md before designing. The user's request and project constraints outrank this skill. Preserve an established visual system for extensions and polish; replace it only for an approved redesign. A new project does not require those files. Identify the audience, primary task, important states, and intended result. Ask only about missing choices that would materially change the work. A precise request is enough to proceed; do not turn a small fix into a discovery workshop. ## Research before choosing the target For a new design, an approved redesign or a substantive improvement, use [the research playbook](reference/research.md): the agent discovers and inspects relevant screens and flow steps, selects useful examples, and turns their lessons into a checkable specification. Do this automatically before generating a new target; do not require manual browsing, a saved collection or shortlist approval. Supplied references and existing product constraints retain authority when present; small technical fixes need no research ceremony. Apply [anti-slop craft](reference/anti-slop-craft.md) for visual consistency and, when relevant, navigation and motion. Preserve deliberate brand exceptions and native platform behavior. Load these supporting playbooks only when the task needs them: - Native inputs, sheets and menus: [mobile controls](reference/mobile-controls.md). - Data-backed flows, recovery, typing or measured latency: [state and performance](reference/mobile-state-performance.md). - New or revised illustrations and imagery: [image assets](reference/image-assets.md). - Native screen, gesture and full-flow checks: [native verification](reference/native-verification.md). ## Image first, then implement Follow [Uizze's image-to-UI workflow](references/uizze-image-to-ui.md) before visual implementation. For new visual work or an approved redesign, use an available authorized image-generation tool to create and inspect the actual UI target before writing UI code. A supplied approved image is already the target; do not regenerate it. Save its actual dimensions and implement it 1:1 with real text, components and working controls. Render at the target viewport after fonts and images load, compare side by side or with an overlay, and correct visible differences before claiming a match. Keep the target stable rather than redesigning it to fit the code. Small technical fixes, read-only audits and unavailable image tools do not require a new image; disclose limitations and preserve the existing system. ## Select the workflow Load the playbook for the requested action, plus the platform and craft guidance needed to execute it: - New interface or major redesign: [new-work](reference/new-work.md) - Product or dashboard work: [operate](reference/operate.md) - Refinement and polish: [polish](reference/polish.md) - Simplification: [distill](reference/distill.md) - Explicit web audit: [audit](reference/audit.md), read-only unless fixes were requested - Native iOS: [iOS](reference/ios.md), alongside the action's playbook; for an audit, use [native audit](reference/audit.native.md) instead of a DOM scan - Explicit `/overdrive`, “Uizze Overdrive”, or a request for exceptional interaction work: [Overdrive](reference/overdrive.md) For implementation, use [craft](reference/craft.md) after the direction is settled. Load only relevant files; multiple complementary playbooks are allowed. Overdrive is opt-in, not the default for ordinary UI work. It requires a chosen direction before implementation. “Use Uizze Overdrive on this screen” works through this router; a native slash command depends on the host. These are self-contained Markdown playbooks, not an installer, background service, or executable engine. ## Optional Uizze evidence Read [the reference policy](references/uizze-reference-policy.md) before using `find_ui_references` or `find_ui_materials`. Inspect relevant visual evidence when it can inform the layout, state, interaction, or assets. A returned screen's job is to anchor the contract and the critique: compare the build against it; do not copy it. Use the host's available tools, not invented calls or connections. Paid retrieval is optional; missing access does not block local design work. Distinguish an exact reference, a related example, no match, and a service error. Briefly disclose a limitation that affected the result. Never claim an image was inspected or a state was found without evidence. ## Finish Build the requested scope and exercise its important states. Render the real result at representative desktop/mobile sizes or native device classes, including the user's reported failing size. Critique in a separate context using [the critique round](references/uizze-critique.md): a fresh subagent or a second model, given the contract, the captures and the chosen direction or supplied reference, names the single highest-impact difference. The agent that wrote the code does not grade its own render. Fix that one thing, render again, and stop after three rounds or when the critic finds nothing material; keep the best candidate rather than the last. Count the finish checks rather than judge them with `scripts/count-finish.mjs`: inert controls, missing loading, empty and error states, raw colours or radii outside the contract, default decoration, duplicate labels; check contrast and focus in the render. If a bounded pass cannot resolve an issue, report it instead of claiming a pass. When rendering is unavailable, distinguish code checks from visual verification. Save the actual captures, tested states and source hashes using [visual verification](references/uizze-visual-verification.md). Its optional local integrity check rejects missing or stale evidence; it does not judge aesthetics or replace inspection. Link the receipt in the handoff and keep blocked checks explicit. Keep the handoff concise: what changed, what was actually tested, and any remaining limitation. A skill does not authorize publishing, purchases, new dependencies, account changes, or destructive actions.

相关技能

设计创意

Automation Workflows

设计和实施自动化工作流程,以节省时间和规模化操作作为独家. 用于识别重复任务实现自动化,构建跨工具的工作流程,设置触发器和行动,或优化现有自动化. 包括自动化机会识别,工作流程设计,工具选择(Zapier,Make,n8n),测试,和维护. 触发"自动","自动","工作流程自动…

设计创意

Ui Ux Pro Max

UI/UX设计智能及建筑抛光接口实施指导. 当用户要求UI设计,UX流量,信息架构,视觉风格方向,设计系统/托盘,组件规格,副本/显微镜,可访问性,或生成/critique/refine前端UI(HTML/CSS/JS,React,Next.js,Vue,Svelte,Tailw…

设计创意

Frontend Design

创建美丽现代UI的专家前端设计指南. 在构建起落架页面,仪表板,或任何用户界面时使用.

设计创意

N8n Workflow Automation

设计和输出 n8n 工作流程 JSON 有强力触发器, idempotency, 错误处理, 记录, 重试, 以及 人入"一站"审查队列. 当您需要可审计的自动化时使用.