Migrate legacy themes to Design Systems 2.0

Legacy themes, the colors, fonts, radius, and shadows you set in the legacy theme editor, will be retired on November 30, 2026. You can no longer create new legacy themes. Move each theme you still use to Design Systems 2.0, which saves your design system as a skill you can attach to any chat.

This guide covers legacy themes only. Template-based legacy design systems aren't part of this change.

Get your theme's CSS

  1. Start a new chat and select your legacy theme from the design system menu in the prompt toolbar.
  2. Ask v0 for a simple page, such as a dashboard.
  3. When it's done, open the code and copy two files:
    • app/globals.css, which holds your theme's colors, radius, and shadows as CSS variables.
    • app/layout.tsx, which loads your theme's fonts.

Import it as a Design Systems 2.0 skill

  1. Open the Design Systems page and select New.
  2. Attach the two files, or paste them into Notes.
  3. In Notes, tell v0 this is a shadcn/ui theme with no component package of its own, and give it a name.
  4. Submit the form. v0 builds a small starter app with your theme and pauses for your review.
  5. Check the colors in light and dark mode, the fonts, and the corner radius. Ask v0 to fix anything that's off, then approve to save the skill.

See Design Systems 2.0 for the full import flow.

Use the new design system

Select the saved design system from the prompt toolbar in new chats, the same way you selected the legacy theme. Team owners can also set it as the team default.

Existing chats keep the code they already have. Your theme's styles are already in their app/globals.css, so they keep working after legacy themes are retired.