Duplicate and iterate screens

Duplicate the onboarding screens from the current file into the working branch, create a variation for the personalized headline and the price toggle, and rename each new frame with the pattern Onboard — Variant — Step number. Link the new frames into the prototype flow so QA can test both variants, and leave a pinned comment for Max in engineering to confirm the API placeholder.

Before I spin another iteration, make this duplication frictionless: copy the hero, form, and confirmation frames into a single page called Experiments, keep components linked to the design system, and mark variants with a visible badge. Highlight where spacing or token overrides break component reuse so I can avoid duplicate fixes later.

I copied three onboarding variants for a pricing test and the new frames ended up across three different pages; the navigation prototype points to old frames. I don't know which links are safe to update without breaking the live demo. What's the safest quick approach to consolidate the variants and restore the prototype links before Wednesday's test?

Every sprint we duplicate screens for experiments and later spend days hunting versions, relinking prototypes, and reconciling spacing. Are we failing at naming, page structure, or variant discipline, and what single routine would prevent this from eating a full day each sprint?