component-fix

Fix UI component implementations in design-system repositories.

Updated Sep 14, 2025
One-click install
npx skills add https://github.com/Higashi-Kota/react-tailwindcss-sandbox --skill component-fix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: component-fix
Source: https://github.com/Higashi-Kota/react-tailwindcss-sandbox/tree/main/.claude/skills/component-fix
Command: npx skills add https://github.com/Higashi-Kota/react-tailwindcss-sandbox --skill component-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pnpm.

What problem does it solve?

Inconsistent token usage, non-standardized props, or missing accessibility patterns in UI components lead to a fragmented user experience and increased maintenance burden. This Skill systematically fixes these issues, ensuring your components are robust, accessible, and aligned with your design system.

Core Features & Use Cases

  • Token Usage Updates: Replaces hardcoded styles (e.g., bg-blue-600) with semantic theme tokens (e.g., bg-primary) for consistent theming.
  • Props API Standardization: Aligns variant, size, and state props (e.g., typevariant, smallsm) across component groups for a unified developer experience.
  • Accessibility Enhancements: Implements critical accessibility patterns like visible focus indicators, text adaptation on hover, and missing states (e.g., disabled, loading, error).
  • Efficient Code Modification: Leverages symbolic code manipulation tools for targeted and systematic changes, minimizing manual effort and errors.
  • Use Case: Standardize the variant prop across all button-like components (Button, IconButton, SegmentedButton) and add a consistent loading state with a spinner to each.

Quick Start

Use the component-fix skill to add a loading state to the Button component, including the prop, spinner, and disabled logic.

Frequently Asked Questions about component-fix

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update UI components to use design system tokens instead of hardcoded styles?

Token usage updates replace hardcoded styles like `bg-blue-600` with semantic theme tokens like `bg-primary` across your React components, ensuring consistent theming and easier design system maintenance.

What's the best way to standardize component props across a design system?

Props API standardization aligns variant, size, and state props (e.g., `type` → `variant`, `small` → `sm`) across related components like Button and IconButton, creating a unified developer experience and reducing cognitive load.

How do I add accessibility patterns to existing React components?

Accessibility enhancements implement critical patterns including visible focus indicators, text adaptation on hover, and missing states like `disabled`, `loading`, and `error` to meet accessibility conformance requirements.

Can I standardize multiple component variants at once in Tailwind CSS projects?

Yes, systematic code modification tools enable targeted updates across component groups—for example, standardizing the `variant` prop and adding a consistent loading state with spinner to all button-like components simultaneously.

What validation happens after component changes are applied?

Automated post-change validation using build-validation and Serena MCP tooling confirms that token remapping, Props API standardization, and accessibility conformance meet technical requirements before deployment.

Do I need pnpm to use component fixes in my design system workflow?

pnpm is a required dependency for running component fixes, serving as the package manager for the Skill's execution environment and build validation processes.