Component registry

This is the shadcn pattern: registry-as-source-code, not registry-as-package. You own ejected components; bumping @cimplify/sdk no longer updates them.

List

# All ejectable components
cimplify list

# Filter (pipe to grep)
cimplify list | grep selector
cimplify list | grep card

Add

# Eject a single component into ./components/
cimplify add cart-summary
# → writes ./components/cart-summary.tsx

cimplify add variant-selector
cimplify add product-customizer

The CLI resolves the registry entry, copies its source (renaming imports as needed), and writes it under components/. Replace the SDK import in the page or layout that used the original component with the local copy.

When to eject

Example flow: restyle the cart drawer

cimplify add cart-drawer
# → ./components/cart-drawer.tsx

"use client";
import { CimplifyProvider } from "@cimplify/sdk/react";
import { CartDrawerProvider } from "@cimplify/sdk/react";
// import { CartDrawer } from "@cimplify/sdk/react";          // ← was
import { CartDrawer } from "@/components/cart-drawer";        // ← now

// ...

// Edit the JSX, swap the close button, change the empty-state copy,
// add a per-merchant "free shipping" banner, etc. The state machine, cart
// hooks, and onCheckout contract still flow through the SDK; you only own
// the rendering.
"use client";
import { useCart, useCartDrawer } from "@cimplify/sdk/react";
// ... (the ejected source)

What's in the registry

The registry mirrors the React SDK exports. Pages, customizers, cards, primitives: every non-trivial component has an entry. cimplify list is the source of truth; the table below groups the most-used ones.

Ejection golden rules

1. Read the ejected file end-to-end before editing.
2. Don't change the state shape or the cart payload contract; the customizer / cart pricing math has been iterated on heavily, and the mock will reject mismatched payloads.
3. Restyle via Tailwind classes / wrap nodes / add per-merchant copy.
4. Run bun run check:cart and bun run check:contract after.

Where next

• Component catalog Real names, props, examples.

• Hooks reference Drive ejected components from data hooks.

• CLI overview Full subcommand index.