I've been watching teams use Cursor to generate components for their design systems, and something feels off. You get fast output, sure. But the generated code has zero consideration for versioning, deprecation paths, or breaking changes. It's all just latest patterns copied from whatever it scraped.

Then you've got junior devs committing these components thinking they're following the system, when really they're creating technical debt at scale. The tool doesn't understand that a button component in v2.0 needs a migration story if you change the API.

Is it just me or are we trading short-term velocity for long-term fragmentation?