component-polish — for Claude Code component-polish, claude-code-utils, community, for Claude Code, ide skills, **Disabled states:**, **Loading states:**, Component, Polish, components

v1.0.0

À propos de ce Skill

Scenario recommande : Ideal for AI agents that need polish components to production quality. run a full pass or target a specific area. Resume localise : # Component Polish Polish components to production quality. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

Fonctionnalités

Polish components to production quality. Run a full pass or target a specific area.
/component-polish — full pass (states + interactions + polish)
/component-polish states — interactive states only (hover, focus, active, disabled, loading)
/component-polish interactions — micro-interactions only (animations, transitions, entrance effects)
Parse the argument and run the specified area. If no argument, run all three in order.

# Core Topics

cbemister cbemister
[0]
[0]
Updated: 3/24/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 10/11

This page remains useful for teams, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution Quality floor passed for review
Review Score
10/11
Quality Score
70
Canonical Locale
en
Detected Body Locale
en

Scenario recommande : Ideal for AI agents that need polish components to production quality. run a full pass or target a specific area. Resume localise : # Component Polish Polish components to production quality. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

Pourquoi utiliser cette compétence

Recommandation : component-polish helps agents polish components to production quality. run a full pass or target a specific area. Component Polish Polish components to production quality. This AI agent skill supports

Meilleur pour

Scenario recommande : Ideal for AI agents that need polish components to production quality. run a full pass or target a specific area.

Cas d'utilisation exploitables for component-polish

Cas d'usage : Applying Polish components to production quality. Run a full pass or target a specific area
Cas d'usage : Applying /component-polish — full pass (states + interactions + polish)
Cas d'usage : Applying /component-polish states — interactive states only (hover, focus, active, disabled, loading)

! Sécurité et Limitations

  • Limitation : /component-polish states — interactive states only (hover, focus, active, disabled, loading)
  • Limitation : /component-polish interactions — micro-interactions only (animations, transitions, entrance effects)
  • Limitation : Requires repository-specific context from the skill documentation

Why this page is reference-only

  • - Current locale does not satisfy the locale-governance contract.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is component-polish?

Scenario recommande : Ideal for AI agents that need polish components to production quality. run a full pass or target a specific area. Resume localise : # Component Polish Polish components to production quality. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

How do I install component-polish?

Run the command: npx killer-skills add cbemister/claude-code-utils/component-polish. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for component-polish?

Key use cases include: Cas d'usage : Applying Polish components to production quality. Run a full pass or target a specific area, Cas d'usage : Applying /component-polish — full pass (states + interactions + polish), Cas d'usage : Applying /component-polish states — interactive states only (hover, focus, active, disabled, loading).

Which IDEs are compatible with component-polish?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for component-polish?

Limitation : /component-polish states — interactive states only (hover, focus, active, disabled, loading). Limitation : /component-polish interactions — micro-interactions only (animations, transitions, entrance effects). Limitation : Requires repository-specific context from the skill documentation.

How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add cbemister/claude-code-utils/component-polish. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use component-polish immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

component-polish

# Component Polish Polish components to production quality. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows. Polish components to

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

Component Polish

Polish components to production quality. Run a full pass or target a specific area.

Usage

/component-polish              — full pass (states + interactions + polish)
/component-polish states       — interactive states only (hover, focus, active, disabled, loading)
/component-polish interactions — micro-interactions only (animations, transitions, entrance effects)

Instructions

Parse the argument and run the specified area. If no argument, run all three in order.


Area: states

Add complete interactive states to components: hover, focus, active, disabled, loading.

Goals:

  • Every interactive element has all essential states defined
  • States are visually distinct and accessible (focus visible to keyboard users)
  • Transitions between states are smooth (150ms ease-out for micro, 200ms for larger elements)

Hover states — subtle, purposeful changes:

css
1.button:hover { background: var(--color-primary-dark); transform: translateY(-1px); box-shadow: 0 2px 4px rgba(0,0,0,.1); } 2.card:hover { border-color: var(--color-border-hover); box-shadow: 0 4px 12px rgba(0,0,0,.08); } 3.link:hover { color: var(--color-primary-dark); text-decoration-color: currentColor; }

Focus states — keyboard-accessible, always visible:

css
1.button:focus-visible { outline: 2px solid var(--color-primary); outline-offset: 2px; } 2.input:focus { border-color: var(--color-primary); box-shadow: 0 0 0 3px rgba(37,99,235,.15); outline: none; }

Active/pressed states:

css
1.button:active { transform: translateY(0); box-shadow: none; background: var(--color-primary-darker); } 2.card:active { transform: scale(0.99); }

Disabled states:

css
1.button:disabled { opacity: 0.5; cursor: not-allowed; pointer-events: none; } 2.input:disabled { background: var(--color-gray-100); color: var(--color-gray-400); cursor: not-allowed; }

Loading states:

css
1.buttonLoading { position: relative; color: transparent; pointer-events: none; } 2.buttonLoading::after { 3 content: ''; position: absolute; width: 16px; height: 16px; 4 border: 2px solid currentColor; border-right-color: transparent; 5 border-radius: 50%; animation: spin 0.6s linear infinite; 6 top: 50%; left: 50%; transform: translate(-50%, -50%); 7} 8@keyframes spin { to { transform: translate(-50%, -50%) rotate(360deg); } }

Component-specific state guide:

ComponentHoverFocusActiveDisabledLoading
ButtonDarken + liftRing outlinePress downDim + no-pointerSpinner, text hidden
InputBorder colorBorder + glow ringGray bg
CardShadow + borderfocus-within ringScale 0.99DimSkeleton
LinkColor + underlineOutlineDarkerDim
TogglePreview stateRingScale 0.95DimSpinner

Base transition:

css
1.button { transition: all 0.15s ease-out; } 2.card { transition: transform 0.2s ease-out, box-shadow 0.2s ease-out, border-color 0.15s ease-out; }

Area: interactions

Add micro-interactions — animations and transitions that make interfaces feel responsive and alive.

Goals:

  • Hover/press feedback on all interactive elements
  • Entrance animations for content that appears dynamically
  • Loading states that feel smooth (no jarring spinners)
  • All animations respect prefers-reduced-motion
  • Only animate transform and opacity for 60fps performance

Hover effects:

css
1/* Lift */ 2.card { transition: transform 0.2s ease-out, box-shadow 0.2s ease-out; } 3.card:hover { transform: translateY(-4px); box-shadow: 0 12px 24px rgba(0,0,0,.15); } 4 5/* Underline slide */ 6.link::after { content: ''; position: absolute; bottom: 0; left: 0; width: 0; height: 2px; background: currentColor; transition: width 0.2s ease-out; } 7.link:hover::after { width: 100%; }

Press feedback:

css
1.button:active { transform: scale(0.98); transition: transform 0.1s ease; }

Entrance animations:

css
1@keyframes fadeIn { from { opacity: 0; } to { opacity: 1; } } 2@keyframes slideUp { from { opacity: 0; transform: translateY(20px); } to { opacity: 1; transform: translateY(0); } } 3 4.fadeIn { animation: fadeIn 0.3s ease-out; } 5.slideUp { animation: slideUp 0.4s ease-out; } 6 7/* Stagger for lists */ 8.staggerItem { opacity: 0; animation: slideUp 0.4s ease-out forwards; } 9.staggerItem:nth-child(1) { animation-delay: 0ms; } 10.staggerItem:nth-child(2) { animation-delay: 50ms; } 11.staggerItem:nth-child(3) { animation-delay: 100ms; }

Loading animations:

css
1/* Skeleton pulse */ 2.skeleton { background: var(--color-gray-200); animation: pulse 1.5s ease-in-out infinite; } 3@keyframes pulse { 0%, 100% { opacity: 1; } 50% { opacity: 0.5; } }

Common patterns:

css
1/* Tooltip */ 2.tooltip { opacity: 0; transform: translateY(4px); transition: all 0.15s ease-out; pointer-events: none; } 3.trigger:hover .tooltip { opacity: 1; transform: translateY(0); } 4 5/* Modal */ 6.modal { opacity: 0; transform: scale(0.95); transition: all 0.3s ease-out; } 7.modalOpen { opacity: 1; transform: scale(1); }

Timing guide:

InteractionDurationEasing
Hover on/off150msease-out
Button press100msease
Card hover200msease-out
Modal open300msease-out
Modal close200msease-in
Entrance300-400msease-out

Always include reduced-motion override:

css
1@media (prefers-reduced-motion: reduce) { 2 *, *::before, *::after { 3 animation-duration: 0.01ms !important; 4 transition-duration: 0.01ms !important; 5 } 6}

Full Polish Pass (default)

When no argument is provided, run all three areas in order, then apply final refinements:

  1. States — Apply the states area above
  2. Interactions — Apply the interactions area above
  3. Design system consistency — Verify all colors, spacing, typography from tokens
  4. Subtle details — Layered shadows, inner glows, gradient accents where appropriate
  5. Spacing and alignment — Optical alignment for icons, consistent rhythm
  6. Accessibility final check — aria-busy on loaders, aria-invalid on errors, all focus states visible

Design system consistency check:

tsx
1// ❌ Inconsistent 2<div className="p-3 rounded-md bg-gray-100"> 3<div className="p-4 rounded-lg bg-slate-50"> 4 5// ✅ Consistent 6<div className="p-4 rounded-lg bg-surface">

Refined shadows:

css
1.card { box-shadow: 0 1px 2px rgba(0,0,0,.04), 0 4px 8px rgba(0,0,0,.04); } 2.cardElevated { box-shadow: 0 2px 4px rgba(0,0,0,.04), 0 8px 16px rgba(0,0,0,.08); }

Polish checklist:

  • All design tokens used (no hardcoded values)
  • All interactive states present (hover, focus, active, disabled, loading)
  • Entrance animations on dynamic content
  • Skeleton loading states instead of spinners for content loads
  • Error states styled with accessible messaging
  • Touch targets ≥ 44px on mobile
  • Focus indicators visible and styled
  • prefers-reduced-motion respected
  • No layout shift on state change
  • Responsive at all breakpoints

Compétences associées

Looking for an alternative to component-polish or another community skill for your workflow? Explore these related open-source skills.

Voir tout

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

widget-generator

Logo of f
f

Générez des plugins de widgets personnalisables pour le système de flux prompts.chat

flags

Logo of vercel
vercel

Le Cadre de Réaction

138.4k
0
Navigateur

pr-review

Logo of pytorch
pytorch

Tenseurs et réseaux neuronaux dynamiques en Python avec une forte accélération GPU

98.6k
0
Développeur