Tailwind CSS v4 docs snapshot workflow
Answer Tailwind v4 questions from a locally synced official-docs snapshot, with a migration checklist and engineering playbook
- What
- Answer Tailwind v4 questions from a locally synced official-docs snapshot, with a migration checklist and engineering playbook
- Cost
- Free
- Needs
- git, Python 3 and internet access for the one-time docs sync. The docs snapshot comes from tailwindlabs/tailwindcss.com, which is source-available but not open-source: downloading it means accepting that repo's license, and my "yes, install" at the confirmation step will count as that acceptance.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — a workflow for answering Tailwind CSS v4 questions from a locally synced snapshot of the official docs: a one-time sync script downloads the tailwindcss.com docs into `references/docs/`, then the agent looks up utilities, variants, config and migration guidance via a docs index, with an engineering playbook for implementation/refactor/review tasks and a gotchas file covering common v3→v4 pitfalls. By @lombiq, listed here with credit to its creator. Honest caveats: the docs snapshot is NOT bundled — initialization requires git, Python 3 and internet access, and you must accept the tailwindcss.com license (source-available, not open-source) before downloading; until the snapshot is initialized, only the bundled gotchas and engineering-playbook fallbacks are available. Discovered via skills.sh. Skill Harbor never reviews the code, review it yourself before use.
Version:
Quick answer
Tailwind CSS v4 docs snapshot workflow is a free Muse skill that answers Tailwind v4 questions from a locally synced snapshot, with a migration checklist. A one-time sync script downloads the official docs into a local references folder, then the agent looks up utilities and migration guidance via a docs index, so answers stay grounded in official documentation.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 634ec18Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: git, Python 3 and internet access for the one-time docs sync. The docs snapshot comes from tailwindlabs/tailwindcss.com, which is source-available but not open-source: downloading it means accepting that repo's license, and my "yes, install" at the confirmation step will count as that acceptance. Install "Tailwind CSS v4 docs snapshot workflow" for me. Give my agent the Tailwind v4 docs workflow: the sync script that downloads the official docs locally, the docs index for looking up utilities, variants, config and migration guidance, the engineering playbook, and the v3-to-v4 gotchas file. Repository: https://raw.githubusercontent.com/lombiq/tailwind-agent-skills/634ec184c36e495fae1d8cf7975df7e6969e3a89/skills/tailwind-4-docs/SKILL.md Pinned version: install the code at commit 634ec184c36e495fae1d8cf7975df7e6969e3a89 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. The skill folder (skills/tailwind-4-docs/ in the repo, branch dev) contains exactly these 5 files, and I want all of them: - SKILL.md - scripts/sync_tailwind_docs.py - references/docs-source.txt - references/engineering-playbook.md - references/gotchas.md Two more pieces are generated locally by the initialization step below, they are not in the repo: references/docs/ (the docs snapshot) and references/docs-index.tsx (the index the skill looks topics up in). 1. Fetch the whole skills/tailwind-4-docs folder into a temporary folder (all 5 files listed above) and look inside. 2. Integrity check: Skill Harbor reviewed this listing on 2026-10-09 and recorded the fingerprints below. I want you to compute the SHA-256 of each downloaded file and compare: - SKILL.md: SHA-256 72304ac077613ab1f9dd449483dcf64e71e6d2f709eec27d430e68fa1eda034f - scripts/sync_tailwind_docs.py: SHA-256 d973bfc8a9637d8a0a86387f03fd89ff3857c2bf4eb130672549675a969f6603 - references/docs-source.txt: SHA-256 5b82557ed150c357a7607bf2eb850f43da0c6ddce0ee4557e249684b34326d4a - references/engineering-playbook.md: SHA-256 9184ed1dd0b9f4472233d73eb1de8ae7458b18606283d1c62531478c06f79bfd - references/gotchas.md: SHA-256 065d1087042679f9884c1f3f734b8ca3c627594c435c009e3fb9d8a0f120d53d If a fingerprint does not match, I want you to stop before installing and tell me the files changed since Skill Harbor's review, so the new version is unverified. Show me your safety findings and give me three choices: (a) wait for Skill Harbor to re-review the listing (recommended), (b) analyze the new files in detail first and then decide, (c) install anyway knowing the risk. Then wait for my answer before doing anything else. 3. Safety check: I want to see your findings explicitly, in short separate items: - every network address the code contacts (expect: the sync script clones tailwindlabs/tailwindcss.com from GitHub, nothing else) - every shell command it runs (expect: the sync script runs git clone at depth 1 and copies files) - every place credentials, API keys or personal data are read, stored or sent (expect: none) - any obfuscated or encoded code If anything looks suspicious, stop and explain it to me before continuing. 4. Confirmation: before installing, give me a short summary of what the skill does plus your safety findings, remind me that installing includes the one-time docs download under the tailwindcss.com license, and wait for my explicit "yes, install". 5. Install it as a skill: copy all 5 files, keeping the folder structure (SKILL.md at the top, scripts/ and references/ under it), into the agent's skills directory, in a folder named "lombiq-tailwind-agent-skills-tailwind-4-docs". 6. Initialization (part of the install, not an optional extra): run the installed sync script once, python3 scripts/sync_tailwind_docs.py --accept-docs-license from the installed folder, so it generates references/docs/ and references/docs-index.tsx and updates references/docs-source.txt with the snapshot date. This downloads a shallow clone of the docs repo, so give it time to finish. 7. Verify with no network calls: frontmatter valid, all 5 base files in place, references/docs/ exists and contains .mdx files, references/docs-index.tsx exists, and references/docs-source.txt shows a snapshot date instead of "Not initialized". 8. Report what was installed, where, and what I still need to do myself (for example re-running the sync script about once a week to refresh the snapshot). 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. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
- It can run commands on your Muse’s computer.
- It can download and install software packages.
What the scan found — excerpts from the install prompt
- runs commands — 6. Initialization (part of the install, not an optional extra): run the installed sync script once, python3 sc · - chaque commande shell qu'il exécute (attendu : le script de synchro lance un git clone à profondeur 1 et cop · 6. Initialisation (fait partie de l'installation, pas un extra optionnel) : lance le script de synchro install
- installs packages — - every shell command it runs (expect: the sync script runs git clone at depth 1 and copies files) · - chaque commande shell qu'il exécute (attendu : le script de synchro lance un git clone à profondeur 1 et cop
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 634ec18 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : runs commands · installs packages
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill 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 skill before installing it.