Thinking out loud:
This might be too late (especially the AI angle you mentioned), but why not freeze Tailwind CSS per major version and charge for updates, similar to Laravel Spark?
If people want new templates/components or component touch-ups, they pay again (or an upgrade fee).
Slightly off-topic: I recently built a POC with MCP tools + Stripe. If ChatGPT invoked a tool, it was billed per invocation.
Just an idea (not sure if it’s viable): put all Tailwind CSS knowledge/markdown behind an MCP server with a subscription? Basically, building your own @shadcn.
Been playing with MCP tools on top of OpenAI and ChatGPT lately. Wiring up real APIs, keeping tools small and focused, and letting the AI decide what to call next instead of hard-coding flows. This is starting to feel way more practical than I expected.
Been experimenting with MCP lately…
Wild how fast an AI tool turns into “AI, can you handle this for me?” once it gets access to real systems.
Might have pushed things a bit too far with this one 👀
@jamesm Call apple support, they will setup an express replacement. You will receive a new one first and then you send this one back. They have special processes for this.
@wesbos I prefer a MacBook without stickers because of the ecstatics. But I also understand that people like to add personality to their things.
I think it’s just a matter of taste 🤷🏻♂️