@mia @westbrook I guess going preludeless guarantees zero naming clashes.Personally, I’m on the side of naming things and treating clashes as silly mistakes, but many larger companies have relied on CSS-in-JS auto-generating class names, so a well-performing preludeless solution would remove the friction in migrating away from that complexity/overhead to a no-build solution.