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.
90
87%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Refactor page components to follow project conventions: use existing UI components, DaisyUI classes, and semantic colors.
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 /> |
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 |
When styling patterns repeat (e.g., border-t border-base-300 pt-6), consider extracting to a component.
packages/ui/src/components/ui/f734087
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.