ui-polish-review
UI Polish Review
Overview
A structured visual design audit methodology based on Refactoring UI by Adam Wathan and Steve Schoger. Guides you through 7 sequential phases to systematically evaluate and improve the visual quality of any web or application interface, transforming rough or inconsistent designs into polished, professional ones.
When to Use
- Before launching a product or feature to production
- When a design "looks off" but you cannot pinpoint why
- During design reviews or code reviews that include UI changes
- When elevating a functional prototype into a polished product
- After implementing a design and wanting to verify visual quality against best practices
- When onboarding a new team and establishing design standards
When NOT to Use
- As a substitute for usability testing (use the ux-usability-review skill for that)
- For branding or marketing strategy decisions
More from ahmedhamadto/software-forge
web-app-security-audit
Use when testing a web application for security vulnerabilities, before deployment or during security review — guides through a structured 10-phase penetration testing methodology covering mapping, authentication, session management, access controls, injection, logic flaws, and server configuration.
33ux-usability-review
Use when reviewing any interface for usability — walks through Krug's principles from Don't Make Me Think covering cognitive load, scanning, navigation, homepage clarity, mobile usability, accessibility, and the goodwill reservoir.
27voice-agent-prompt
Engineer system prompts for LiveKit voice agents with multilingual support. Use when creating or optimizing AI agent conversation flows.
15systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
12subagent-driven-development
Use when executing implementation plans with independent tasks in the current session
11verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
11