tailwind-4-docs Skill: What It Does and How to Install It
Gives your agent a local copy of the Tailwind CSS v4 docs, a migration checklist and a gotchas list, so it answers from the official docs.
- Installs
- 18.1K
- on skills.sh
- Stars
- 79
- on GitHub
- Files
- 4
- besides SKILL.md
- Updated
- Apr 2026
- last repo commit
The SKILL.md tells the agent to answer Tailwind v4 questions from a local docs snapshot. The snapshot is not bundled. A Python script clones the Tailwind docs repo and copies the docs into the skill's references/docs/ folder, and the agent loads only the file it needs. For implementation, refactor or review work it also reads an engineering playbook.
If the snapshot is missing or more than a week old, the SKILL.md says the agent must ask to run the sync command before it answers. It needs Python 3, git and internet access. Until the sync has run, the bundled gotchas list and playbook are a limited fallback.
Good for
- Developers upgrading a project from Tailwind v3 to v4
- Teams that want agents to follow the official v4 docs
- Reviewers checking Tailwind code for common v4 mistakes
Install tailwind-4-docs
Claude Code
- 1
Copy this prompt.
Install the tailwind-4-docs skill in Claude Code. Run this command: npx skills add Lombiq/Tailwind-Agent-Skills Then check that it loaded and tell me how to use it.
- 2
Paste it into Claude Code. It shows the change and asks before running it.
Requires Node.js.
After installing, run the sync script once. The README command is python skills/tailwind-4-docs/scripts/sync_tailwind_docs.py --accept-docs-license, run from your project root with the path changed to wherever the skill folder now sits. It needs Python 3.8 or later, git, internet access and a writable skill folder, and it downloads the Tailwind docs, which the README calls source-available and not open source. Add --local-repo <path> if you already have a clone of tailwindlabs/tailwindcss.com.
From the project README. Source.
What's in the skill
When it loads
Comprehensive Tailwind CSS v4 documentation snapshot and workflow guidance. Use when answering Tailwind v4 questions, selecting utilities/variants, configuring Tailwind v4, or migrating projects from v3 to v4 with official docs and gotcha checks.
Sections in SKILL.md
- Overview
- Quick start
- Initialization (required once per install)
- References map
- MDX handling
- Common entry points
- Migration checklist
- Update workflow
Key facts
- Installs on skills.sh
- 18,052 (Nov 2, 2026)
- Last repo commit
- Apr 9, 2026
What it includes
See if references/docs/ and references/docs-index.tsx exist and are under a week old.
If not, the agent stops and asks to run the initialization step before answering.
Read ·
Check the snapshotsync_tailwind_docs.py clones tailwindcss.com and copies the docs in.
Needs --accept-docs-license. Writes references/docs/, docs-index.tsx and docs-source.txt with the upstream commit and snapshot date.
Try: “Initialize the Tailwind docs snapshot”
Delete ·
Sync scriptLook up the topic in docs-index.tsx and open one file from references/docs/.
Reads the MDX files, treating the exported title and description as metadata and the callout tags as guidance.
Try: “How do I set a custom theme color in Tailwind v4?”
Read ·
Find the right docLoad references/engineering-playbook.md for implementation, refactor and review.
Sections cover tokens first, custom utilities, component classes, variants, @apply, responsive strategy and a review checklist.
Try: “Review this component for Tailwind v4 best practice”
Read ·
Engineering playbookA 20-item quick scan of v4 migration pitfalls.
Covers browser support, the new @tailwindcss/postcss, cli and vite packages, @import "tailwindcss", renamed utilities and @theme rules. Source: references/gotchas.md.
Read ·
Gotchas listConfirm browser support, tooling, imports, renames and variant changes.
Points to references/docs/upgrade-guide.mdx and compatibility.mdx after the sync.
Try: “Plan the Tailwind v3 to v4 upgrade for this project”
Read ·
Migration checklist
From the official docs
Permissions
Medium risk
The sync script downloads a GitHub repo and replaces the docs folder inside the skill, and with a local repo option it hard-resets that clone. Point that option at a throwaway clone only.
What it can do
- Read your data
- Create and change things
- Delete things
- Read-only mode
Watch out for
The sync script downloads from GitHub and replaces files
scripts/sync_tailwind_docs.py runs git clone --depth 1 of tailwindlabs/tailwindcss.com into a temp folder, deletes references/docs in the skill folder, and copies in the fresh docs and index. github.com
--local-repo hard-resets the clone you give it
With --local-repo, the script runs git fetch, git checkout and git reset --hard origin/<ref> in that folder. Point it at a throwaway clone, not one with uncommitted work. github.com
The agent is told to ask before running it
The SKILL.md says that if the snapshot is missing or older than one week, the agent must ask permission to run the command or ask you to run it, and should not give Tailwind guidance until it exists. github.com
The docs have their own license
The README calls the Tailwind docs repo source-available and not open source, and says users must accept its license. The script refuses to run without --accept-docs-license. github.com
Security advisories
No published security advisories as of Nov 2, 2026.
Technical details
| Turning on read-only | No read-only mode. |
|---|---|
| Talks to | github.com/tailwindlabs/tailwindcss.com (git clone by the sync script) |
| Scopes |
|
Questions
What does tailwind-4-docs do?
It makes your agent answer Tailwind CSS v4 questions from a local copy of the official docs. It also adds a migration checklist, a gotchas list and an engineering playbook for implementation and review.
How do I install tailwind-4-docs?
Use the install box above, then run the sync script once. The README says to ask your agent to run it if it does not do so on its own, and to confirm that references/docs/ and references/docs-index.tsx were created.
Is tailwind-4-docs an official Tailwind Labs skill?
It is a third-party skill. The README says it is developed by Lombiq Technologies, and the skill downloads the Tailwind docs from the tailwindlabs/tailwindcss.com repository instead of bundling them.
Why does the agent ask to run a command first?
The docs are not bundled because the Tailwind docs repo is source-available but not open source. The SKILL.md has the agent ask permission to download them whenever the snapshot is missing or older than one week.
Does it need Python and internet?
Yes, for the sync step. The README lists Python 3.8 or later, git, internet access and a writable skill folder. Without the snapshot, the gotchas list and playbook still work as a limited fallback.
Does it work in the Claude app?
The README documents folders for Copilot, Codex and Claude Code, not the Claude app. The sync step runs Python and git locally, so the install box has no Claude app tab.
Is tailwind-4-docs safe to install?
The skill itself is instructions plus one Python script that clones a GitHub repo and replaces its own docs folder. Our advice: do not use --local-repo on a clone with uncommitted work, because the script hard-resets it.
Information
updated Nov 2, 2026
- Repository
- lombiq/tailwind-agent-skills
- Folder
skills/tailwind-4-docs
Sources
Docs, issue trackers and discussions this page is built from.
Show all 6Hide
- tailwind-4-docs SKILL.md · github.com
- Tailwind-Agent-Skills Readme · github.com
- sync_tailwind_docs.py · github.com
- gotchas.md · github.com
- engineering-playbook.md · github.com
- Tailwind-Agent-Skills License.md · github.com