Skip to main content
skill CX Codex

json-render-shadcn — Claude Code skill for UI components

json-render-shadcn is a Claude Code skill that adds ready-made shadcn/ui components to json-render catalogs and web UIs. It activates for work with @json-render/shadcn.

Apache-2.0 257 installs ★ 19,802 updated 2026-10-24

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add vercel-labs/json-render --skill json-render-shadcn -a claude-code
Open on GitHub

What json-render-shadcn does

json-render-shadcn supplies definitions and React implementations for 36 components built with Radix UI and Tailwind CSS. The set covers layouts, navigation, dialogs, forms, tables, and feedback elements. Import definitions from @json-render/shadcn/catalog when building a catalog; use @json-render/shadcn for React implementations.

Select only the components used by the app, and add custom ones alongside them. The /catalog entry point has no React dependency, so it can generate prompts server-side. Components use Tailwind CSS classes, which means Tailwind must be configured in the app.

What it helps with

  • add standard shadcn/ui components to a json-render catalog
  • connect component schemas to React implementations
  • extend the standard set with custom components
  • generate prompts server-side without a React dependency

Example prompts for the agent

  • Add Card, Stack, and Button from @json-render/shadcn to my json-render catalog.
  • Build a React registry for the selected @json-render/shadcn components.
  • Add a custom Metric beside the standard catalog components.

How to install json-render-shadcn

1Skills CLI (Vercel)

npx skills add vercel-labs/json-render --skill json-render-shadcn -a claude-code

2Manually: put the files in place

~/.claude/skills/json-render-shadcn/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/json-render-shadcn/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about json-render-shadcn

How do I install json-render-shadcn in Claude Code?

Run npx skills add vercel-labs/json-render --skill json-render-shadcn -a claude-code. The skill file is at ~/.claude/skills/json-render-shadcn/SKILL.md.

What does json-render-shadcn do?

It provides shadcn/ui component definitions for json-render catalogs and React implementations for registries. The set contains 36 components.

What does json-render-shadcn require?

The app needs Tailwind CSS configured because the components use its classes. Catalog definitions and React implementations come from @json-render/shadcn/catalog and @json-render/shadcn.

Source text

SKILL.md · Apache-2.0
---
name: json-render-shadcn
description: Pre-built shadcn/ui components for json-render. Use when working with @json-render/shadcn, adding standard UI components to a catalog, or building web UIs with Radix UI + Tailwind CSS components.
---

# @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** - Data table with columns (string[]) and rows (string[][])

### Feedback
- **Progress** - Progress bar with value, max, label
- **Skeleton** - Loading placeholder with width, height, rounded
- **Spinner** - Loading spinner with size and label

### Input
- **Button** - Button with label, variant (primary, secondary, danger), disabled
- **Link** - Anchor link with label and href
- **Input** - Text input with label, name, type, placeholder, value, checks
- **Textarea** - Multi-line input with label, name, placeholder, rows, value, checks
- **Select** - Dropdown select with label, name, options (string[]), value, checks
- **Checkbox** - Checkbox with label, name, checked, checks, validateOn
- **Radio** - Radio group with label, name, options (string[]), value, checks, validateOn
- **Switch** - Toggle switch with label, name, checked, checks, validateOn
- **Slider** - Range slider with label, min, max, step, value
- **Toggle** - Toggle button with label, pressed, variant
- **ToggleGroup** - Group of toggles with items, type, value
- **ButtonGroup** - Button group with buttons array and selected

## Built-in Actions (from `@json-render/react`)

These are built into the React schema and handled by `ActionProvider` automatically. They appear in prompts without needing to be declared in the catalog.

- **setState** - Set a value at a state path (`{ statePath, value }`)
- **pushState** - Push a value onto an array (`{ statePath, value, clearStatePath? }`)
- **removeState** - Remove an array item by index (`{ statePath, index }`)
- **validateForm** - Validate all fields, write `{ valid, errors }` to state (`{ statePath? }`)

## Validation Timing (`validateOn`)

All form components support `validateOn` to control when validation runs:
- `"change"` — validate on every input change (default for Select, Checkbox, Radio, Switch)
- `"blur"` — validate when field loses focus (default for Input, Textarea)
- `"submit"` — validate only on form submission

## Important Notes

- The `/catalog` entry point has no React dependency -- use it for server-side prompt generation
- Components use Tailwind CSS classes -- your app must have Tailwind configured
- Component implementations use bundled shadcn/ui primitives (not your app's `components/ui/`)
- All form inputs support `checks` for validation (type + message pairs) and `validateOn` for timing
- Events: inputs emit `change`/`submit`/`focus`/`blur`; buttons emit `press`; selects emit `change`/`select`

© vercel-labs · Apache-2.0 · vercel-labs/json-render

Similar skills

All skills for Frontend and UI →

From the same set30

The whole set →
shadcn-svelte shadcn-svelte is a Claude Code skill for assembling interfaces and configuring schema catalogs for json-render. It includes 36 components built on Svelte 5 and Tailwind CSS. CX Codex +1 1,200installs yaml Streaming YAML parser for json-render that turns code fences into JSON Patch. Built for progressive rendering and surgical spec edits via stream. CX Codex +1 1,100installs solid Skill to render JSON-specs into reactive SolidJS components. Use it when building UI catalogs, wiring providers, or debugging Solid reactivity patterns. CX Codex +1 1,100installs xstate Teaches AI assistants how to hook @xstate/store into json-render's state interface. Useful when driving dynamic UI layouts with an XState atom. CX Codex +1 1,100installs tanstack-start Gives the agent a recipe for building TanStack Start pages from a JSON spec, wiring routes, layouts and SSR loaders into the router. CX Codex +1 245installs devtools-react devtools-react is a skill that adds a developer panel to React json-render apps for spec inspection, state editing, and action and stream timelines. CX Codex +1 215installs devtools-vue This Claude Code skill adds the json-render inspector panel to a Vue app. It activates when configuring or troubleshooting @json-render/devtools-vue. CX Codex +1 165installs devtools-svelte The devtools-svelte Claude Code skill helps connect the json-render devtools inspector to a Svelte app. It activates for setup and troubleshooting tasks involving specs, state, actions, streams, catalogs, or DOM picking. CX Codex +1 158installs

Project sponsors

Companies that keep this analytics open