When to Use: This is for when your site/app already works and looks decent and you want to improve it. There's a different approach when it looks bad and needs a complete overhaul.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionui-ux-polishExecute the skills CLI command in your project's root directory to begin installation:
Fetches ui-ux-polish from dicklesworthstone/agent_flywheel_clawdbot_skills_and_integrations and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate ui-ux-polish. Access via /ui-ux-polish in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
1
total installs
1
this week
62
GitHub stars
0
upvotes
Run in your terminal
1
installs
1
this week
62
stars
When to Use: This is for when your site/app already works and looks decent and you want to improve it. There's a different approach when it looks bad and needs a complete overhaul.
Key Insight: Something about asking for agreement from the model ("don't you agree?") somehow motivates it to polish things up better. Also, instructing it to separately think through desktop vs mobile leads to much better outcomes.
This prompt is used so frequently it's worth putting on a Stream Deck button:
I still think there are strong opportunities to enhance the UI/UX look and feel and to make everything work better and be more intuitive, user-friendly, visually appealing, polished, slick, and world class in terms of following UI/UX best practices like those used by Stripe, don't you agree? And I want you to carefully consider desktop UI/UX and mobile UI/UX separately while doing this and hyper-optimize for both separately to play to the specifics of each modality. I'm looking for true world-class visual appeal, polish, slickness, etc. that makes people gasp at how stunning and perfect it is in every way. Use ultrathink.
The phrase "don't you agree?" engages the model's reasoning about whether improvements are possible, rather than just executing instructions.
"carefully consider desktop UI/UX and mobile UI/UX separately...
hyper-optimize for both separately to play to the specifics of each modality"
This prevents the model from making compromises that work "okay" on both but great on neither.
References:
These anchors push the model toward higher quality than generic "make it better" instructions.
Extended thinking allows the model to:
| Model | Effectiveness |
|---|---|
| Claude Code + Opus 4.5 | Excellent |
| Codex + GPT 5.2 (High/Extra-High reasoning) | Excellent |
| Gemini CLI | Good |
This prompt works with:
# First pass
[Run the UI/UX polish prompt]
# Review changes
[Agent makes improvements]
# Second pass
[Run the same prompt again]
# Repeat 10+ times until changes become minimal
You can have more than one agent working on UI/UX polish simultaneously:
For complete overhauls, use a different approach focused on establishing a design system and component library first.
After each iteration, you might notice:
These small changes compound. An app after 10 passes looks dramatically better than after 1 pass.
For systematic UI/UX work, create beads:
br create "Polish homepage UI/UX for desktop" -t enhancement -p 2
br create "Polish homepage UI/UX for mobile" -t enhancement -p 2
br create "Polish dashboard UI/UX for desktop" -t enhancement -p 2
br create "Polish dashboard UI/UX for mobile" -t enhancement -p 2
This lets agents work on UI/UX polish as part of the normal bead workflow.
I still think there are strong opportunities to enhance the UI/UX look and feel and to make everything work better and be more intuitive, user-friendly, visually appealing, polished, slick, and world class in terms of following UI/UX best practices like those used by Stripe, don't you agree? And I want you to carefully consider desktop UI/UX and mobile UI/UX separately while doing this and hyper-optimize for both separately to play to the specifics of each modality. I'm looking for true world-class visual appeal, polish, slickness, etc. that makes people gasp at how stunning and perfect it is in every way. Use ultrathink.
Great, now I want you to super carefully scrutinize every aspect of the application workflow and implementation and look for things that just seem sub-optimal or even wrong/mistaken to you, things that could very obviously be improved from a user-friendliness and intuitiveness standpoint, places where our UI/UX could be improved and polished to be slicker, more visually appealing, and more premium feeling and just ultra high quality, like Stripe-level apps.
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
anthropics/claude-code
mblode/agent-skills
github/awesome-copilot
sickn33/antigravity-awesome-skills
leonxlnx/taste-skill
erichowens/some_claude_skills
ui-ux-polish has been reliable in day-to-day use. Documentation quality is above average for community skills.
I recommend ui-ux-polish for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Keeps context tight: ui-ux-polish is the kind of skill you can hand to a new teammate without a long onboarding doc.
Solid pick for teams standardizing on skills: ui-ux-polish is focused, and the summary matches what you get after install.
ui-ux-polish is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
ui-ux-polish has been reliable in day-to-day use. Documentation quality is above average for community skills.
ui-ux-polish is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Useful defaults in ui-ux-polish — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Registry listing for ui-ux-polish matched our evaluation — installs cleanly and behaves as described in the markdown.
We added ui-ux-polish from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
showing 1-10 of 46