It is very probable that if you ask a frontier model for a custom dropdown, you’ll get a nested div monster with a JavaScript library on top, instead of a plain appearance: base-select. Ask it for any UI at all, and there is a fair chance it arrives in a thick coat of Tailwind utility classes, whether your project uses Tailwind or not. Back in September I wrote about Tailwind being installed over 110 million times a week while its own business struggled because agents were writing the classes for everyone (I suspect not all of those installs were entirely voluntary, so please wink if you are in distress).
Chrome’s answer to the legacy-pattern habit is Modern Web Guidance, now stable at 1.0: a set of skills you install into your coding agent (npx modern-web-guidance@latest install) that injects short, task-scoped guides based on what you are asking for, whatever the model or harness.
Version 1.0 has 200-plus guides across accessibility, performance, security, privacy, forms and UX, each reviewed by a domain expert, and it is now a cross-browser effort with Firefox and Edge joining Chrome. Guides carry Baseline compatibility data and fallbacks, so you get @supports queries and polyfills matched to your browser targets rather than Chrome-only code. A legacy-scan command looks for safe modernisation spots in an existing codebase.
Whether it also cures the reflex of reaching for Tailwind on every div, the release notes do not say. You can always try the famous prompt “One shot, no bugs or Tailwind bro”.