tailwind-design-system
Skill by wpank
Why use this skill?
Master your design system using CVA, component tokens, and Tailwind CSS. Learn to build type-safe, themeable UI libraries easily.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/wpank/tailwind-design-systemWhat This Skill Does
The tailwind-design-system skill provides a standardized framework for architecting scalable, maintainable component libraries within a Tailwind CSS ecosystem. It acts as an architectural guide and code generator that helps developers implement high-quality UI patterns using industry-standard tools like Class Variance Authority (CVA), tailwind-merge, and clsx. By focusing on a token-driven approach, this skill ensures that your design system remains consistent across complex applications, supporting advanced features like theme-based variables, dark mode toggling, and type-safe component props.
Installation
To integrate this skill into your environment, use the OpenClaw CLI package manager:
npx clawhub@latest install tailwind-design-system
Ensure your project already has Tailwind CSS configured, as this skill builds upon the base utility-first paradigm.
Use Cases
This skill is ideal for:
- Building robust component libraries (similar to shadcn/ui) from scratch.
- Migrating legacy CSS into a clean, token-based architecture.
- Implementing complex, themeable UI components that require variants (e.g., button, card, or modal variants).
- Enforcing strict type safety on design components using TypeScript and CVA.
- Setting up advanced responsive layouts and animation states that share consistent logic.
Example Prompts
- "Build a new Button component using CVA that supports primary, secondary, and ghost variants with three distinct sizes."
- "Help me define a semantic color system in my tailwind.config.ts file that supports both light and dark mode using CSS variables."
- "Refactor my existing card component to use a compound component architecture for header, content, and footer sections."
Tips & Limitations
- Token Hierarchy: Always define primitive tokens first before mapping them to semantic tokens to avoid circular dependencies in your CSS variables.
- Performance: While
clsxandtailwind-mergeare highly efficient, avoid over-nesting CVA variants to prevent complex build-time calculations in extremely large component files. - Tailwind v4: If you are using the latest Tailwind CSS version 4, consider using the
tailwind-v4-shadcnskill instead, as this design system skill is optimized for v3-based architectural patterns but remains highly portable.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-wpank-tailwind-design-system": {
"enabled": true,
"auto_update": true
}
}
}Tags(AI)
Flags: file-write
Related Skills
mermaid-diagrams
Create software diagrams using Mermaid syntax. Use when users need to create, visualize, or document software through diagrams including class diagrams, sequence diagrams, flowcharts, ERDs, C4 architecture diagrams, state diagrams, git graphs, and other diagram types. Triggers include requests to diagram, visualize, model, map out, or show the flow of a system.
api-design-principles
Skill by wpank
auto-context
Automatically read relevant context before major actions. Loads TODO.md, roadmap.md, handoffs, task plans, and other project context files so the AI operates with full situational awareness. Use when starting a task, implementing a feature, refactoring, debugging, planning, or resuming a session.
clear-writing
Write clear, concise prose for humans — documentation, READMEs, API docs, commit messages, error messages, UI text, reports, and explanations. Combines Strunk's rules for clearer prose with technical documentation patterns, structure templates, and review checklists.
track-performance
Track the performance of Uniswap LP positions over time — check which positions need attention, are out of range, or have uncollected fees. Use when the user asks how their positions are doing.