
Ui Ux Polish
- 2 installs
- 404 repo stars
- Updated August 5, 2026
- aiskillstore/marketplace
ui-ux-polish is a Claude skill that provides an iterative prompt and methodology for polishing a working web app's UI/UX across desktop and mobile.
About
ui-ux-polish is an iterative UI/UX polishing workflow for web applications that already work and look decent. It supplies an exact prompt run repeatedly, each pass making small compounding visual improvements to spacing, typography, states, and interactions, with desktop and mobile optimized separately. Developers use it to elevate a working app from decent to highly refined.
- Iterative UI/UX polishing prompt and methodology for web apps
- Optimizes desktop and mobile separately across many passes
- Includes the exact polish prompt to run repeatedly
Ui Ux Polish by the numbers
- 2 all-time installs (skills.sh)
- +1 installs in the week ending Jun 23, 2026 (Skillselion tracking)
- Ranked #1,564 of 1,880 Design & UI/UX skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
ui-ux-polish capabilities & compatibility
- Capabilities
- ui design · frontend · design review
- Use cases
- ui design · frontend · web design
What ui-ux-polish says it does
Iterative UI/UX polishing workflow for web applications. The exact prompt and methodology for achieving Stripe-level visual polish through multiple passes.
These really add up after 10 iterations!
npx skills add https://github.com/aiskillstore/marketplace --skill ui-ux-polishAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 2 |
|---|---|
| repo stars | ★ 404 |
| Last updated | August 5, 2026 |
| Repository | aiskillstore/marketplace ↗ |
What it does
Iteratively polish a working web app's UI/UX across desktop and mobile until it is highly refined.
Who is it for?
Developers with a working, decent-looking app who want to elevate it to a highly polished finish.
Skip if: Broken or buggy apps, or apps with fundamentally wrong styling that need a complete overhaul.
When should I use this skill?
When an app already works and looks decent and you want to iteratively improve its look and feel.
What you get
Repeated polish passes compound small improvements in spacing, typography, states, and responsiveness.
- Incrementally polished UI across desktop and mobile
By the numbers
- 10+ recommended iterations
Files
UI/UX Polish — Iterative Enhancement Workflow
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.
---
The Workflow
Overview
1. App already works and looks decent 2. Run the polish prompt 3. Agent makes incremental improvements 4. Repeat many times (10+ iterations) 5. Each pass adds small improvements that compound
Why Multiple Passes Work
- Each time, it tries to make some incremental improvement, even if it's minor
- These really add up after 10 iterations!
- Multiple agents can work on this simultaneously
- Cumulative effect is dramatic
---
THE EXACT PROMPT — UI/UX Polish
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.---
Why This Prompt Works
1. Asks for Agreement
The phrase "don't you agree?" engages the model's reasoning about whether improvements are possible, rather than just executing instructions.
2. Separates Desktop and Mobile
"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.
3. Sets High Standards
References:
- "world class"
- "best practices like those used by Stripe"
- "makes people gasp at how stunning and perfect it is"
These anchors push the model toward higher quality than generic "make it better" instructions.
4. Uses Ultrathink
Extended thinking allows the model to:
- Analyze the current state thoroughly
- Consider multiple improvement options
- Choose the highest-impact changes
- Think through edge cases
---
Best Models for This Task
| Model | Effectiveness |
|---|---|
| Claude Code + Opus 4.5 | Excellent |
| Codex + GPT 5.2 (High/Extra-High reasoning) | Excellent |
| Gemini CLI | Good |
---
Tech Stack Compatibility
This prompt works with:
- Next.js 16 + React 19 + Tailwind 4
- Any modern web framework
- Applications using Framer Motion or similar animation libraries
- Pretty much anything—it's generic enough to adapt
---
Iteration Protocol
Single Agent
# 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 minimalMultiple Agents
You can have more than one agent working on UI/UX polish simultaneously:
- They'll focus on different areas
- Use file reservations to avoid conflicts
- Compound improvements faster
---
When to Use vs. When NOT to Use
USE This Prompt When:
- App works correctly
- Basic styling is in place
- You want to elevate from "decent" to "world-class"
- Ready for iterative refinement
- Want to optimize for both desktop and mobile
DON'T Use This Prompt When:
- App is broken or buggy (fix bugs first)
- Styling is fundamentally wrong (need complete overhaul)
- No basic design system in place
- Starting from scratch
For complete overhauls, use a different approach focused on establishing a design system and component library first.
---
What the Model Typically Improves
Visual Polish
- Spacing and padding consistency
- Typography hierarchy
- Color contrast and accessibility
- Shadow and depth effects
- Border radius consistency
- Hover/focus states
Interaction Design
- Button feedback
- Loading states
- Transitions and animations
- Error state handling
- Empty state design
Mobile Optimization
- Touch target sizes
- Responsive breakpoints
- Mobile-specific navigation
- Gesture support
- Performance on mobile devices
Desktop Optimization
- Keyboard navigation
- Hover states
- Multi-column layouts
- Sidebar navigation
- Power user shortcuts
---
Tracking Progress
After each iteration, you might notice:
- Subtle shadow improvements
- Better spacing rhythm
- More consistent typography
- Smoother animations
- Better responsive behavior
These small changes compound. An app after 10 passes looks dramatically better than after 1 pass.
---
Integration with Beads
For systematic UI/UX work, create beads:
bd create "Polish homepage UI/UX for desktop" -t enhancement -p 2
bd create "Polish homepage UI/UX for mobile" -t enhancement -p 2
bd create "Polish dashboard UI/UX for desktop" -t enhancement -p 2
bd create "Polish dashboard UI/UX for mobile" -t enhancement -p 2This lets agents work on UI/UX polish as part of the normal bead workflow.
---
Complete Prompt Reference
Main Polish Prompt
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.Alternative: General Scrutiny (from agent-swarm-workflow)
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.---
Tips
1. Don't skip iterations — Even when changes seem small, keep going 2. Review changes — Make sure the model isn't breaking things 3. Test on real devices — Desktop browser != mobile experience 4. Consider accessibility — WCAG compliance matters 5. Keep performance in mind — Pretty but slow is bad UX
{
"schema_version": "2.0",
"meta": {
"generated_at": "2026-01-17T03:15:40.264Z",
"slug": "dicklesworthstone-ui-ux-polish",
"source_url": "https://github.com/Dicklesworthstone/agent_flywheel_clawdbot_skills_and_integrations/tree/main/skills/ui-ux-polish",
"source_ref": "main",
"model": "claude",
"analysis_version": "3.0.0",
"source_type": "community",
"content_hash": "4340ec23c453cd2411ae515c24714f6d4642edfbe18a63274b6596325846a475",
"tree_hash": "cfd3ae2db168b1c7b1291d48ff2151fef9814a30c58755c0b16c3c8f01fc6259"
},
"skill": {
"name": "ui-ux-polish",
"description": "Iterative UI/UX polishing workflow for web applications. The exact prompt and methodology for achieving Stripe-level visual polish through multiple passes.",
"summary": "Iterative UI/UX polishing workflow for web applications. The exact prompt and methodology for achiev...",
"icon": "🎨",
"version": "1.0.0",
"author": "Dicklesworthstone",
"license": "MIT",
"category": "design",
"tags": [
"ui-ux",
"design",
"web-apps",
"frontend",
"visual-polish"
],
"supported_tools": [
"claude",
"codex",
"claude-code"
],
"risk_factors": [
"network",
"external_commands"
]
},
"security_audit": {
"risk_level": "safe",
"is_blocked": false,
"safe_to_publish": true,
"summary": "Pure documentation skill containing only text prompts and methodology. No executable code, file access, network calls, or system commands. All 60 static findings are false positives from the scanner misinterpreting text patterns as security issues (e.g., 'ultrathink' flagged as C2, normal prose as cryptographic algorithms, GitHub URLs as network calls).",
"risk_factor_evidence": [
{
"factor": "network",
"evidence": [
{
"file": "skill-report.json",
"line_start": 6,
"line_end": 6
}
]
},
{
"factor": "external_commands",
"evidence": [
{
"file": "SKILL.md",
"line_start": 37,
"line_end": 39
},
{
"file": "SKILL.md",
"line_start": 39,
"line_end": 51
},
{
"file": "SKILL.md",
"line_start": 51,
"line_end": 54
},
{
"file": "SKILL.md",
"line_start": 54,
"line_end": 101
},
{
"file": "SKILL.md",
"line_start": 101,
"line_end": 112
},
{
"file": "SKILL.md",
"line_start": 112,
"line_end": 194
},
{
"file": "SKILL.md",
"line_start": 194,
"line_end": 199
},
{
"file": "SKILL.md",
"line_start": 199,
"line_end": 208
},
{
"file": "SKILL.md",
"line_start": 208,
"line_end": 210
},
{
"file": "SKILL.md",
"line_start": 210,
"line_end": 213
},
{
"file": "SKILL.md",
"line_start": 213,
"line_end": 215
}
]
}
],
"critical_findings": [],
"high_findings": [],
"medium_findings": [],
"low_findings": [],
"dangerous_patterns": [],
"files_scanned": 2,
"total_lines": 405,
"audit_model": "claude",
"audited_at": "2026-01-17T03:15:40.263Z"
},
"content": {
"user_title": "Polish web app UI/UX with iterative enhancement workflow",
"value_statement": "Your web app looks decent but lacks world-class polish. Use this iterative workflow to incrementally enhance UI/UX across desktop and mobile, achieving Stripe-level visual quality through multiple focused passes.",
"seo_keywords": [
"UI UX polish",
"web design enhancement",
"Stripe-level UI",
"iterative design workflow",
"visual polish prompts",
"Claude Code",
"Codex",
"mobile desktop optimization",
"frontend design",
"user interface improvement"
],
"actual_capabilities": [
"Provides exact prompts for UI/UX enhancement",
"Guides iterative improvement process (10+ passes)",
"Separate optimization strategies for desktop and mobile",
"Best practices for visual polish techniques",
"Integration tips with modern tech stacks (Next.js, React, Tailwind)",
"Progress tracking methodology for cumulative improvements"
],
"limitations": [
"Does not modify code directly; provides prompts to guide AI agents",
"Requires existing working app with basic styling already in place",
"Does not fix bugs or broken functionality",
"Cannot establish design systems from scratch"
],
"use_cases": [
{
"target_user": "Frontend developers",
"title": "Elevate existing web apps",
"description": "Transform decent-looking web applications into polished, professional interfaces following industry best practices."
},
{
"target_user": "Product designers",
"title": "Refine visual polish iteratively",
"description": "Apply systematic improvements through multiple passes to achieve high-quality visual presentation."
},
{
"target_user": "AI-assisted development teams",
"title": "Guide AI agents for UI work",
"description": "Provide AI agents with effective prompts to make meaningful UI/UX enhancements automatically."
}
],
"prompt_templates": [
{
"title": "Main Polish Prompt",
"scenario": "Iterative UI/UX enhancement",
"prompt": "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."
},
{
"title": "General Scrutiny",
"scenario": "Application-wide review",
"prompt": "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."
},
{
"title": "Mobile Optimization",
"scenario": "Mobile-specific improvements",
"prompt": "Focus specifically on mobile UI/UX optimization. Consider touch target sizes, responsive breakpoints, mobile-specific navigation, gesture support, and mobile performance. What changes would make this app exceptional on mobile devices?"
},
{
"title": "Desktop Optimization",
"scenario": "Desktop-specific improvements",
"prompt": "Focus specifically on desktop UI/UX optimization. Consider keyboard navigation, hover states, multi-column layouts, sidebar navigation, and power user shortcuts. What changes would make this app exceptional on desktop?"
}
],
"output_examples": [
{
"input": "Apply UI/UX polish to my dashboard application",
"output": [
"Improved shadow and depth effects for better visual hierarchy",
"Consistent border radius and spacing across components",
"Enhanced hover and focus states for interactive elements",
"Optimized typography scale for readability",
"Better loading and empty state designs",
"Touch-friendly button sizes for mobile devices"
]
},
{
"input": "Make my landing page look more premium and professional",
"output": [
"Refined color palette with better contrast ratios",
"Added subtle micro-animations for engagement",
"Improved hero section visual impact",
"Streamlined navigation with clearer hierarchy",
"Enhanced call-to-action button styling",
"Consistent spacing system across sections"
]
}
],
"best_practices": [
"Run multiple iterations (10+) for cumulative improvements rather than expecting dramatic changes in a single pass",
"Separate desktop and mobile optimization to avoid compromises that work poorly on both platforms",
"Review AI-generated changes carefully to ensure no regressions in functionality"
],
"anti_patterns": [
"Using this workflow on broken or buggy apps instead of fixing issues first",
"Applying polish prompts when no basic styling or design system exists",
"Skipping iterations when changes seem minor; small improvements compound significantly"
],
"faq": [
{
"question": "Which AI models work best with this skill?",
"answer": "Claude Code with Opus 4.5 and Codex with GPT 5.2 (High/Extra-High reasoning) work excellently. Gemini CLI also produces good results."
},
{
"question": "How many iterations are recommended?",
"answer": "Plan for 10 or more iterations. Each pass adds incremental improvements that compound dramatically over time."
},
{
"question": "Can multiple agents work on polish simultaneously?",
"answer": "Yes, multiple agents can work together. Use file reservations to avoid conflicts and focus on different areas of the application."
},
{
"question": "What data does this skill access?",
"answer": "This is a prompt-only skill that provides text guidance. It does not access files, networks, or execute any code."
},
{
"question": "When should I not use this workflow?",
"answer": "Do not use on broken apps, when starting from scratch, or when no basic styling exists. This is for refining working applications."
},
{
"question": "How does this compare to complete design overhauls?",
"answer": "This workflow enhances already-working apps incrementally. Complete overhauls require establishing design systems first, which this does not do."
}
]
},
"file_structure": [
{
"name": "SKILL.md",
"type": "file",
"path": "SKILL.md",
"lines": 226
}
]
}
Related skills
FAQ
When should you not use ui-ux-polish?
Do not use it when the app is broken or buggy, styling is fundamentally wrong, or there is no basic design system in place.
Why run the prompt multiple times?
Each pass makes small incremental improvements that compound, so an app after 10 passes looks dramatically better than after 1.