Skip to main content
Iuliiagav
Iuliiagav
New Member
September 27, 2026
Question

Forking the PrimeVue Figma UI Kit as our product design system — valid in practice?

Hi everyone,

Our product is moving to PrimeVue 4.0.0, and I'd like a reality check on our design system setup.

Current approach: we copy individual components from the PrimeVue Figma Kit into our design system and keep them linked to the PrimeVue library.

What I'm proposing instead: duplicate the whole PrimeVue Figma Kit and use it as our own separate design system library.

  • All PrimeVue components stay unchanged.
  • The main customization is our own primitive colors, plus adjusting PrimeVue settings to match our design.
  • We keep PrimeVue variables as they are. Our own variables go into the custom folder in PrimeVue's variables.
  • Our custom components and icons have separate names, agreed with our developer.

Updates: when a new PrimeVue Figma file comes out, I'd compare it with ours (with AI help if possible), then move the needed changes manually. If the changes are too big, I'd copy our custom parts into the new file instead.

Is this a valid approach in practice? Has anyone worked this way with PrimeVue or a similar vendor kit?

Thanks!

1 reply

JesseHilton
JesseHilton
New Participant
September 30, 2026

Yes, this is a practical approach. I’d treat the duplicated PrimeVue kit as a maintained fork and keep your custom variables/components clearly separated from PrimeVue’s originals.

PrimeVue recommends using the Custom collection for your own variables, while updates to customized components may require manual review.

Your update process—compare the new kit, migrate required changes, and test before replacing the old version—should work well. Just document your customizations so future PrimeVue updates are easier to manage.

    Terms & ConditionsAccessibility statement