Tailwind Design System
Build scalable design systems with Tailwind CSS v4 — CSS-first config, design tokens, component variants, responsive patterns, and accessibility
- What
- Build scalable design systems with Tailwind CSS v4 — CSS-first config, design tokens, component variants, responsive patterns, and accessibility
- Cost
- Free
- Needs
- a project using (or moving to) Tailwind CSS v4
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — a practical guide to building production-ready design systems with Tailwind CSS v4: CSS-first configuration with `@theme`, design tokens and theming, component variants, responsive and accessible patterns, and dark mode via native CSS features. Includes a v3→v4 migration map (e.g. `tailwind.config.ts` → `@theme` in CSS). Targets Tailwind v4 (2024+) specifically — for v3 projects it points to the official upgrade guide rather than mixing versions. By @wshobson, listed here with credit to its creator. Honest caveats: v4-only guidance; if your project is stuck on Tailwind v3, most patterns here won't apply directly. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: a project using (or moving to) Tailwind CSS v4 Install "Tailwind Design System" for me. Build scalable design systems with Tailwind CSS v4 — CSS-first config, design tokens, component variants, responsive patterns, and accessibility Repository: https://github.com/wshobson/agents/blob/main/plugins/frontend-mobile-development/skills/tailwind-design-system/SKILL.md 1. Fetch the SKILL.md file for the wshobson-tailwind-design-system skill from the repository into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "wshobson-tailwind-design-system". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. any accounts, API keys, or CLI tools mentioned in the prerequisites above). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. Never ask me to paste secrets in chat — credentials go through the secure vault or environment variables. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.