agentleFS
TsuzatTsuzat/Edra/.agents/skills/tailwind-4-docs/SKILL.md

tailwind-4-docs

Skill675 starsChanged 4 months agoMITView on GitHub

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.

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 1

    1. wemwi/skill-library★ 146% same

    Wrote their own version · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository4 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

12 rules. About 0 are common, 5 are distinctive, and 7 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 7

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill to navigate a locally synced Tailwind CSS v4 documentation snapshot and answer development, configuration, migration, …

    line 11
  2. Very specific:

    Check whether the docs snapshot is initialized (references/docs/ and references/docs-index.tsx exist).

    line 17
  3. Distinctive:

    If the snapshot is missing or older than one week, stop and ask to run the initialization step in "Initialization" before continuing.

    line 18
  4. Distinctive:

    Run the sync script to download the Tailwind docs locally.

    line 27
  5. Very specific:

    If you cannot run tools or have no internet access, ask the user to run the exact command above in a terminal, then continue once …

    line 35
  6. Distinctive:

    If the snapshot is missing or older than one week, you must ask for permission to run the command or ask the user to run it.

    line 37
  7. Very specific:

    If initialization is blocked (no internet or no write access), use references/gotchas.md as a limited fallback and ask the user to consult …

    line 39
  8. Very specific:

    Treat export const title and export const description as metadata.

    line 51
  9. Very specific:

    Read JSX callouts like <TipInfo> or <TipBad> as guidance text.

    line 52
  10. Distinctive:

    When upgrading from v3 to v4, always confirm the following in the docs:

    line 65
  11. Very specific:

    Import syntax: @import "tailwindcss" replaces @tailwind directives.

    line 69
  12. Very specific:

    Run scripts/sync_tailwind_docs.py to refresh the snapshot.

    line 75

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Tailwind 4 Docs

Overview

Use this skill to navigate a locally synced Tailwind CSS v4 documentation snapshot and answer development, configuration, migration, implementation, refactor, and review questions with official guidance.

The docs snapshot is not bundled with this skill because the upstream repository is source-available but not open-source. Users must initialize the snapshot themselves and are responsible for complying with the upstream license.

Quick start

  1. Check whether the docs snapshot is initialized (references/docs/ and references/docs-index.tsx exist).
  2. If the snapshot is missing or older than one week, stop and ask to run the initialization step in "Initialization" before continuing. Do not answer the user's question until the snapshot is initialized.
  3. Identify the topic (utility, variant, config, migration, compatibility, implementation, refactor, review).
  4. Find the matching doc in references/docs-index.tsx.
  5. Load only the relevant file from references/docs/.
  6. For implementation, refactor, or review tasks, also load references/engineering-playbook.md.
  7. Apply guidance and call out any breaking changes or constraints.

Initialization (required once per install)

Run the sync script to download the Tailwind docs locally. This requires network access, git, and Python 3:

python skills/tailwind-4-docs/scripts/sync_tailwind_docs.py --accept-docs-license

This pulls content from tailwindlabs/tailwindcss.com. That repo is source-available and explicitly not open-source, so the user must accept its license before downloading and keep the snapshot local.

If you cannot run tools or have no internet access, ask the user to run the exact command above in a terminal, then continue once references/docs/ and references/docs-index.tsx exist.

If the snapshot is missing or older than one week, you must ask for permission to run the command or ask the user to run it. Do not proceed with Tailwind guidance until the snapshot is initialized or refreshed.

If initialization is blocked (no internet or no write access), use references/gotchas.md as a limited fallback and ask the user to consult the official docs. For implementation, refactor, or review tasks, references/engineering-playbook.md can also serve as a limited fallback.

References map

  • references/docs/ is generated locally and contains the Tailwind v4 MDX docs snapshot.
  • references/docs-index.tsx is generated locally and contains the category and slug map used by the docs sidebar.
  • references/docs-source.txt captures the upstream repo, commit, and snapshot date (or reports that initialization is pending).
  • references/engineering-playbook.md is the agent-oriented implementation, refactor, and review guide.
  • references/gotchas.md provides a quick scan of common v4 migration pitfalls.

MDX handling

  • Treat export const title and export const description as metadata.
  • Read JSX callouts like <TipInfo> or <TipBad> as guidance text.

Common entry points

  • Migration: references/docs/upgrade-guide.mdx, references/docs/compatibility.mdx.
  • Implementation/refactor/review: references/engineering-playbook.md.
  • Gotchas overview: references/gotchas.md.
  • Configuration and directives: references/docs/functions-and-directives.mdx, references/docs/adding-custom-styles.mdx, references/docs/theme.mdx.
  • Variants and responsive patterns: references/docs/hover-focus-and-other-states.mdx, references/docs/responsive-design.mdx.
  • Core behavior: references/docs/preflight.mdx, references/docs/detecting-classes-in-source-files.mdx.

Migration checklist

When upgrading from v3 to v4, always confirm the following in the docs:

  • Browser support and compatibility expectations.
  • Tooling changes: @tailwindcss/postcss, @tailwindcss/cli, @tailwindcss/vite.
  • Import syntax: @import "tailwindcss" replaces @tailwind directives.
  • Utility renames/removals, prefix format, and important modifier placement.
  • Changes to variants, transforms, and arbitrary value syntax.

Update workflow

Run scripts/sync_tailwind_docs.py to refresh the snapshot. Use --local-repo if you already have a local clone of tailwindlabs/tailwindcss.com to speed up syncs. Always pass --accept-docs-license.


Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.