mirror of
https://github.com/github/awesome-copilot.git
synced 2026-08-24 09:56:51 +00:00
chore: publish from main
This commit is contained in:
github-actions[bot]
+9
-11
@@ -1,6 +1,6 @@
|
||||
# UIZZE Plugin
|
||||
|
||||
Stop generic UI from shipping. UIZZE gives GitHub Copilot a repeatable workflow for turning real interface evidence into a product-specific design contract, then checking the result against a hard finish gate.
|
||||
Stop generic UI from shipping. UIZZE helps GitHub Copilot build product-specific interfaces and finish the states that make them usable.
|
||||
|
||||
## Installation
|
||||
|
||||
@@ -12,16 +12,16 @@ copilot plugin install uizze@awesome-copilot
|
||||
|
||||
| Skill | Description |
|
||||
|---|---|
|
||||
| `anti-ui-slop` | Selects relevant interface references, extracts reusable design decisions, writes an implementation-ready design contract, and blocks completion until specificity, interaction states, responsiveness, accessibility, and design-system integrity pass review. |
|
||||
| `anti-ui-slop` | Uses the product brief and existing design system, loads one focused playbook, optionally finds relevant interface evidence, and checks the rendered result before completion. |
|
||||
|
||||
## How It Works
|
||||
|
||||
1. Inspect the target product, task, and existing design system.
|
||||
2. Search [UIZZE](https://uizze.com) for three to five relevant examples from its public catalogue of 800,000+ real web and iOS screens.
|
||||
3. Convert the evidence into a design contract before implementation.
|
||||
4. Run the finish gate and fix every blocking issue before calling the UI complete.
|
||||
1. Inspect the target product, task, components, and existing design system.
|
||||
2. Load one focused playbook for the kind of interface work being done.
|
||||
3. Use UIZZE evidence only when a concrete visual question would benefit from it.
|
||||
4. Render once when possible and fix observable breakage before completion.
|
||||
|
||||
The skill remains usable when catalogue browsing is unavailable: it can work from user-provided references or repository evidence and will state which evidence is missing.
|
||||
The skill works from repository evidence alone. UIZZE references are optional, and an empty search result is a normal no-op.
|
||||
|
||||
## Requirements and Scope
|
||||
|
||||
@@ -29,13 +29,11 @@ The skill remains usable when catalogue browsing is unavailable: it can work fro
|
||||
- No MCP server is bundled with this plugin.
|
||||
- The skill is MIT licensed and useful on its own.
|
||||
|
||||
UIZZE maintains the public catalogue referenced by the skill.
|
||||
|
||||
For an optional, separate anonymous source check outside this plugin, use the [free UI slop preview](https://uizze.com/mcp/preview). It exposes exactly one deterministic `check_ui_slop` tool, requires no account or token, and is not required by this plugin.
|
||||
The optional, separate authenticated UIZZE MCP exposes exactly `find_ui_references` and `find_ui_materials`. It is not required by this plugin.
|
||||
|
||||
## Source
|
||||
|
||||
This plugin is part of [Awesome Copilot](https://github.com/github/awesome-copilot).
|
||||
This plugin is part of [Awesome Copilot](https://github.com/github/awesome-copilot). The canonical UIZZE packages are maintained at [uizze/uizze](https://github.com/uizze/uizze).
|
||||
|
||||
## License
|
||||
|
||||
|
||||
@@ -1,8 +1,8 @@
|
||||
{
|
||||
"$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
|
||||
"name": "uizze",
|
||||
"description": "Stop generic UI from shipping. Ground GitHub Copilot in 800,000+ real web and iOS screens, write a product-specific design contract, and enforce a hard finish gate.",
|
||||
"version": "1.0.0",
|
||||
"description": "Build product-specific interfaces with a focused UIZZE workflow, optional real-screen evidence, and a practical finish check.",
|
||||
"version": "1.2.13",
|
||||
"author": {
|
||||
"name": "UIZZE",
|
||||
"url": "https://uizze.com"
|
||||
|
||||
@@ -0,0 +1,13 @@
|
||||
f1411aac76d20cf8b94a6c1376daf1ddcd1005c338cf45831c5531aeb7391171 agents/openai.yaml
|
||||
02bb8c3b4e70190e3986c0404ad2fd8d639b4f534252d82379cc1b502b6d1812 LICENSE
|
||||
ac7cbac310d74dde573d18ac6caec6c51c3499eb9c766a043e4cfae75bc06daf MANIFEST.json
|
||||
5d84775dccdfbd3b9a1bfa634a79b17ad2742b6ab04f3684cd966f35294e9a39 MODIFICATIONS.md
|
||||
03efc08e3a77d4c5bf10b4abefa7348445b77aceba48ddd87fbf06adcbaee94f NOTICE
|
||||
0e8e36dbca739b4b545bb45608f18def6263402bc8268e263d653e3f05f90c39 reference/audit.md
|
||||
5cf9acf215f145ae152a53314f3a95f119b9984aa0cf7da8d61caf75619a65e9 reference/distill.md
|
||||
817cf6e7b79c6181658c618a4c5fe42cd06b9438f647daae86e241dfb1eea11d reference/ios.md
|
||||
da668bd62e99d88b9d76f7a970c02b135245611fabd669fd65cfeaf028441c8d reference/new-work.md
|
||||
be6eec1114d122a9a115e31ddf1568567792b33f03ce35ff9e12e96af302696d reference/operate.md
|
||||
8435138f1bf85d93654ca91f0e725bb271d4288ac352c6596e9a64ffcdada651 reference/polish.md
|
||||
21616e54cefae88396b521591e8b6170e82314c4abf06b9ca14453508c884477 references/uizze-reference-policy.md
|
||||
38beaf00024589581ed70bcf97e1372e0cdca8e08bfd69ee5e8d3b8beefb3f35 SKILL.md
|
||||
@@ -0,0 +1,191 @@
|
||||
Apache License
|
||||
Version 2.0, January 2004
|
||||
http://www.apache.org/licenses/
|
||||
|
||||
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
||||
|
||||
1. Definitions.
|
||||
|
||||
"License" shall mean the terms and conditions for use, reproduction,
|
||||
and distribution as defined by Sections 1 through 9 of this document.
|
||||
|
||||
"Licensor" shall mean the copyright owner or entity authorized by
|
||||
the copyright owner that is granting the License.
|
||||
|
||||
"Legal Entity" shall mean the union of the acting entity and all
|
||||
other entities that control, are controlled by, or are under common
|
||||
control with that entity. For the purposes of this definition,
|
||||
"control" means (i) the power, direct or indirect, to cause the
|
||||
direction or management of such entity, whether by contract or
|
||||
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
||||
outstanding shares, or (iii) beneficial ownership of such entity.
|
||||
|
||||
"You" (or "Your") shall mean an individual or Legal Entity
|
||||
exercising permissions granted by this License.
|
||||
|
||||
"Source" form shall mean the preferred form for making modifications,
|
||||
including but not limited to software source code, documentation
|
||||
source, and configuration files.
|
||||
|
||||
"Object" form shall mean any form resulting from mechanical
|
||||
transformation or translation of a Source form, including but
|
||||
not limited to compiled object code, generated documentation,
|
||||
and conversions to other media types.
|
||||
|
||||
"Work" shall mean the work of authorship, whether in Source or
|
||||
Object form, made available under the License, as indicated by a
|
||||
copyright notice that is included in or attached to the work
|
||||
(an example is provided in the Appendix below).
|
||||
|
||||
"Derivative Works" shall mean any work, whether in Source or Object
|
||||
form, that is based on (or derived from) the Work and for which the
|
||||
editorial revisions, annotations, elaborations, or other modifications
|
||||
represent, as a whole, an original work of authorship. For the purposes
|
||||
of this License, Derivative Works shall not include works that remain
|
||||
separable from, or merely link (or bind by name) to the interfaces of,
|
||||
the Work and Derivative Works thereof.
|
||||
|
||||
"Contribution" shall mean any work of authorship, including
|
||||
the original version of the Work and any modifications or additions
|
||||
to that Work or Derivative Works thereof, that is intentionally
|
||||
submitted to the Licensor for inclusion in the Work by the copyright
|
||||
owner or by an individual or Legal Entity authorized to submit on
|
||||
behalf of the copyright owner. For the purposes of this definition,
|
||||
"submitted" means any form of electronic, verbal, or written
|
||||
communication sent to the Licensor or its representatives, including
|
||||
but not limited to communication on electronic mailing lists, source
|
||||
code control systems, and issue tracking systems that are managed by,
|
||||
or on behalf of, the Licensor for the purpose of discussing and
|
||||
improving the Work, but excluding communication that is conspicuously
|
||||
marked or otherwise designated in writing by the copyright owner as
|
||||
"Not a Contribution."
|
||||
|
||||
"Contributor" shall mean Licensor and any individual or Legal Entity
|
||||
on behalf of whom a Contribution has been received by Licensor and
|
||||
subsequently incorporated within the Work.
|
||||
|
||||
2. Grant of Copyright License. Subject to the terms and conditions of
|
||||
this License, each Contributor hereby grants to You a perpetual,
|
||||
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
||||
copyright license to reproduce, prepare Derivative Works of,
|
||||
publicly display, publicly perform, sublicense, and distribute the
|
||||
Work and such Derivative Works in Source or Object form.
|
||||
|
||||
3. Grant of Patent License. Subject to the terms and conditions of
|
||||
this License, each Contributor hereby grants to You a perpetual,
|
||||
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
||||
(except as stated in this section) patent license to make, have made,
|
||||
use, offer to sell, sell, import, and otherwise transfer the Work,
|
||||
where such license applies only to those patent claims licensable
|
||||
by such Contributor that are necessarily infringed by their
|
||||
Contribution(s) alone or by combination of their Contribution(s)
|
||||
with the Work to which such Contribution(s) was submitted. If You
|
||||
institute patent litigation against any entity (including a
|
||||
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
||||
or a Contribution incorporated within the Work constitutes direct
|
||||
or contributory patent infringement, then any patent licenses
|
||||
granted to You under this License for that Work shall terminate
|
||||
as of the date such litigation is filed.
|
||||
|
||||
4. Redistribution. You may reproduce and distribute copies of the
|
||||
Work or Derivative Works thereof in any medium, with or without
|
||||
modifications, and in Source or Object form, provided that You
|
||||
meet the following conditions:
|
||||
|
||||
(a) You must give any other recipients of the Work or
|
||||
Derivative Works a copy of this License; and
|
||||
|
||||
(b) You must cause any modified files to carry prominent notices
|
||||
stating that You changed the files; and
|
||||
|
||||
(c) You must retain, in the Source form of any Derivative Works
|
||||
that You distribute, all copyright, patent, trademark, and
|
||||
attribution notices from the Source form of the Work,
|
||||
excluding those notices that do not pertain to any part of
|
||||
the Derivative Works; and
|
||||
|
||||
(d) If the Work includes a "NOTICE" text file as part of its
|
||||
distribution, then any Derivative Works that You distribute must
|
||||
include a readable copy of the attribution notices contained
|
||||
within such NOTICE file, excluding those notices that do not
|
||||
pertain to any part of the Derivative Works, in at least one
|
||||
of the following places: within a NOTICE text file distributed
|
||||
as part of the Derivative Works; within the Source form or
|
||||
documentation, if provided along with the Derivative Works; or,
|
||||
within a display generated by the Derivative Works, if and
|
||||
wherever such third-party notices normally appear. The contents
|
||||
of the NOTICE file are for informational purposes only and
|
||||
do not modify the License. You may add Your own attribution
|
||||
notices within Derivative Works that You distribute, alongside
|
||||
or as an addendum to the NOTICE text from the Work, provided
|
||||
that such additional attribution notices cannot be construed
|
||||
as modifying the License.
|
||||
|
||||
You may add Your own copyright statement to Your modifications and
|
||||
may provide additional or different license terms and conditions
|
||||
for use, reproduction, or distribution of Your modifications, or
|
||||
for any such Derivative Works as a whole, provided Your use,
|
||||
reproduction, and distribution of the Work otherwise complies with
|
||||
the conditions stated in this License.
|
||||
|
||||
5. Submission of Contributions. Unless You explicitly state otherwise,
|
||||
any Contribution intentionally submitted for inclusion in the Work
|
||||
by You to the Licensor shall be under the terms and conditions of
|
||||
this License, without any additional terms or conditions.
|
||||
Notwithstanding the above, nothing herein shall supersede or modify
|
||||
the terms of any separate license agreement you may have executed
|
||||
with Licensor regarding such Contributions.
|
||||
|
||||
6. Trademarks. This License does not grant permission to use the trade
|
||||
names, trademarks, service marks, or product names of the Licensor,
|
||||
except as required for reasonable and customary use in describing the
|
||||
origin of the Work and reproducing the content of the NOTICE file.
|
||||
|
||||
7. Disclaimer of Warranty. Unless required by applicable law or
|
||||
agreed to in writing, Licensor provides the Work (and each
|
||||
Contributor provides its Contributions) on an "AS IS" BASIS,
|
||||
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
||||
implied, including, without limitation, any warranties or conditions
|
||||
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
||||
PARTICULAR PURPOSE. You are solely responsible for determining the
|
||||
appropriateness of using or redistributing the Work and assume any
|
||||
risks associated with Your exercise of permissions under this License.
|
||||
|
||||
8. Limitation of Liability. In no event and under no legal theory,
|
||||
whether in tort (including negligence), contract, or otherwise,
|
||||
unless required by applicable law (such as deliberate and grossly
|
||||
negligent acts) or agreed to in writing, shall any Contributor be
|
||||
liable to You for damages, including any direct, indirect, special,
|
||||
incidental, or consequential damages of any character arising as a
|
||||
result of this License or out of the use or inability to use the
|
||||
Work (including but not limited to damages for loss of goodwill,
|
||||
work stoppage, computer failure or malfunction, or any and all
|
||||
other commercial damages or losses), even if such Contributor
|
||||
has been advised of the possibility of such damages.
|
||||
|
||||
9. Accepting Warranty or Additional Liability. While redistributing
|
||||
the Work or Derivative Works thereof, You may choose to offer,
|
||||
and charge a fee for, acceptance of support, warranty, indemnity,
|
||||
or other liability obligations and/or rights consistent with this
|
||||
License. However, in accepting such obligations, You may act only
|
||||
on Your own behalf and on Your sole responsibility, not on behalf
|
||||
of any other Contributor, and only if You agree to indemnify,
|
||||
defend, and hold each Contributor harmless for any liability
|
||||
incurred by, or claims asserted against, such Contributor by reason
|
||||
of your accepting any such warranty or additional liability.
|
||||
|
||||
END OF TERMS AND CONDITIONS
|
||||
|
||||
Copyright 2025 Paul Bakaus
|
||||
|
||||
Licensed under the Apache License, Version 2.0 (the "License");
|
||||
you may not use this file except in compliance with the License.
|
||||
You may obtain a copy of the License at
|
||||
|
||||
http://www.apache.org/licenses/LICENSE-2.0
|
||||
|
||||
Unless required by applicable law or agreed to in writing, software
|
||||
distributed under the License is distributed on an "AS IS" BASIS,
|
||||
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
||||
See the License for the specific language governing permissions and
|
||||
limitations under the License.
|
||||
@@ -0,0 +1,19 @@
|
||||
{
|
||||
"name": "anti-ui-slop",
|
||||
"version": "quiet-expert-v12",
|
||||
"designStack": {
|
||||
"version": "4.1.1",
|
||||
"commit": "5a149f3fdb1b5793f10567233b1dcab98fc305fd",
|
||||
"license": "Apache-2.0"
|
||||
},
|
||||
"designAuthority": "uizze",
|
||||
"evidenceMode": "concrete-need-only",
|
||||
"included": [
|
||||
"reference/new-work.md",
|
||||
"reference/operate.md",
|
||||
"reference/polish.md",
|
||||
"reference/distill.md",
|
||||
"reference/audit.md",
|
||||
"reference/ios.md"
|
||||
]
|
||||
}
|
||||
@@ -0,0 +1,3 @@
|
||||
# Modifications notice
|
||||
|
||||
Uizze packages a licensed design stack pinned at version 4.1.1, commit 5a149f3fdb1b5793f10567233b1dcab98fc305fd. Uizze maintains the router, reference policy, packaging, versioning, and distribution. Product-facing instructions use Uizze terminology.
|
||||
@@ -0,0 +1,12 @@
|
||||
# Third-Party Notices
|
||||
|
||||
This project includes content derived from third-party work, used under the terms of its original license.
|
||||
|
||||
## Platform Design Skills
|
||||
|
||||
The `reference/ios.md` playbook includes material distilled from ehmo's
|
||||
`platform-design-skills` (Apple Human Interface Guidelines).
|
||||
|
||||
**Original work:** https://github.com/ehmo/platform-design-skills
|
||||
**Original license:** MIT
|
||||
**Author:** ehmo
|
||||
@@ -1,109 +1,58 @@
|
||||
---
|
||||
name: anti-ui-slop
|
||||
description: 'Stop Codex, GitHub Copilot, Claude Code, and Cursor from shipping generic UI. Use UIZZE’s public catalogue of 800,000+ real web and iOS screens to extract product-specific design decisions and enforce a hard finish gate for web and iOS interfaces.'
|
||||
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: MIT
|
||||
metadata:
|
||||
version: "1.2.13"
|
||||
author: "UIZZE <business@uizze.com>"
|
||||
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"
|
||||
---
|
||||
|
||||
# Anti UI Slop
|
||||
> **Stop AI coding agents from shipping generic UI.**
|
||||
|
||||
Use this skill when building, refactoring, or reviewing a web or iOS interface. The goal is not to make a generic layout prettier. The goal is to make the interface visibly belong to this product, support its real user job, and behave correctly in every important state.
|
||||
# Stop Making UI Slop
|
||||
|
||||
Browse 800,000+ real web and iOS screens at https://uizze.com before choosing a layout.
|
||||
Build product-specific UI with 800,000+ real web and iOS screens via [UIZZE](https://uizze.com).
|
||||
|
||||
The workflow is instruction-only. It does not execute third-party code or require credentials.
|
||||
|
||||
|
||||
## 1. Inspect the Product Before Designing
|
||||
## Overview
|
||||
|
||||
Read the repository and identify:
|
||||
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.
|
||||
|
||||
- the primary user and the job this screen must complete;
|
||||
- the single primary action and the information needed before taking it;
|
||||
- the existing component library, design tokens, typography, and layout conventions;
|
||||
- real product nouns, workflows, constraints, and data already present in the codebase;
|
||||
- required loading, empty, error, partial, success, disabled, and permission states;
|
||||
- relevant mobile, tablet, desktop, keyboard, and assistive-technology behavior.
|
||||
## Prerequisites
|
||||
|
||||
Do not invent product requirements, analytics, user research, or hidden states.
|
||||
- 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.
|
||||
|
||||
## 2. Collect Real Interface Evidence
|
||||
## Authentication
|
||||
|
||||
Search the public catalogue at https://uizze.com and select three to five relevant web or iOS screens. Prefer references that match the target workflow, information density, navigation model, or interaction pattern—not merely its industry or color palette.
|
||||
- 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.
|
||||
|
||||
For each reference, record:
|
||||
## Work from the product
|
||||
|
||||
1. the screen or flow and its source link;
|
||||
2. the structural decision worth transferring;
|
||||
3. why that decision fits this product;
|
||||
4. what must not be copied.
|
||||
Read the brief, existing UI, components, tokens, and constraints before designing. They always outrank this skill. Keep familiar interaction conventions and make the product's own objects, workflow, and priorities visually clear. Do not add novelty for its own sake.
|
||||
|
||||
Transfer hierarchy, workflow shape, density, navigation, control behavior, responsive treatment, and state handling. Never copy another product’s branding, proprietary text, imagery, or exact layout.
|
||||
## Load one playbook
|
||||
|
||||
If catalogue browsing is unavailable, ask the user for two or three UIZZE links or screenshots. If they cannot provide them, continue from repository evidence and label the missing reference evidence explicitly.
|
||||
Choose at most one file for the current request:
|
||||
|
||||
## 3. Write a Design Contract
|
||||
- New interface or major redesign: `reference/new-work.md`
|
||||
- Product or dashboard work: `reference/operate.md`
|
||||
- Refinement and polish: `reference/polish.md`
|
||||
- Simplification or distillation: `reference/distill.md`
|
||||
- Explicit audit: `reference/audit.md`
|
||||
- Native iOS work: `reference/ios.md`
|
||||
|
||||
Before changing code, write a short contract with these fields:
|
||||
Do not load a second playbook. Apply judgment rather than treating its examples as a checklist.
|
||||
|
||||
| Field | Decision |
|
||||
| --- | --- |
|
||||
| Screen job | The one outcome this screen enables |
|
||||
| Primary user and action | Who acts, and what they do |
|
||||
| Content hierarchy | What must be understood first, second, and third |
|
||||
| Navigation and controls | Product-specific structure and interaction model |
|
||||
| Visual language | Type, spacing, density, surfaces, imagery, and motion rules |
|
||||
| Required states | Loading, empty, error, partial, success, disabled, permission |
|
||||
| Responsive behavior | What changes across supported widths and input modes |
|
||||
| Evidence used | Reference links and transferable decisions |
|
||||
| Forbidden defaults | Generic patterns that would erase product specificity |
|
||||
| Acceptance criteria | Observable conditions required before shipping |
|
||||
## Optional Uizze evidence
|
||||
|
||||
The contract must name concrete choices. “Clean,” “modern,” “intuitive,” and “premium” are not design decisions.
|
||||
Read `references/uizze-reference-policy.md` before using the paid MCP. It exposes exactly `find_ui_references` and `find_ui_materials`. Use them only when a concrete unresolved visual or material question would benefit from evidence. If they return nothing, continue silently.
|
||||
|
||||
## 4. Build in the Product’s Language
|
||||
## Finish
|
||||
|
||||
- Reuse the repository’s components and semantic tokens before adding new ones.
|
||||
- Make the primary action visually and structurally obvious.
|
||||
- Use product-specific labels and information rather than placeholder metrics or generic copy.
|
||||
- Keep repeated cards only when the content is genuinely a repeated collection.
|
||||
- Add decoration, motion, badges, or elevation only when they communicate state or hierarchy.
|
||||
- Implement every required interaction and state; do not leave convincing-looking inert controls.
|
||||
- Preserve accessibility semantics, focus order, contrast, touch targets, and reduced-motion behavior.
|
||||
|
||||
## 5. Run the Finish Gate
|
||||
|
||||
Render the result at every supported breakpoint and block completion when any item fails:
|
||||
|
||||
### Product specificity
|
||||
|
||||
- Could this interface belong to an unrelated product after changing the logo?
|
||||
- Does the hierarchy reflect the real user job and product data?
|
||||
- Are there interchangeable dashboard cards, filler metrics, vague headings, or generic calls to action?
|
||||
|
||||
### Interaction completeness
|
||||
|
||||
- Do all visible controls have a real outcome?
|
||||
- Are loading, empty, error, success, disabled, and permission states implemented where applicable?
|
||||
- Are destructive, irreversible, or sensitive actions confirmed appropriately?
|
||||
|
||||
### Responsive and accessible behavior
|
||||
|
||||
- Does the layout remain usable without merely stacking every region vertically?
|
||||
- Do keyboard navigation, focus visibility, semantics, contrast, and touch targets pass inspection?
|
||||
- Does content remain readable at zoom and with longer real-world text?
|
||||
|
||||
### Design-system integrity
|
||||
|
||||
- Are local tokens and components used consistently?
|
||||
- Is every new visual rule justified by the design contract?
|
||||
- Is borrowed evidence transformed into this product’s own visual language?
|
||||
|
||||
Fix every blocking failure and re-run the gate before declaring the UI complete.
|
||||
|
||||
## 6. Handoff Format
|
||||
|
||||
Report the finished work in this order:
|
||||
|
||||
1. **Evidence:** the references and decisions that influenced the result.
|
||||
2. **Contract:** the final product-specific design rules.
|
||||
3. **Implementation:** the meaningful interface and behavior changes.
|
||||
4. **Verification:** breakpoints, interaction states, and accessibility checks performed.
|
||||
5. **Remaining risks:** anything that could not be verified, without overstating completion.
|
||||
Complete the requested scope. When the environment supports it, render and inspect once. Fix observable breakage such as clipping, overlap, distorted media, inaccessible controls, or inert interactions. Keep the handoff concise.
|
||||
|
||||
@@ -0,0 +1,4 @@
|
||||
interface:
|
||||
display_name: "Uizze Anti UI Slop"
|
||||
short_description: "Design guidance with quiet visual evidence"
|
||||
default_prompt: "Use Uizze for design judgment. Retrieve evidence or materials only for one concrete unresolved need."
|
||||
@@ -0,0 +1,14 @@
|
||||
# Audit an implemented interface
|
||||
|
||||
Review only what can be observed in the implementation or rendered result. Do not invent missing requirements or turn personal taste into a defect.
|
||||
|
||||
Inspect:
|
||||
|
||||
- task clarity and hierarchy;
|
||||
- consistency with the product's existing system;
|
||||
- layout, overflow, media treatment, and responsive behavior;
|
||||
- interaction feedback and necessary loading, empty, error, success, disabled, and recovery states;
|
||||
- labels, focus, keyboard access, target size, and contrast;
|
||||
- obvious performance problems visible in the experience.
|
||||
|
||||
Return at most three material findings, ordered by user impact. For each finding, name the observable evidence and the smallest concrete correction. If nothing material is visible, say so briefly. An audit does not modify the product unless the user also asked for fixes.
|
||||
@@ -0,0 +1,20 @@
|
||||
# Simplify an interface
|
||||
|
||||
Remove obstacles between the user and the main task without removing necessary capability.
|
||||
|
||||
## Find the excess
|
||||
|
||||
- Identify the primary goal and the information required to complete it.
|
||||
- Remove repeated copy, duplicate actions, decorative noise, and containers that do not clarify grouping.
|
||||
- Reduce unnecessary variation in colors, type sizes, button styles, spacing, and surface treatments.
|
||||
- Prefer one obvious primary action and a small number of clearly subordinate actions.
|
||||
- Use progressive disclosure for advanced or infrequent controls, but keep essential information visible.
|
||||
|
||||
## Preserve clarity
|
||||
|
||||
- Do not hide required actions behind mystery interactions.
|
||||
- Do not remove labels, focus states, accessibility semantics, error messages, or recovery paths.
|
||||
- Do not flatten genuinely complex information until it becomes harder to understand.
|
||||
- Prefer spacing and alignment over nested cards; prefer plain language over explanatory copy.
|
||||
|
||||
Verify that the simplified result still supports the complete task, including its important states, at the relevant screen sizes.
|
||||
@@ -0,0 +1,17 @@
|
||||
# Native iOS interfaces
|
||||
|
||||
Follow the product's existing iOS conventions first, then Apple platform conventions. A native interface should feel predictable before it feels distinctive.
|
||||
|
||||
## Structure and controls
|
||||
|
||||
- Use a navigation stack for hierarchy, a tab bar for a small set of top-level destinations, and sheets for self-contained tasks.
|
||||
- Preserve the edge-swipe back gesture and safe-area behavior.
|
||||
- Prefer native controls, materials, menus, alerts, sheets, pickers, and text behavior unless the product already has a coherent custom system.
|
||||
- Keep touch targets comfortable, text scalable, labels accessible, and focus order sensible.
|
||||
- Account for the keyboard, long content, dynamic type, reduced motion, dark mode, and device insets.
|
||||
|
||||
## States
|
||||
|
||||
Include the states the task requires: loading, empty, error, success, permission denied, offline, disabled, and recovery where applicable. Feedback should be immediate and should not depend on color alone.
|
||||
|
||||
When a simulator or runnable build is available, inspect the relevant device class once and fix observable clipping, overlap, unsafe-area violations, unreadable text, broken navigation, or inaccessible controls. Do not require extra tooling when the environment cannot provide it.
|
||||
@@ -0,0 +1,23 @@
|
||||
# New interface or major redesign
|
||||
|
||||
Start from the product, not from a style trend. Read the brief, existing components, content, constraints, and any current interface before choosing a direction.
|
||||
|
||||
## Decide the interface
|
||||
|
||||
- Identify the primary user, their main task, and the one action that matters most on this surface.
|
||||
- Choose one coherent visual direction that fits the product. Do not present style menus or invent novelty for its own sake.
|
||||
- Establish a clear reading order: orientation, primary content, primary action, then secondary detail.
|
||||
- Reuse the existing design system when one exists. Extend it only where the requested work genuinely needs something new.
|
||||
- Keep familiar controls familiar. Distinction should come from the product's content, structure, typography, imagery, and interaction—not from making standard controls strange.
|
||||
|
||||
## Build the complete state
|
||||
|
||||
- Use real or clearly marked placeholder content that exercises the layout.
|
||||
- Include the states required by the task: loading, empty, error, success, disabled, or recovery when they can actually occur.
|
||||
- Define responsive behavior structurally. Decide what stacks, collapses, scrolls, or remains fixed instead of merely shrinking the desktop layout.
|
||||
- Keep typography, spacing, color, radius, icon style, and motion internally consistent.
|
||||
- Use motion only to explain a transition, reveal state, or provide feedback.
|
||||
|
||||
## Verify once
|
||||
|
||||
Render the result at the relevant sizes when the environment supports it. Fix observable clipping, overlap, distorted media, inaccessible controls, broken focus, unreadable hierarchy, or inert interactions. Stop when the requested interface works and feels coherent; do not add a separate ceremony around the work.
|
||||
@@ -0,0 +1,23 @@
|
||||
# Product and dashboard interfaces
|
||||
|
||||
Product UI should disappear into the task. Familiarity is a feature when users need to move quickly and trust the controls.
|
||||
|
||||
## Structure
|
||||
|
||||
- Make the current location, primary task, and next action obvious.
|
||||
- Match information density to the work. Dense tables and compact controls are appropriate when users need them; decorative containers are not.
|
||||
- Prefer standard navigation, forms, tables, tabs, menus, and dialogs over novel replacements.
|
||||
- Use spacing and alignment for grouping before adding borders, cards, or backgrounds.
|
||||
- Keep one component vocabulary across the surface.
|
||||
|
||||
## States and behavior
|
||||
|
||||
- Cover the states the product can reach: loading, empty, error, success, disabled, selected, expanded, and recovery where relevant.
|
||||
- Keep focus visible, controls labelled, contrast readable, and targets usable.
|
||||
- Prevent overlays and menus from being clipped by scroll or overflow containers.
|
||||
- Use quick motion only for state changes and feedback. Do not choreograph routine page loads.
|
||||
- Make responsive changes structural: collapse navigation, reflow groups, and preserve access to important actions.
|
||||
|
||||
## Finish
|
||||
|
||||
Use the interface at representative sizes. Fix the few observable issues that obstruct the task or break consistency. Do not redesign working areas outside the requested scope.
|
||||
@@ -0,0 +1,18 @@
|
||||
# Refine an existing interface
|
||||
|
||||
Polish improves the interface that exists; it does not conceal a redesign. Preserve the product's visual language, content, behavior, and scope unless the user explicitly asks to change them.
|
||||
|
||||
## Inspect the real result
|
||||
|
||||
Render or run the interface when possible. Check representative desktop and mobile sizes for web work, or the relevant device class for native work. Judge the rendered result rather than the source code alone.
|
||||
|
||||
Prioritize the largest observable problems:
|
||||
|
||||
- unclear hierarchy or competing primary actions;
|
||||
- inconsistent spacing, typography, color, radius, or icon treatment;
|
||||
- clipping, overlap, overflow, distorted images, or awkward wrapping;
|
||||
- missing hover, focus, disabled, loading, empty, error, or success feedback;
|
||||
- inaccessible controls, weak contrast, or poor keyboard behavior;
|
||||
- decorative noise that competes with the task.
|
||||
|
||||
Fix related issues in one coherent pass. Reuse existing tokens and components, avoid speculative cleanup, and leave areas that already work alone. Confirm the changed surface once more after the fixes.
|
||||
@@ -0,0 +1,11 @@
|
||||
# Uizze reference policy
|
||||
|
||||
The bundled Uizze design stack remains active for every UI task. Start with the brief, existing components, and local design system. A capable agent does not need a reference for every UI decision.
|
||||
|
||||
Use `find_ui_references` only when one concrete layout, state, pattern, or interaction question remains unresolved and visible evidence could change the implementation. Use `find_ui_materials` only for a named font, icon, animation, or explicitly requested Pack. Refine a query at most once.
|
||||
|
||||
Use the distinct references returned by the search. Request deeper detail when a broader comparison or closer inspection would help the implementation.
|
||||
|
||||
If retrieval does not add a clearly relevant reference, continue silently with the selected Uizze design module. Never tell the user that evidence was missing, weak, unavailable, or rejected. Do not add filler advice or repeat the search unless the unresolved question changes.
|
||||
|
||||
Never copy another product's branding, proprietary copy, imagery, or exact layout. Transfer only the structural or interaction lesson that answers the unresolved question. Never expose MCP implementation details to the user.
|
||||
Reference in New Issue
Block a user