Skip to content

[feat]: Config-first workflow for existing shadcn/ui projects #9488

@agustinusnathaniel

Description

@agustinusnathaniel

Feature description

Problem

The Create page is excellent for onboarding new projects, but it currently optimizes almost entirely for greenfield setups.

At the moment, it:

  • scaffolds a full project, or
  • redirects configuration to v0

This makes it hard to iterate on configuration for existing projects.

There is still a /themes page, but:

  • it’s no longer discoverable from the main navigation
  • it only outputs CSS variables
  • it does not cover other configuration options now available in the Create page (library choice, style, etc)

As a result, configuration is split across two places, and only one of them is accessible without scaffolding a new project.

Current Workflow Friction

For existing projects, iterating on configuration usually means:
1. scaffolding a new project via the Create page
2. copying components.json and CSS variables
3. pasting them back into the existing project
4. regenerating components via the CLI

This works, but adds unnecessary friction for teams already using shadcn/ui who want to experiment or refine design decisions.

Proposed Improvement

Introduce a configuration-first workflow alongside project scaffolding.

Ideally, the Create page would allow users to:

  • configure theme, CSS variables, library, and style
  • export those settings in a reusable format
  • components.json
  • CSS variables
  • other relevant config
  • apply them directly to an existing project
  • then let the shadcn CLI regenerate components based on the updated config

This could be implemented via:

  • an “Export config” option in the Create page, or
  • a dedicated “Reconfigure existing project” flow

Why This Matters

Supporting both:

  • new project scaffolding, and
  • existing project reconfiguration

would better reflect real-world usage, where teams often need to iterate on design and configuration without recreating their project from scratch.

Affected component/components

No response

Additional Context

Additional details here...

Before submitting

  • I've made research efforts and searched the documentation
  • I've searched for existing issues and PRs

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions