Polish
Polish micro-details that make UI feel better — optical alignment, tabular nums, text-wrap, interruptible transitions, press feedback, hit areas, no transition:all. Use when building/reviewing UI polish, "feels off", "rapihin detail", hover/press feedback, or after anti-slop-design. Structural layout, radius language, and WCAG conformance belong to other owners.
Install
/plugin marketplace add sukirman1901/frontend-expertThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add sukirman1901/frontend-expert --skill polishgit clone --depth 1 https://github.com/sukirman1901/frontend-expert.git /tmp/frontend-expert
mkdir -p ~/.claude/skills
cp -r /tmp/frontend-expert/skills/polish ~/.claude/skills/polishPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Polish ## Overview After tokens, structure, and anti-slop, apply micro-craft so the UI feels right in the rendered surface. Numeric recipes here are heuristics unless a standard or project token owns them. ## When to use - Finishing `/ui` builds (after `anti-slop-design`) - `/polish` / “rapihin detail” / “feels off” - Hover, press, enter/exit, icon-swap micro-interactions ## When to skip - Structural grid/spacing/hierarchy → `design-foundations` - Comparing rendered directions / stressing all states → `prototype` - Nested radius / elevation language → `design-surfaces` - Type roles, wrapping, truncation → `design-typography` - Conformance (contrast, names, keyboard) → `accessibility` - Motion systems / named families → `motion` - Copy-only / “tulisan AI” / empty-state wording → `content-design` - “Rapikan kode” / generated implementation → `anti-slop-code` - Backend-only edits with no rendered UI change ## MUST | Rule | Detail | |------|--------| | **Rendered proof** | Judge wrapping, alignment, press, and radius from the rendered UI, not source alone | | **Tokens first** | Use `--radius`, spacing, and type tokens; do not invent one-off values when a token exists | | **Classify recipes** | Label `0.96`, stagger ms, and similar numbers as heuristics | | **Cheapest valid fix** | Delete decoration → native CSS → reuse project tokens → then add abstraction | | **Mobile craft** | Full-width primary CTA <768; safe-area on sticky chrome; thumb-reachable actions |
Details
- Skill name
polish- Repository
- sukirman1901/frontend-expert
- Path
skills/polish/SKILL.md- License
- MIT
- Repo updated
- 5 November 2026
FAQ
What does the Polish skill do?
Polish micro-details that make UI feel better — optical alignment, tabular nums, text-wrap, interruptible transitions, press feedback, hit areas, no transition:all. Use when building/reviewing UI polish, "feels off", "rapihin detail", hover/press feedback, or after anti-slop-design. Structural layout, radius language, and WCAG conformance belong to other owners.
How do I install the Polish skill?
Claude Code plugin: /plugin marketplace add sukirman1901/frontend-expert. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Polish popular?
It lives in sukirman1901/frontend-expert, which has 9 GitHub stars and 1 forks.
Related skills
Accessibility
9sukirman1901/frontend-expert
Enforce WCAG 2.2 AA by default (keyboard, ARIA, focus, contrast, semantics, target size, dragging alternatives, accessible authentication). Use for accessibility work, pre-ship UI checks, and as a light pass on every UI build or design review — including "a11y", "keyboard", "screen reader", or shipping user-facing changes.
Anti Slop Code
9sukirman1901/frontend-expert
Detect and fix AI-generated frontend implementation slop: isolated helpers that ignore other modules, needless useEffect, type lies, empty wrappers, and boilerplate error handling that misses field edge cases. Trigger for “kode terasa AI”, “rapikan kode”, “dampak ke modul lain”, “edge case”, “error handling generik”, “too many useEffect”, or “over-engineered”. Visual slop stays on anti-slop-design; copy stays on content-design.
Anti Slop Design
9sukirman1901/frontend-expert
Detect and fix AI aesthetic anti-patterns (purple/indigo defaults, gradients, rounded-2xl everywhere, generic heroes, Lorem ipsum, shadow-heavy cards). Use whenever building, restyling, or reviewing visual UI quality — including "terlalu generik", "AI slop", "rapihin UI", or design audit requests — without requiring /design.
Prototype
9sukirman1901/frontend-expert
Render 2–3 distinct UI directions side by side and stress-test component states (loading, error, empty, disabled, overflow) before committing to one production layout. Trigger for “prototype”, “varian”, “side-by-side”, “bandingkan arah”, “tunjukkan 2 opsi”, or “cek semua state”. Text-only axes stay on design-direction; frame-by-frame motion is not this skill.
Performance
9sukirman1901/frontend-expert
Optimize frontend Core Web Vitals (LCP, INP, CLS) and loading/rendering/network. Use when the UI feels slow, images/fonts/bundles need work, or during design audits that touch performance — phrases like "lemot", "optimize", "LCP", or "Core Web Vitals" without requiring a slash command.
Responsive
9sukirman1901/frontend-expert
Mobile-first responsive UI for all devices (320–1440+): no horizontal scroll, 44px tap targets, drawer nav, full-width primary buttons on phone, adaptive tables/forms. REQUIRED on every user-facing page/layout build — including "mobile", "responsive", "tablet", burger menu, or /ui /polish. Report Responsive in Conventions check.
Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.