Add a UI finish gate to code quality workflows

[samuelbushi]

Summary

Adds one concrete UI finish-gate practice to Code Quality & Review. It tells vibe coders to compare agent-built interfaces with real product references and reject output whose hierarchy, density, responsive behavior, states, or copy remain generic.

This is a free, actionable workflow contribution rather than a hosted-MCP listing or naked product drop.

Type of Change

• New tool/resource
• Update existing entry
• Fix broken link
• Improve documentation
• Other (please describe)

Checklist

• I have read the CONTRIBUTING guidelines
• Tool/resource follows the awesome list format
• Links are working and tested
• Entry includes the practice, value, and source in the existing table format
• No promotional/marketing language (focus on utility)
• Existing section order is maintained

Validation

• npx --yes awesome-lint — passes
• git diff --check — passes
• Full repository link check verifies the new UIZZE URL; it still reports four unrelated links already dead on main

Additional Context

This replaces the broader hosted-MCP scope question in #45 with a smaller, workflow-first contribution. Disclosure: I help maintain UIZZE, the linked public reference workflow.