refactor-html
Refactor HTML/TSX files to use existing UI components, DaisyUI classes, and semantic colors. Use when (1) refactoring React/TSX page components to use reusable UI components, (2) replacing raw HTML elements with component library equivalents, (3) converting primitive Tailwind colors to semantic DaisyUI colors, (4) extracting repeated styling patterns into components.
When & Why to Use This Skill
This Claude skill automates the refactoring of React and TSX files to ensure compliance with project-specific UI standards and design systems. It specializes in replacing raw HTML elements with reusable UI components, migrating primitive Tailwind CSS colors to semantic DaisyUI classes, and streamlining codebases by extracting repetitive styling patterns into maintainable components.
Use Cases
- Legacy Code Modernization: Automatically transform HTML-heavy React components into a structured architecture using standardized internal UI libraries.
- Design System Migration: Seamlessly migrate primitive Tailwind utility classes to a semantic DaisyUI system to improve themeability and brand consistency.
- UI Standardization: Enforce project conventions by replacing standard HTML tags (like <button>, <input>, or <select>) with their corresponding design system equivalents.
- Technical Debt Reduction: Identify and extract recurring inline styling patterns into reusable components, reducing code duplication and improving maintainability.
| name | refactor-html |
|---|---|
| description | Refactor HTML/TSX files to use existing UI components, DaisyUI classes, and semantic colors. Use when (1) refactoring React/TSX page components to use reusable UI components, (2) replacing raw HTML elements with component library equivalents, (3) converting primitive Tailwind colors to semantic DaisyUI colors, (4) extracting repeated styling patterns into components. |
Refactor HTML/TSX
Refactor page components to follow project conventions: use existing UI components, DaisyUI classes, and semantic colors.
Rules
1. Use Existing Components
Replace raw HTML with UI components from packages/ui/src/components/ui/. See components.md for available components and their props.
| Before | After |
|---|---|
<div className="alert alert-error"> |
<Alert variant="error"> |
<button className="btn btn-primary"> |
<Button variant="primary"> |
<input className="input input-bordered"> |
<Input /> |
<select className="select select-bordered"> |
<Select /> |
<fieldset className="fieldset"> |
<Fieldset> |
<span className="loading loading-spinner"> |
<Loading /> |
2. Use Semantic Colors
Replace primitive colors with DaisyUI semantic colors:
| Primitive (NG) | Semantic (OK) |
|---|---|
text-red-* |
text-error |
text-blue-* |
text-primary |
text-green-* |
text-success |
bg-gray-100 |
bg-base-100 |
border-gray-* |
border-base-300 |
3. Extract Repeated Styles
When styling patterns repeat (e.g., border-t border-base-300 pt-6), consider extracting to a component.
Workflow
- Read target file
- Check available components in
packages/ui/src/components/ui/ - Identify rule violations
- Apply refactoring with Edit tool
- Add necessary imports
- Report changes made