Provide llms-full.txt file on Tailwind CSS docs site

[doggy8088]

This idea comes from the Model Context Protocol (MCP) site.

The MCP site has a special endpoint here:
https://modelcontextprotocol.io/llms.txt

It's similar to a sitemap file but used for LLMs.

Additionally, there is another endpoint here:
https://modelcontextprotocol.io/llms-full.txt

This provides the entire documentation (plain text format) in one place for LLMs.

Such a design is very convenient in the current age of AI prevalence, and it is hoped that it can be provided.

[sovetski]

that would be great

[thedotmack]

No they decided they were going to charge $12 a month for it, right @adamwathan ?

[thedotmack]

From https://tailwindcss.com/sponsor

Cursor/Claude/AGENTS.md rules — Adam's personal ruleset for working with AI coding assistants, straight from the Tailwind founder's own development setup.

Pretty open source if you ask me, no way to copy paste docs easily on site, you just made everyone's default setup a monetization strategy

[sovetski]

Really?? 😅

[adriancuadrado]

#14677

[sovetski]

We have also https://context7.com/websites/tailwindcss, it might never be like an official llms.txt but is not bad

[msears124]

Just hopping in to say there is a deno package which can scrape the .MDX files from the tailwindcss.com repository, and create an automated llms-full.txt. See here: https://jsr.io/@jurajstefanic/docs2llms

[barthamark]

I just noticed this thread as well. I mentioned this in another discussion too, but sharing here in case it helps someone while an official solution is released:

We built Tailwind v4 Agent Skills that worked well for us internally. It includes an agent-optimized docs workflow: a script that creates a local docs snapshot plus an index map, so an agent can load only the relevant doc pages (and you can refresh it anytime). We also maintain a curated “gotchas” list based on real migration and day-to-day dev work.

Important note: we don’t bundle or redistribute Tailwind docs. The skill just automates pulling a local snapshot after you explicitly accept the upstream docs license.

Everything else is in the repo readme: https://github.com/Lombiq/Tailwind-Agent-Skills

[JYeswak]

+1, with a structural angle. I'm building a library-docs substrate for AI-coding workflows (Tier-1 llms.txt → Tier-2 GitHub README fallback). Across 17 production-stack libraries we walked through (React, Next.js, shadcn/ui, TanStack Query, Stripe, Supabase, Infisical, Railway, Vercel, Nango, Anthropic SDK, OpenAI SDK, MCP SDK, Pydantic, NestJS, HubSpot, and Tailwind), Tailwind is the only Tier-1 gap in the frontend cluster — and it looks structural given the Insiders sponsor tier explicitly bundles "Cursor/Claude/AGENTS.md rules" as a paid perk.

Worth distinguishing though: that licensing restriction covers the AGENTS.md rules and adjacent perks specifically, not the public docs themselves. Pages like tailwindcss.com/docs/installation/using-vite are publicly accessible and Algolia-indexed. An llms.txt pointing at the existing free public docs subset (excluding the AGENTS.md content) would close the gap for downstream tooling without touching sponsor revenue. The MCP project's llms-full.txt is a working precedent — aggregated public docs, no paywall friction.