Repaint

Single entry point for ALL frontend building and restyling — any page, component, dashboard, landing page, app shell, modal, settings panel, onboarding flow, hero, pricing section, data table, command palette, or chat/AI surface. Reach for this FIRST, before writing component code by hand, whenever the user wants to build, create, design, implement, redesign, or "make X look better / less generic / less AI-made / more like Linear/Vercel/Stripe" — even when the request sounds simple ("add a pricing section", "build a settings page", "make the hero bolder"). It routes internally between production-credible and art-directed modes and runs the full pipeline (register lock → brand anchor → token spec → scaffold → build → slop audit → browser verify), so do NOT separately invoke ui-expert, frontend-design, design-build, shadcn, or tailwind-design-system — this skill calls them for you. NOT for: frontend build/bundler/Vite errors, writing or fixing tests, bundle or performance optimization, CI/deploy, debugging an event handler''s logic, dependency or styling migrations, or CSS concept questions — those are other tools.

mkdir -p ~/.claude/skills/repaint
curl -L https://claudskills.com/skills/repaint/SKILL.md \
  -o ~/.claude/skills/repaint/SKILL.md

@misc{repaint-2026,
  author    = {LucasSantana-Dev},
  title     = {Repaint [Claude Code skill]},
  year      = {2026},
  publisher = {ClaudSkills},
  url       = {https://claudskills.com/skills/repaint/}
}