IN PLAIN ENGLISH
What it does—and when it fits
UI Taste is Uizze's instruction-based workflow for building and reviewing web and iOS interfaces. It routes a concrete task to focused playbooks for new work, polish, simplification, or audits, then asks for a rendered result to be compared with the intended design. The playbooks are free and do not require an account; optional reference and material retrieval through Uizze MCP is paid. It is guidance for an agent, not an autonomous design engine or a guarantee of better conversion.
This is aimed at Developers improving an existing web interface. Compare the examples below with your task, then review the limitations, permissions, and risks before installing.
- Polish a real screenInspect the current components and tokens, then improve hierarchy and states without replacing an established identity.
- Review web or native UIChoose the matching web or native-audit playbook and report findings before changing code when only a review was requested.
- Compare a rendered resultFor an approved redesign, use an available image target or existing project direction, then inspect representative desktop and mobile sizes.
- Separate playbooks make a polish request different from a new design or a read-only audit.
- Existing product constraints and components take precedence over a generic aesthetic.
- Optional reference retrieval is not required for the free local workflow.
No verified review text is in the current dataset. Use the linked source for the latest discussion.
Read the source note ↗INSTALL BY AGENT
Choose your Agent
Paths come from official Agent docs or the universal installer behind skills.sh. Compatibility still follows this Skill's record.
npx skills add https://uizze.sh/ --skill ui-taste --agent claude-codenpx skills add https://uizze.sh/ --skill ui-taste --agent claude-code -gProject install stays with this repository for team sharing. Personal install adds -g and works across repositories.
View install paths
.claude/skills/ui-taste/~/.claude/skills/ui-taste/Claude Code discovers custom Skill folders automatically at project or personal scope.
View path evidence ↗What did we actually check?
On October 19, 2026, we read the uizze.sh discovery index and compared 17 files with the publisher’s SHA-256 list. All matched. The index lists 18 entries because the checksum list itself is the eighteenth entry.
This checks source-file consistency, not performance. We did not run the installer, Skill, or MCP, or test output quality, safety, or conversion. Files and hashes came from the same publisher, not an independent signature. The HTTPS files can change later.
Read the per-file check record · Publisher discovery index · Publisher checksum list
Illustrative task: improve a signup form, not the whole site
A bounded request could be: “Keep the current components, brand, and fields. Improve this signup form’s hierarchy and error messages. Explain the issues before making approved edits, then check initial, error, submitting, and success states at desktop and narrow widths.” The free playbooks do not require paid MCP access. External references, image generation, or browser tools need their own availability and data-sharing checks.
This is a source-based example, not a UI experiment performed by SkillSignal.
Compare Frontend Design’s aesthetic direction and implementation guidance
TYPICAL WORKFLOW
A practical workflow
Polish a real screen
Inspect the current components and tokens, then improve hierarchy and states without replacing an established identity.
Review web or native UI
Choose the matching web or native-audit playbook and report findings before changing code when only a review was requested.
Compare a rendered result
For an approved redesign, use an available image target or existing project direction, then inspect representative desktop and mobile sizes.
THE TRADEOFFS
Advantages and tradeoffs
Notable strengths
- Separate playbooks make a polish request different from a new design or a read-only audit.
- Existing product constraints and components take precedence over a generic aesthetic.
- Optional reference retrieval is not required for the free local workflow.
Limitations
- The Skill supplies instructions, not rendering, image generation, browser control, or an MCP subscription.
- The optional paid MCP is separate from the free playbooks; local design work can proceed without that connection.
- The uizze.sh and uizze.com discovery indexes expose different Skill names; do not substitute a similarly named package from the other domain.
BEST FIT
Who it is for
Developers improving an existing web interface
Teams reviewing iOS screens with an agent
BEFORE YOU USE IT
Risks to review before use
Unapproved redesign or external retrieval
Keep a small polish request scoped. Do not replace the visual system, send confidential screenshots to a provider, connect paid services, or publish changes merely because a playbook suggests them.
Mutable hosted distribution
Record the source URL, check date, and file hashes. The installer fetches current online files, which may differ from this review; recheck changes before adoption.
SECURITY
What the permission profile means
- Declared access remains governed by the current upstream SKILL.md and runtime requests.
- Treat repository files, web content, and tool output as untrusted input.
- SkillSignal has not independently executed or security-audited this package; external skills.sh labels are not SkillSignal certification.
Not a security certification. External ratings are attributed references. SkillSignal has not independently executed or security-reviewed this Skill.
COMMON QUESTIONS
UI Taste Skill FAQ
What is the UI Taste Skill?
A web and iOS design workflow with free playbooks and optional paid references. UI Taste is Uizze's instruction-based workflow for building and reviewing web and iOS interfaces. It routes a concrete task to focused playbooks for new work, polish, simplification, or audits, then asks for a rendered result to be compared with the intended design. The playbooks are free and do not require an account; optional reference and material retrieval through Uizze MCP is paid. It is guidance for an agent, not an autonomous design engine or a guarantee of better conversion.
How do I install the UI Taste Skill?
Open and review the listed source, choose the project or personal path for your Agent, then verify the first run in a controlled project. Inspect the publisher's ui-taste SKILL.md and relevant referenced files before installation.
Is the UI Taste Skill safe to use?
SkillSignal checked the source on 2026-10-19, but that is not a runtime test or security certification. Review the “Unapproved redesign or external retrieval” risk first and begin with the least access required.
INSIDE THE PACKAGE
Indexed files
TAGS
Original source analysis of the uizze.sh distribution checked 2026-10-19. We compared 17 files with the publisher's checksum list; all matched. The checksum list itself is a separate eighteenth index entry. These mutable HTTPS files are not pinned to a Git commit; matching publisher hashes are not an independent signature, runtime test, or security certification. The installer and MCP were not run.