tailwind-design-system · sickn33 — Claude Code skill: install and use
A skill that keeps the agent on Tailwind while you build a design system: tokens, component variants, responsive patterns, accessibility. Useful when the UI drifts.
npx skills add sickn33/agentic-awesome-skills --skill tailwind-design-system -a claude-codeWhat tailwind-design-system does
It asks for goals, constraints and inputs first, then returns steps and a way to check them. The trigger list is narrow on purpose: a component library, tokens and theming, responsive and accessible components, one UI pattern across a codebase, a move to Tailwind, dark mode.
The skill folder holds SKILL.md with those instructions and resources/implementation-playbook.md. The agent opens the second file when you want worked examples and fuller patterns.
Its own limitations are blunt: the output does not replace validation in your environment, testing or expert review. So token names and contrast still need a look in the browser. If inputs, permissions or success criteria are missing, the skill stops and asks instead of filling the gaps.
What it helps with
- spin up a component library on Tailwind
- move colors and spacing into design tokens
- add dark mode without copy-pasted class strings
- unify scattered buttons and form fields
- check a component for keyboard access and small screens
Example prompts for the agent
- Set up a Tailwind design system: tokens for color, spacing and type, plus button variants.
- Migrate these hand-written classes to my Tailwind theme tokens.
- Build a responsive card and check it works with a keyboard.
How to install tailwind-design-system
1Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill tailwind-design-system -a claude-code2Manually: put the files in place
~/.claude/skills/tailwind-design-system/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/tailwind-design-system/
1Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill tailwind-design-system -a codex2Manually: put the files in place
.agents/skills/tailwind-design-system/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill tailwind-design-system -a cursor2Manually: put the files in place
.cursor/skills/tailwind-design-system/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install sickn33/agentic-awesome-skills tailwind-design-system2Manually: put the files in place
.github/skills/tailwind-design-system/SKILL.md1Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill tailwind-design-system -a gemini-cli2Platform CLI
gemini skills install https://github.com/sickn33/agentic-awesome-skills --path skills/tailwind-design-systemManually: put the files in place
.devin/skills/tailwind-design-system/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add sickn33/agentic-awesome-skills --skill tailwind-design-system -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set80
The whole set →Other versions of tailwind-design-system
Similar
Questions about tailwind-design-system
How do I install tailwind-design-system in Claude Code?
Run npx skills add sickn33/agentic-awesome-skills --skill tailwind-design-system -a claude-code. The skill file lands at ~/.claude/skills/tailwind-design-system/SKILL.md.
What does tailwind-design-system do?
Walks the agent through Tailwind design system work: tokens and theming, component variants, responsive patterns, accessibility, dark mode.
Does it replace testing my UI?
No. The skill's limitations say the output is not a substitute for environment-specific validation, testing or expert review.
Source text
SKILL.md · MIT
--- name: tailwind-design-system description: "Build production-ready design systems with Tailwind CSS, including design tokens, component variants, responsive patterns, and accessibility." risk: safe source: community date_added: "2026-02-27" --- # Tailwind Design System Build production-ready design systems with Tailwind CSS, including design tokens, component variants, responsive patterns, and accessibility. ## Use this skill when - Creating a component library with Tailwind - Implementing design tokens and theming - Building responsive and accessible components - Standardizing UI patterns across a codebase - Migrating to or extending Tailwind CSS - Setting up dark mode and color schemes ## Do not use this skill when - The task is unrelated to tailwind design system - You need a different domain or tool outside this scope ## Instructions - Clarify goals, constraints, and required inputs. - Apply relevant best practices and validate outcomes. - Provide actionable steps and verification. - If detailed examples are required, open `resources/implementation-playbook.md`. ## Resources - `resources/implementation-playbook.md` for detailed patterns and examples. ## Limitations - Use this skill only when the task clearly matches the scope described above. - Do not treat the output as a substitute for environment-specific validation, testing, or expert review. - Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
© sickn33 · MIT · sickn33/agentic-awesome-skills