Shadcn design system generators: do you need a theme, a system, or an agent handoff?

First decide what artifact you need. A visual theme changes values such as colors, fonts, radius, and shadows. An implementation-ready design system connects those values to semantic roles and usage rules. A coding-agent handoff puts the rules and tokens where an agent can read or install them. These categories overlap. They describe the delivered artifact, not its quality.

The observed tools use similar labels for different outputs. Official shadcn/ui provides customizable open-code components and a common composable interface. Shadcn Design generates light and dark theme CSS from one primary color. Shadcn Studio adds a larger theme editor with controls, previews, presets, and installation routes. Identity Forge packages semantic tokens with written design guidance and agent-delivery artifacts.

The comparison uses four evidence states. "Documented" means a frozen source establishes the capability. "Partial" means the source establishes a narrower capability, with the limit stated. "Undocumented" means the available evidence does not establish it, which is not proof of absence. "Not applicable" is for a field that does not fit the artifact.

• Semantic roles: undocumented. The cited pages establish customizable components and open code, but not a semantic-token output contract.
• Light and dark output: undocumented. The homepage includes light and dark interface images, but this does not document the contents of a generated or distributed theme.
• Typography controls: undocumented. The cited evidence does not establish typography controls as part of an output contract.
• Spacing and layout guidance: undocumented. The cited evidence does not establish exported spacing or layout rules.
• Component guidance: partial. The sources document customizable open-code components and a common composable interface, but not exported design-usage rules.
• Previews: partial. The homepage shows representative interface surfaces, but the evidence does not establish an interactive theme or export-preview workflow.
• Export or delivery form: documented. The documentation describes open component code distributed through a flat-file schema and CLI.
• Registry delivery: undocumented. The cited excerpts do not establish that delivery route.
• Agent-readable documentation: partial. The introduction says AI models can read the open code and consistent API, but it does not establish a separate design-rules document.

• Semantic roles: undocumented. The page documents generated CSS variables but does not expose enough of the output to verify a meaning-based role set.
• Light and dark output: documented. The generator states that it creates both modes from one primary color.
• Typography controls: documented. The page offers separate body and heading font choices.
• Spacing and layout guidance: undocumented. The page does not establish written spacing or layout rules.
• Component guidance: undocumented. Styled preview screens do not establish exported component-usage instructions.
• Previews: documented. The generator provides live previews across landing pages, dashboards, and charts.
• Export or delivery form: documented. It copies Tailwind v4 CSS variables covering colors, fonts, radius, and shadows.
• Registry delivery: undocumented. The cited page does not establish registry installation for the generated theme.
• Agent-readable documentation: undocumented. The evidence does not establish a design brief or another rules document delivered with the theme.

• Semantic roles: partial. The generator documents named controls including primary and destructive, but the evidence does not establish a complete semantic-role inventory.
• Light and dark output: documented. The generator documents shadcn theme customization and export within its theme workflow.
• Typography controls: documented. Its documentation includes a typography tab.
• Spacing and layout guidance: undocumented. The cited pages do not establish exported spacing or layout rules.
• Component guidance: undocumented. Real-time previews show visual effects, but the evidence does not establish written component-usage rules in the export.
• Previews: documented. The generator provides real-time previews for components, blocks, and templates.
• Export or delivery form: documented. The sources describe copied output, manual setup, and a registry route.
• Registry delivery: documented. The documentation identifies registry installation as a Pro option and manual setup as another route.
• Agent-readable documentation: undocumented. AI-assisted theme generation is documented, but that is different from exporting rules for another coding agent.

• Semantic roles: documented. Identity Forge documents 28 meaning-based color roles in both modes and CSS, Tailwind, and DTCG exports.
• Light and dark output: documented. The semantic-token guide and public kit evidence describe separate light and dark values.
• Typography controls: documented. Public kit data includes type roles, families, weights, and a scale label.
• Spacing and layout guidance: documented. The DESIGN.md guide says its generated briefs include spacing and layout rules.
• Component guidance: documented. The DESIGN.md guide describes component treatments and explicit usage constraints in the written brief.
• Previews: documented. Public kit pages show kits on representative interface surfaces.
• Export or delivery form: documented. The product sources describe DESIGN.md plus CSS, Tailwind, shadcn, and DTCG token formats.
• Registry delivery: documented. First-party guides document shadcn registry installation alongside CLI and MCP routes.
• Agent-readable documentation: documented. DESIGN.md supplies written guidance tied to the kit tokens.

There is no universal winner in this map. A focused generator is the better fit when an existing shadcn project only needs new visual variables and a preview. Broader rules become useful when developers or agents must make new interface decisions without repeatedly guessing the intended system.

Run this worksheet on an actual export. It is a reader-performed inspection, not a benchmark of the tools above. Use the same sample content for every candidate so that differences come from the artifacts rather than different test screens.

• Test content: page background, standard and muted text, primary and destructive actions, a bordered input, a selected control, and a keyboard-focus state.
• Inspect: record whether names describe purpose, such as background, foreground, primary, destructive, border, and ring, or only visual values. Pair every inspected light role with its dark counterpart.
• Failure condition: a component needs a raw hue because no suitable role exists, a light role has no dark counterpart, or destructive and focus states borrow an unrelated role.

• Test content: primary and secondary buttons, disabled and error inputs, cards, popovers, navigation, a table with selected and hover rows, and a chart with several series.
• Inspect: trace visible colors to exported roles. Check foreground and background pairs, borders, focus indicators, overlays, selected states, and chart-series roles.
• Failure condition: the screen requires improvised values, one role serves conflicting purposes, or a state becomes indistinguishable in one mode. Record this as a gap in the candidate export, not proof about everything the tool can support.

• Test content: page title, section heading, body copy, form label, helper text, table values, and a code or identifier field when relevant.
• Inspect: note whether the artifact maps families, weights, sizes, line heights, and tracking to named roles or only supplies font-family values.
• Failure condition: implementers must invent weights or treatments, a role refers to an unavailable weight, or the exported values conflict with the written instructions.

• Test content: narrow form, card grid, dense table, page header, and responsive navigation.
• Inspect: look for rules covering content width, gutters, section spacing, component density, grid behavior, and responsive changes. Check whether those rules remain available after export or installation.
• Failure condition: a preview implies a layout that the artifact never describes, the export drops the written rules, or another implementer must infer density and structure from images alone.

A coding agent can use only the guidance that reaches its working context. Before calling an export an agent handoff, answer these questions for the actual artifact and project.

• Framework assumptions: Which shadcn, Tailwind, framework, or component-library context does it expect? Record versions when the source supplies them.
• Installation route: Does the project receive copied CSS, component code, a CLI-applied bundle, a registry item, an MCP-delivered artifact, or a combination?
• Token-to-component mapping: Can the implementer identify the roles for buttons, inputs, cards, popovers, navigation, tables, charts, destructive actions, and focus states?
• Typography choices: Are the permitted families, roles, and available weights explicit?
• Spacing and layout rules: Does the handoff describe page and component arrangement, or only theme values?
• Usage constraints: Does it explain when a treatment should or should not be used?
• Known gaps: Which values or rules still require a designer, developer, or agent to decide?

A DESIGN.md helps only if the workflow puts it where the target agent reads it. A registry item can install values without necessarily putting written rationale into the same context. Inspect both paths instead of assuming that one installed artifact carries the complete handoff.

The public Ambient Sage kit is a bounded example of a broader handoff. Its published data lists 28 semantic color tokens for light and dark modes. The page also provides a DESIGN.md and identifies installation paths including the Identity Forge CLI and shadcn registry. These are observed properties of this kit, not evidence that its visual choices suit every product.

The published typography assigns Plus Jakarta Sans to heading and body roles at weights 400, 500, 600, and 700. JetBrains Mono has the mono role at weights 400, 500, and 700. The scale label is compact-product. The font project sources establish that the named families exist, but they do not show that this pairing, weight set, or scale is preferable for every implementation.

The public evidence identifies the artifact and its stated coverage. Adoption still requires inspection. Check whether the chosen export preserves all 28 roles in both modes, whether the project loads the listed weights, and whether DESIGN.md reaches the person or agent expected to follow it. Then trace the roles through the worksheet components. This article has not performed a comparative benchmark.

• Choose copied CSS when the task is a visual refresh and the project already has component, typography, spacing, and layout rules.
• Choose a theme editor or reusable preset when shadcn projects need consistent visual variables and previews, while broader product guidance exists elsewhere.
• Choose an implementation-ready design system when implementers need shared semantic roles plus explicit typography, spacing, layout, and component guidance.
• Choose an agent handoff when an AI builder must retain those decisions during implementation. Verify how both tokens and written rules enter its context.

Take one candidate export and run it through the worksheet before adding it to the project. The unresolved decisions will show whether the current artifact is sufficient or whether the work needs a broader handoff.

• The Foundation for your Design System - shadcn/ui: Shows customizable open-code components and representative light and dark interface surfaces.
• Introduction - shadcn/ui: Documents open code, composition, flat-file schema and CLI distribution, and an API readable by AI tools.
• Shadcn Theme Generator | Live Preview, Copy Theme CSS: Documents generation from one primary color, light and dark themes, font controls, radius presets, live previews, and Tailwind v4 CSS-variable output.
• Design Stunning UIs Faster with Shadcn Theme Generator: Documents presets, real-time customization, typography controls, named color controls, contrast validation, previews, and theme import or export.
• Shadcn Theme Generator Documentation: Documents theme controls, copying output, manual setup, and Pro registry installation.
• Identity Forge: Documents kits containing fonts, semantic tokens, spacing, DESIGN.md guidance, previews, and agent delivery paths.
• Ambient Sage Design Kit: Provides public evidence for the worked example's semantic tokens, typography roles and weights, compact-product scale label, DESIGN.md, exports, and installation targets.
• Semantic color tokens explained: Documents Identity Forge's 28 light and dark semantic roles and CSS, Tailwind, and DTCG export forms.
• How to generate a DESIGN.md (and what it is): Documents DESIGN.md coverage including design intent, token references, typography, spacing, layout, component treatments, motifs, and usage constraints.
• Design systems for AI coding agents: Documents delivery of tokens and DESIGN.md through MCP, CLI, and shadcn registry routes.
• Plus Jakarta Sans: Provides the project source for the Plus Jakarta Sans family named in the Ambient Sage example.
• JetBrains Mono: Provides the project source for the JetBrains Mono family named in the Ambient Sage example.