Manage component variants

Consolidate the card component into three variants: compact, default, and expanded. Migrate all product list and dashboard instances to the default variant, update overrides for image aspect ratios, and ensure interactions for expand/collapse map to the expanded state. Finish migration by Monday and report any frames that reference a detached master or a renamed variant.

Before I reorganize card variants, make it easy for PMs and engineers to approve the change. Show a matrix of where compact versus default currently appears, surface places where local overrides change padding or shadows, and flag any components that rely on the old expanded layout for JS hooks. Call out the complexity cost of every instance that will need manual adjustment.

I merged three card variants into default and compact, and the analytics dashboard now shows collapsed spacing on several rows. I’m not sure if the issue is a padding override or that the instance accidentally switched to compact. What are the likely causes, what quick view should I open to diagnose the problematic instances, and how do I revert only those instances without undoing the whole merge?

Over the past six months we keep refactoring component variants and each time it creates new visual regressions and extra QA cycles. Is the pattern coming from poor naming, insufficient migration checks, or a lack of stable tokens? Recommend a practical convention and one enforcement step we can add to our release checklist so variant churn stops costing us sprints.