Keep your agents on the shadcn/ui setup you already have.

Ask an agent for a date picker and it may install a new library, switch primitives or pull in a second icon set. A shadcn DESIGN.md names your components, the primitives under them and your icons, so Cursor, Claude Code and Codex reuse what’s already there.

Create your DESIGN.md

What agents add without a decision

Pull requestafter a week of prompts

+ @mui/x-date-pickers

+ @radix-ui/react-dialog

+ react-icons

+ components/Modal.tsx

+ components/ui/dialog-2.tsx

What your DESIGN.md tells them

DESIGN.mdread by your agents

## Components

Library shadcn/ui

Path @/components/ui

Base Base UI

## Icons

Set Lucide, outline

Reuse these. Don’t install another library.

Each addition works on its own. Together they leave you with two ways to open a dialog and three icon styles on one screen.

Agents can’t tell which components are yours.

shadcn/ui copies components into your repository, so to an agent they look like any other React files. It doesn’t know they are your design system. Asked for something new, it writes another dialog, adds Radix next to Base UI, or imports icons from a package you never chose.

None of that breaks the build, which is why it gets merged. A shadcn design system for Cursor or Claude Code needs the decision written down: which library, which primitives, which icons, and a rule to reuse them before adding anything.

One file, the decisions agents need.

01

Your components and where they live

shadcn/ui and its path, such as @/components/ui, so agents extend the components you have before writing new ones.

02

Base UI or Radix

The primitives your shadcn/ui components are built on, so agents follow the same APIs and never mix the two.

03

One icon set, one style

Lucide, Phosphor, Heroicons or your own set, with the style you use for default and active states, so icon families don’t mix.

Built for the way agents read a project.

  1. 1

    Start from your website.

    Onefold recognizes shadcn/ui and icon sets like Lucide on your live site. Confirm them, pick Base UI or Radix and add your component path.

  2. 2

    Get tokens for your Tailwind theme.

    Your colors, dark theme, type, corners and shadows come as CSS variables and a Tailwind theme to paste into your stylesheet.

  3. 3

    Point every agent at DESIGN.md.

    Keep it in the repository and mention it in AGENTS.md or your Cursor rules. The next component request starts from the ones you have.

New screens, built from the components you have.

Tell Onefold your shadcn/ui setup once. Every agent after that builds with the components and icons already in your repository.
Start free