
Shadcn
Wire json-render catalogs and React registries to 36 Radix-based shadcn/ui components instead of reinventing UI bindings.
Overview
shadcn is an agent skill for the Build phase that maps json-render catalogs to 36 Radix-and-Tailwind shadcn/ui component definitions and React implementations.
Install
npx skills add https://github.com/vercel-labs/json-render --skill shadcnWhat is this skill?
- 36 pre-built shadcn/ui components on Radix UI and Tailwind CSS for json-render
- Split entry points: @json-render/shadcn/catalog (server-safe schemas) and @json-render/shadcn (React implementations)
- Explicit pick-list pattern—import only the component definitions your catalog needs, not a blind spread of all 36
- defineCatalog + defineRegistry pairing documented for Card, Stack, Heading, Button, Input and the rest of the set
- Aligns with json-render schema from @json-render/react/schema for typed UI trees
- 36 shadcn/ui components
- 2 package entry points (catalog vs React)
Adoption & trust: 1.2k installs on skills.sh; 15k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You are generating UI via json-render but lack a curated, typed bridge to real shadcn/ui components on both server catalog and client registry sides.
Who is it for?
Indie SaaS and agent-UI builders already on json-render who want standard shadcn controls without custom wrappers for every primitive.
Skip if: Teams not using json-render, native mobile UI, or backends with zero React front end.
When should I use this skill?
Working with @json-render/shadcn, adding standard UI components to a json-render catalog, or building web UIs with Radix and Tailwind shadcn components.
What do I get? / Deliverables
You import only the needed shadcn definitions and matching React components into defineCatalog and defineRegistry for renderable UI trees.
- Typed catalog component definitions
- Matching React component registry entries
Recommended Skills
Journey fit
How it compares
Component binding package for json-render—not a doc-updater like Context7 or an image juxtaposition workflow like anti-render.
Common Questions / FAQ
Who is shadcn for?
Developers shipping json-render-driven web UIs who want Radix-based shadcn components with separate server catalog and client registry exports.
When should I use shadcn?
During Build frontend work when adding @json-render/shadcn to a catalog, registering standard UI nodes, or scaffolding agent-rendered dashboards and forms.
Is shadcn safe to install?
Check the Security Audits panel on this Prism page and verify the @json-render/shadcn package source and versions in your lockfile before production use.
SKILL.md
READMESKILL.md - Shadcn
# @json-render/shadcn Pre-built shadcn/ui component definitions and implementations for json-render. Provides 36 components built on Radix UI + Tailwind CSS. ## Two Entry Points | Entry Point | Exports | Use For | |-------------|---------|---------| | `@json-render/shadcn/catalog` | `shadcnComponentDefinitions` | Catalog schemas (no React dependency, safe for server) | | `@json-render/shadcn` | `shadcnComponents` | React implementations | ## Usage Pattern Pick the components you need from the standard definitions. Do not spread all definitions -- explicitly select what your app uses: ```typescript import { defineCatalog } from "@json-render/core"; import { schema } from "@json-render/react/schema"; import { shadcnComponentDefinitions } from "@json-render/shadcn/catalog"; import { defineRegistry } from "@json-render/react"; import { shadcnComponents } from "@json-render/shadcn"; // Catalog: pick definitions const catalog = defineCatalog(schema, { components: { Card: shadcnComponentDefinitions.Card, Stack: shadcnComponentDefinitions.Stack, Heading: shadcnComponentDefinitions.Heading, Button: shadcnComponentDefinitions.Button, Input: shadcnComponentDefinitions.Input, }, actions: {}, }); // Registry: pick matching implementations const { registry } = defineRegistry(catalog, { components: { Card: shadcnComponents.Card, Stack: shadcnComponents.Stack, Heading: shadcnComponents.Heading, Button: shadcnComponents.Button, Input: shadcnComponents.Input, }, }); ``` > State actions (`setState`, `pushState`, `removeState`) are built into the React schema and handled by `ActionProvider` automatically. No need to declare them. ## Extending with Custom Components Add custom components alongside standard ones: ```typescript const catalog = defineCatalog(schema, { components: { // Standard Card: shadcnComponentDefinitions.Card, Stack: shadcnComponentDefinitions.Stack, // Custom Metric: { props: z.object({ label: z.string(), value: z.string(), trend: z.enum(["up", "down", "neutral"]).nullable(), }), description: "KPI metric display", }, }, actions: {}, }); const { registry } = defineRegistry(catalog, { components: { Card: shadcnComponents.Card, Stack: shadcnComponents.Stack, Metric: ({ props }) => <div>{props.label}: {props.value}</div>, }, }); ``` ## Available Components ### Layout - **Card** - Container with optional title, description, maxWidth, centered - **Stack** - Flex container with direction, gap, align, justify - **Grid** - Grid layout with columns (number) and gap - **Separator** - Visual divider with orientation ### Navigation - **Tabs** - Tabbed navigation with tabs array, defaultValue, value - **Accordion** - Collapsible sections with items array and type (single/multiple) - **Collapsible** - Single collapsible section with title - **Pagination** - Page navigation with totalPages and page ### Overlay - **Dialog** - Modal dialog with title, description, openPath - **Drawer** - Bottom drawer with title, description, openPath - **Tooltip** - Hover tooltip with content and text - **Popover** - Click-triggered popover with trigger and content - **DropdownMenu** - Dropdown with label and items array ### Content - **Heading** - Heading text with level (h1-h4) - **Text** - Paragraph with variant (body, caption, muted, lead, code) - **Image** - Image with alt, width, height - **Avatar** - User avatar with src, name, size - **Badge** - Status badge with text and variant (default, secondary, destructive, outline) - **Alert** - Alert banner with title, message, type (success, warning, info, error) - **Carousel** - Scrollable carousel with items array - **Table** -