Ui Ux Polish
CheckedHelps with UI components, UX design as part of agent workflows workflows.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add oakoss/agent-skills --skill ui-ux-polish -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
oakoss
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned oakoss/agent-skills at 85e3a3919d.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 85e3a3919d
- Manifest
- skills/ui-ux-polish/SKILL.md
- Scanned
- 5 files, 839 lines
About this skill
What it does
This skill, Ui Ux Polish, iteratively enhances working web applications to improve their visual quality and user experience. It focuses on refining existing designs, optimizing for both desktop and mobile, applying specific design patterns (like glassmorphism or neumorphism), and ensuring accessibility standards are met. The process emphasizes small, incremental improvements through repeated refinement cycles.
When to use it
- The application functions correctly but requires visual improvement beyond basic styling.
- You want to apply a particular design pattern like glassmorphism, neumorphism, or bento grids.
- You need to audit and improve the accessibility of an existing web application.
- You are looking for iterative refinement rather than a complete redesign.
Key capabilities
- Iterative Polish: Repeatedly applying small refinements to achieve significant visual improvements.
- Desktop/Mobile Optimization: Separately optimizing designs for desktop and mobile experiences.
- Design Pattern Application: Implementing specific design patterns such as glassmorphism, neumorphism, and bento grids.
- Accessibility Auditing & Improvement: Ensuring compliance with WCAG 2.2 AA accessibility standards (contrast ratios, target sizes, focus visibility).
- Respecting User Preferences: Adhering to the user's
prefers-reduced-motionsetting for animations. - Semantic HTML Implementation: Utilizing proper HTML structure and elements for improved accessibility and SEO.
Example prompts
- "Polish this web application with a glassmorphism design."
- "Optimize this page for mobile viewing, focusing on spacing rhythm."
- "Audit the accessibility of this component and suggest improvements based on WCAG 2.2 AA guidelines."
- "Apply neumorphic styling to these buttons, ensuring sufficient contrast for accessibility."
Tips & gotchas
- Fix bugs first: This skill is intended for visual refinement after functional issues are resolved.
- Iterate frequently: Run the polish prompt multiple times (10+) to allow small improvements to compound.
- Separate desktop and mobile: Treat each platform as a distinct modality when optimizing designs.