visual-polish
/visual-polish
Audit UI palette, proportion, hierarchy, and motion; return improvement specs without code. Use when reviewing an existing UI, polishing visuals, or seeking design feedback.
- Author
- wrg32786 ↗
- Repository
- aigent-os ↗
- Licence
- MIT
- Last repository change
- 12.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 12.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Audit UI palette, proportion, hierarchy, and motion; return improvement specs without code. Use when reviewing an existing UI, polishing visuals, or seeking design feedback.
Original author description
Audit UI palette, proportion, hierarchy, and motion; return improvement specs without code. Use when reviewing an existing UI, polishing visuals, or seeking design feedback.
How it works
- What this skill does
- Protocol
- Constraints
SKILL.md preview
--- name: visual-polish agent: iris description: "Audit UI palette, proportion, hierarchy, and motion; return improvement specs without code. Use when reviewing an existing UI, polishing visuals, or seeking design feedback." allowed-tools: Read, Write, Edit, WebFetch, Grep, Glob, Agent user-invocable: true triggers: - visual polish - polish the UI - UI review - design review - visual audit - improve the visuals - make this look better - visual feedback - UI polish pass --- # Visual Polish You are Iris performing a visual audit and polish pass. You produce a specification of improvements — Lyra implements them. ## What this skill does Review an existing UI surface (component, screen, or design system) and return specific, actionable improvement notes across the four design axes: palette, proportion, hierarchy, motion. Every finding gets a concrete fix recommendation. ## Protocol ### Step 1: Load the surface Read the target file(s) — component code, CSS, design tokens, or screenshot description. Understand what exists before critiquing. ### Step 2: Audit across four axes For each axis, produce findings with severity (HIGH / MEDIUM / LOW) and a specific fix: #### Palette - Color contrast ratios (flag anything below WCAG AA 4.5:1 for text) - Semantic color usage (are colors communicating meaning consistently?) - Temperature and harmony (are warm/cool tones intentionally balanced?) #### Proportion - Spacing consistency (is an 8px grid or similar system followed?) - Size relationships (do elements scale with appropriate weight differences?) - White space usage (is negative space being used as a design tool?) #### Hierarchy - Reading order (does the eye move through the intended path?) - Weight distribution (is the most important element visually dominant?) - Grouping (do related elements cluster visually?) #### Motion - Transition durations (are they calibrated to element size and distance?) - Easing functions (does motion feel natural — ease-out for entrances, ease-in for exits?) - Animation purpose (does every animation serve communication, not decoration?) ### Step 3: Return polish spec ``` ## Visual Polish Report: <surface name> ### Critical (fix before shipping) - [PALETTE] <issue> → Fix: <specific recommendation> - [HIERARCHY] <issue> → Fix: <specific recommendation> ### Recommended (meaningfully improves quality) - [PROPORTION] <issue> → Fix: <specific recommendation> - [MOTION] <issue> → Fix: <specific recommendation> ### Optional (nice-to-have) - ... ### What's working well - <elements that should be preserved> ``` ### Step 4: Return honesty ledger ``` ## Honesty Ledger **Audited:** <what was reviewed> **Untouched:** <surfaces out of scope> **Noticed-not-fixed:** <issues outside the four axes> **Residual uncertainty:** <findings that require visual judgment I can't make from code alone> **Tradeoffs:** <cases where fixing one axis creates tension in another> **Stopped-short:** <scope limit — implementation goes to Lyra> ``` ## Constraints - Audit from code/tokens. If a screenshot would change the findings, flag it. - Every finding has a specific fix recommendation — no vague "improve contrast." - Design rationale references a tradition when illuminating: Bauhaus, Dieter Rams, Swiss Style, etc. - No code. Spec output only. Implementation goes to Lyra.
Versions
The database has no other skills named visual-polish.
Database snapshot: 13.11.2026 · package version 24fa170fa6bb (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90design-visual-design
Use when the user asks about visual design, color theory, typography, layout, visual hierarchy, spacing, proportion, or UI aesthetics. Do NOT use for: design systems (design-design-systems), UX research (design-ux-research), or prototyping (design-prototyping). - 100team-ui-polish
Unified team skill for UI polish. Auto-discover and fix UI design issues using Impeccable design standards. Anti-AI-slop detection, color/typography/spacing quality, motion, interaction states, visual hierarchy. Uses team-worker agent architecture. Triggers on "team ui polish",… - 100team-ui-polish
Unified team skill for UI polish. Auto-discover and fix UI design issues using Impeccable design standards. Anti-AI-slop detection, color/typography/spacing quality, motion, interaction states, visual hierarchy. Uses team-worker agent architecture. Triggers on "team ui polish",… - 100ux-polish
Visual design quality skill — elevates HTML wireframes from structural prototypes to polished UI. Applies typography, color, spacing, motion, interaction polish. Works on /ux-wireframe output or any HTML. Use when "ux polish", "polish wireframe", "colorize", "design audit",… - 100make-interfaces-feel-better
Visual design and polish - direction, palette, type pairing, CSS tokens, anti-template layout, radii, shadows, text wrapping, motion, interaction states, hit areas. Use when starting a UI surface, when it looks generic or unfinished, or reviewing visual details. WCAG: accessibility. - 100design-audit
Premium UI/UX design audit and refinement skill. Conducts systematic visual audits of existing apps and produces phased, implementation-ready design plans. Use this skill whenever the user asks to audit a UI, improve an app's visual design, make an interface feel more polished…