Design responsive components

I need responsive button and card components that behave predictably across phone, tablet, and desktop breakpoints for our checkout flow. Build the variants so the label truncates with an ellipsis, tap targets are at least 44px, spacing compresses at tablet, and the primary button expands to full width on mobile. Before handing these to engineering, check states, token usage, and that auto-layout keeps paddings consistent.

Before I hand these to engineering, make it obvious what will break on resize. Surface the min and max widths, show how text wraps, call out any fixed pixel values, and add a quick demo frame that cycles phone/tablet/desktop so a PM or engineer can approve without guessing.

I moved the desktop card variant into the phone frame to test responsiveness and now icons and text overlap. The engineers expect components that resize without manual overrides and the PM will blame 'inconsistent tokens'. I don't know which constraints I broke or whether the issue is auto-layout, fixed widths, or a badly nested group. What's the most likely cause and the fastest fix to make this a reliable mobile variant?

Across multiple releases we recreate responsive rules for cards and buttons and waste time fixing spacing on each new component. I own the component library and want a habit that prevents this recurring cleanup. Where should I standardize tokens, naming, and utility frames so designers stop rebuilding constraints and engineers receive predictable components?