For reference, Tailwind 4 will not read in config files by default (which is the older behavior) - the encouraged practice is to configure customizations directly in the CSS file where you import Tailwind itself.
Not sure how o3 is generally at coding, but this kind of meta information works well for me to avoid version missmatches with Claude and Gemini
It's kinda important that the AI finds the issues itself so it can properly document it in her own words.
This won't be 100%, but that'll be the companies who're able to hire somebody to parse the problems that arise. Without that engineer, they'll be doing what OP calls 'vibe coding', meaning they'll neither understand nor be able to fix when the whole thing blows up.