Add Uizze — UI design that stands out

[samuelbushi]

Adds Uizze — UI design that stands out, matching the Uizze ChatGPT listing and approved subtitle update's display name, developer name, logo and three starter prompts.

The package includes the complete current anti-ui-slop skill, its focused playbooks and licensing notices, and native Streamable HTTP MCP configuration for https://uizze.com/mcp. The free skill works without an account. Optional paid MCP access uses the host's authentication flow and exposes find_ui_references and find_ui_materials.

The finish gate is performed through the skill and local rendering tools. No retired preview or hosted-review endpoint is included. No credentials, runtime wrappers or private assets are bundled.

• Canonical package: https://github.com/uizze/uizze/tree/main/plugins/cursor-agent
• Product and setup: https://uizze.com/docs
• Privacy: https://uizze.com/privacy
• Support: https://uizze.com/contact

Validation: official Cursor plugin and marketplace schemas; Agent Plugins manifest and MCP schemas; complete canonical skill files and checksums. Authenticated Cursor end-to-end use remains to be verified. This updates the existing submission rather than creating a duplicate application.

---

Note

Low Risk
Additive marketplace plugin and bundled markdown skill only; optional external MCP follows the same pattern as other integrations with no changes to core repo runtime.

Overview
Adds the Uizze plugin to the Cursor marketplace and root plugin index, with a new uizze/ package at version 1.3.1.

The package ships the anti-ui-slop agent skill (router in SKILL.md, eight workflow playbooks, reference policy, and Apache-2.0 / third-party attribution files with checksums). Cursor manifests point skills at ./skills/anti-ui-slop/. mcp.json registers optional Streamable HTTP MCP at https://uizze.com/mcp for find_ui_references and find_ui_materials; the skill is documented to work without MCP or credentials.

Also updates README.md with a Uizze row (Developer Tools) and trims trailing blank lines in marketplace.json.

^{Reviewed by Cursor Bugbot for commit 87fce63. Bugbot is set up for automated code reviews on this repo. Configure here.}

[samuelbushi]

Correction to the earlier manifest note: the preview claim and version-specific metadata are retired. The current UIZZE entry points to the free local Skill, npx skills add https://uizze.com --skill anti-ui-slop, and optional authenticated MCP access at https://uizze.com/mcp. Canonical source: https://github.com/uizze/uizze.

[samuelbushi]

Fresh verification: the canonical uizze/uizze Skill is version 1.2.11, its domain-backed copy matches the GitHub source byte-for-byte, and the catalogue-required sections are live at https://uizze.com/.well-known/agent-skills/anti-ui-slop/SKILL.md. The plugin source and free Skill remain on the canonical repository.

[samuelbushi]

Correction to the earlier verification: the install path remains npx skills add https://uizze.com --skill anti-ui-slop; the version-specific directory metric and preview wording are not current public claims. Optional authenticated MCP access is https://uizze.com/mcp. Canonical source: https://github.com/uizze/uizze.

[samuelbushi]

Correction to the earlier conflict update: the anonymous preview claim is retired. The current entry separates the free local Skill, npx skills add https://uizze.com --skill anti-ui-slop, from optional authenticated MCP access at https://uizze.com/mcp. Canonical source: https://github.com/uizze/uizze.

[samuelbushi]

Refreshed the existing submission in merge commit 3067bd4. It now includes current Cursor main, points the plugin homepage to https://uizze.com, and removes the retired /ai-ui-slop and /mcp/preview routes from the bundled docs and skill. Marketplace and plugin manifests parse, and the PR-only diff remains limited to the UIZZE plugin.

[samuelbushi]

Hi Cursor team, I maintain Uizze. The current submission docs direct publishers to cursor.com/marketplace/publish. Should this existing PR continue through review here, or should we carry it over to that portal? We want to keep one submission, not create a duplicate.

One eligibility question before applying: the skill/plugin is free, while the optional hosted MCP service requires a Uizze subscription. Does that model fit section 3.1 of the Publisher Terms, or is a free-only package required? The PR description links the current package and setup docs. Thanks.

[samuelbushi]

Hi Cursor team, following up on the September 14 question: should we continue this submission here or use the publisher portal? The skill is free; hosted MCP access requires a subscription. Please let us know whether that model is eligible and if you need anything else from us to review it. Thanks!

[samuelbushi]

Updated this existing submission—not a second app or portal submission—to head 87fce63e220ff01247916ed06095ef62e4531f46 with the complete Uizze 1.3.1 Skill pinned to released source commit 4a0224f578f65a87f328e9c533b3d8bf1023c1f7. Both manifests are version 1.3.1; all 16 skill files match the reviewed release byte-for-byte, including eight playbooks, LICENSE/NOTICE/MODIFICATIONS, immutable intermediate provenance and checksum records. The still-unknown original iOS source revision is explicitly retained, not claimed resolved.

Executed the repository’s actual node scripts/validate-plugins.mjs with its workflow dependencies: all plugins validated successfully. The actual complete carrier also passes all 15 checksum records and 13 relative support links. No MCP package/token/paid authentication was executed. A genuine native Cursor inspection reached the signed-out login requirement; this is not a claim of native installation, hosted CI authorization, or acceptance.

The earlier review-route and Publisher Terms section 3.1 eligibility question remains unanswered: the Skill is free; the optional authenticated MCP provides exactly find_ui_references and find_ui_materials, while the finish gate is the agent/Skill local workflow. Please confirm whether this existing PR should continue here or use the supported publisher route and whether the free-Skill/optional-paid-MCP model is eligible. We have not created another application, accepted publisher terms, or granted new OAuth scopes.