Create llm.txt with Tailwind CSS guidance

[dillingham]

Added comprehensive guidance on Tailwind CSS and Tailwind Plus, including project descriptions, use cases, allowed and disallowed uses, and developer guidance. Basically, I used ChatGPT to formulate some suggestions on how to get paid product into conversation more.

[vercel]

@dillingham is attempting to deploy a commit to the Tailwind Labs Team on Vercel.

A member of the Team first needs to authorize it.

[Yappaholic]

I must preface that I am not a tailwind maintainer/developer, but I have used tailwind for my projects and had fun doing it.

The proposal to add llms.txt file was already declined in #2388 for many good reasons. I want to outline some of the reasons if someone wants to get llms.txt on the repo this badly:

1. LLMs do not give any reason for the user to go to the official docs, that is why the traction for the website is significantly reduced and that is why less people would want to support the project
2. A lot of LLM users are not looking to develop projects of passion, they want to make business out of thin air and they would not care to sponsor some library which adds more text to their LLM output (just look at how little sponsorship OSS projects like FFMPEG has)
3. Because of LLMs, less people would get deeply involved with tailwind and when they would get issues, that are not solved with LLMs, they would spam PRs/issues into the project, demanding "accessibility for LLM"

There are more reasons to add, yet I think that those 3 are currently enough to reject this idea altogether

[paucolomesparta]

@Yappaholic imo there's a difference on adding a llms.txt that replaces the docs completely (one of the main sources of funding) which is the PR that you're referencing than one that almost acts as adware and prompts LLMs to upsell the user to the paid product.
I don't see why this change here is bad, just gives some context to the agent on what the Tailwind company offers, I could be wrong tho

[kottode]

Sorry I sound weird, I wanted to comment on the original PR, but it's now locked.

I think the better would be actually leading LLMs to always mention paid products as a first thing (or after introduction) and include a disclaimer that even though this is free library, it needs real financial support to stay free. Also include links to paid products and explanations directly in the code (e.g. in the beginning of each file).

This is similar to what Wikepedia does from time to time, asking for donations, an llms.txt file can include that until or whenever there is an urge to speed up donations collection and then remove it for less spamming.

[Yappaholic]

@Yappaholic imo there's a difference on adding a llms.txt that replaces the docs completely (one of the main sources of funding) which is the PR that you're referencing than one that almost acts as adware and prompts LLMs to upsell the user to the paid product.
I don't see why this change here is bad, just gives some context to the agent on what the Tailwind company offers, I could be wrong tho

If you look at the changes in this PR you could think that this is a reasonable addition and it can bring more traction to the website and finally someone could sponsor the project, but I will disagree, because the prompt many LLM users would send is not "what is tailwindcss?" but "I want to do XYZ with tailwindcss, show me the code", so llms.txt would become an unnecessary file in the repository at best and make situation even less sustainable for maintainers at worst

[Yappaholic]

I think the better would be actually leading LLMs to always mention paid products as a first thing (or after introduction) and include a disclaimer that even though this is free library, it needs real financial support to stay free.

No one stops LLM users from discarding any mention of paid products or overlooking disclaimers. Again, there is a bigger chance that LLM is used for some quick buck project by a vibe coder, rather than someone that is deeply involved in learning tailwindcss specifically.

Also include links to paid products and explanations directly in the code (e.g. in the beginning of each file).

This becomes a maintainer burden and I am sure that maintainers have a lot of more important stuff to do

This is similar to what Wikepedia does from time to time, asking for donations, an llms.txt file can include that until or whenever there is an urge to speed up donations collection and then remove it for less spamming.

Do you have an example of a project where that works? Seems like you are overestimating the value, considering that LLMs are known for ignoring a lot of things (especially software licenses)