json-render-shadcn

Provide pre-built shadcn/ui components for json-render in React/Next.js apps.

1|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/supersterling/primus --skill json-render-shadcn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: json-render-shadcn
Source: https://github.com/supersterling/primus/tree/main/.agents/skills/json-render-shadcn
Command: npx skills add https://github.com/supersterling/primus --skill json-render-shadcn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-built shadcn/ui components for json-render remove the friction of building consistent UIs by providing ready-to-use primitives and patterns that align with Radix UI and Tailwind.

Core Features & Use Cases

  • Two Entry Points: @json-render/shadcn/catalog for catalog schemas (server-safe) and @json-render/shadcn for React implementations.
  • Ready-made UI building blocks: Card, Stack, Heading, Button, Input, and more, built on Radix UI + Tailwind CSS.
  • Use Case: Rapidly compose dashboards and JSON-driven interfaces with consistent styling and behavior across apps.

Quick Start

Install and integrate the pre-built shadcn/ui components into your json-render project to enable ready-made UI components.

Frequently Asked Questions about json-render-shadcn

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I use pre-built shadcn/ui components in a json-render app?

Use pre-built shadcn/ui components in a json-render app by installing this skill to access ready-made UI primitives like Card, Button, and Input, built on Radix UI and Tailwind CSS. It provides two entry points for server-safe schemas and React implementations to accelerate UI development.

What is the difference between the @json-render/shadcn/catalog and @json-render/shadcn entry points?

The @json-render/shadcn/catalog entry point provides server-safe catalog schemas, while the @json-render/shadcn entry point provides the actual React implementations. This separation allows json-render apps to define UI components on the server and render them on the client.

Can I use shadcn/ui components for server-side rendering in Next.js?

Yes, you can use these shadcn/ui components for server-side rendering in Next.js. The skill exposes server-safe catalog definitions through the @json-render/shadcn/catalog entry point, enabling JSON-driven interfaces to render consistently across server and client environments.

Do I need Radix UI and Tailwind CSS to use these json-render components?

Yes, Radix UI and Tailwind CSS are required as the pre-built shadcn/ui components are built directly on top of them. This foundation ensures consistent styling and accessible behavior for UI building blocks like Stack, Heading, and Input within json-render apps.

What's the best way to rapidly compose dashboards with shadcn/ui in a React project?

The best way to rapidly compose dashboards in a React project is using pre-built shadcn/ui components for json-render. They provide ready-made UI building blocks that align with Radix UI and Tailwind, removing the friction of building consistent JSON-driven interfaces.

What UI primitives are available for json-render interfaces?

Available UI primitives for json-render interfaces include Card, Stack, Heading, Button, Input, and more. These ready-to-use building blocks expose catalogable component definitions to accelerate UI development and ensure consistent styling across apps.