Install command
Provided
Generate React UI with v0 (Vercel): produce shadcn/ui and Tailwind CSS components and full Next.js pages from prompts, then refine and add them to your app with the shadcn CLI.
Open the source and read safety notes before installing.
Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.
Decision playbook
Signals are comparatively strong, but you should still validate source, privacy posture, and package provenance for your environment.
0
96
—
No baseline selected
No major trust-signal divergence detected in the current selection.
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Source provenance statusRequired
Marked as first-party.
Metadata reviewed
Registry metadata indicates a reviewed listing.
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Trust level risk gateRequired
Trust level does not block evaluation.
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Package verification flag
Package marked verified.
Checksum metadata
SHA-256 hash is present.
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
Baseline comparison available
No baseline peer selected yet.
Diverging trust signals identified
No major trust-signal divergence found.
Setup at a glance
Copy-ready — paste the snippet to get started.
Install command
Provided
Config snippet
Not provided
Copy snippet
Provided
Prerequisites
6 to clear
Platforms
6 listed
Difficulty
100/100
Adoption plan
Current risk score 0/100. Use staged verification before broader rollout.
Validate source and review signals before any execution.
Confirm source provenanceRequired
Source URL/provenance metadata is present.
Confirm metadata review state
Listing has review metadata.
Verify install payload
Install/config payload exists and can be inspected.
Confirm safety, privacy, and package integrity signals.
Review safety notesRequired
Safety notes are present.
Review privacy notesRequired
Privacy notes are present.
Verify package integrity metadata
Package verification/checksum metadata is available.
Adopt in controlled steps based on the selected plan.
Run in isolated sandbox firstRequired
Use a constrained sandbox and observe behavior across multiple tasks.
Roll out graduallyRequired
Roll out to a small cohort before wider usage.
Set monitoring and fallback
Define rollback path and monitor errors after adoption.
Evidence readiness
Required evidence gates are covered (6/6 signals complete).
Source repository/provenance is listed.
Required in this preset
Review metadata is present.
Required in this preset
Safety notes are present.
Required in this preset
Privacy notes are present.
Optional in this preset
Package integrity metadata is present.
Optional in this preset
Install payload is available.
Required in this preset
Required evidence gates are covered for this preset.
Decision timeline
6/6 steps complete with no blocking gaps for this preset.
triage
Source/provenance metadata is available.
triage
Review metadata is available.
verify
Safety notes are available.
verify
Privacy notes are available.
verify
Package integrity metadata is available.
rollout
Install payload is available.
No required blockers for this timeline preset.
Prerequisite readiness
6 prerequisites to line up before setup. Have accounts and credentials ready first.
Safety & privacy surface
2 safety and 1 privacy notes across 3 risk areas.
| Platform | Support | Install path |
|---|---|---|
| claude-code | Native | .claude/skills/<skill-name>/SKILL.md |
| codex | Native | .agents/skills/<skill-name>/SKILL.md |
| windsurf | Native | .windsurf/skills/<skill-name>/SKILL.md |
| gemini | Native | .gemini/skills/<skill-name>/SKILL.md or .agents/skills/<skill-name>/SKILL.md |
| cursor | Adapter | .cursor/rules/<skill-name>.mdc |
| cli | Manual | AGENTS.md or tool-specific context file |
'use client';
import { useState } from 'react';
import { Check } from 'lucide-react';
import { Button } from '@/components/ui/button';
import { Card, CardContent, CardFooter, CardHeader, CardTitle } from '@/components/ui/card';
import { Switch } from '@/components/ui/switch';
interface PricingTier {
name: string;
price: { monthly: number; annual: number };
features: string[];
cta: string;
popular?: boolean;
}
const tiers: PricingTier[] = [
{ name: 'Basic', price: { monthly: 9, annual: 90 }, features: ['5 projects', '1GB storage'], cta: 'Get Started' },
{ name: 'Pro', price: { monthly: 29, annual: 290 }, features: ['Unlimited projects', '10GB storage'], cta: 'Start Free Trial', popular: true },
];
export function PricingTable() {
const [isAnnual, setIsAnnual] = useState(false);
return (
<div className="py-12">
<div className="mx-auto max-w-7xl px-4">
<div className="text-center">
<h2 className="text-3xl font-bold">Simple, transparent pricing</h2>
<div className="mt-6 flex items-center justify-center gap-3">
<span>Monthly</span>
<Switch checked={isAnnual} onCheckedChange={setIsAnnual} />
<span>Annual</span>
</div>
</div>
<div className="mt-12 grid gap-8 lg:grid-cols-3">
{tiers.map((tier) => (
<Card key={tier.name} className={tier.popular ? 'border-primary shadow-lg' : ''}>
<CardHeader>
<CardTitle>{tier.name}</CardTitle>
</CardHeader>
<CardContent>
<div className="text-4xl font-bold">
${isAnnual ? tier.price.annual / 12 : tier.price.monthly}
</div>
<ul className="space-y-3">
{tier.features.map((feature) => (
<li key={feature} className="flex items-center gap-2">
<Check className="h-5 w-5 text-primary" />
<span>{feature}</span>
</li>
))}
</ul>
</CardContent>
<CardFooter>
<Button className="w-full" variant={tier.popular ? 'default' : 'outline'}>
{tier.cta}
</Button>
</CardFooter>
</Card>
))}
</div>
</div>
</div>
);
}Claude can generate React components and complete page layouts using v0 (Vercel) patterns. This skill covers prompt-driven component creation with shadcn/ui integration, Tailwind CSS styling, TypeScript, and Next.js App Router compatibility, then adding the generated components to your project with the shadcn CLI.
SKILL.md.SKILL.md content as reusable workflow instructions..gemini/skills/<skill-name>/SKILL.md or .agents/skills/<skill-name>/SKILL.md where supported..cursor/rules/*.mdc adapter for project rules.Required:
What Claude handles automatically:
Prompt: "Create a pricing table component with 3 tiers (Basic, Pro, Enterprise). Include monthly/annual toggle, feature lists with checkmarks, and prominent CTA buttons. Use shadcn/ui Card and Button components."
Claude will:
Prompt: "Build an analytics dashboard layout with sidebar navigation, header with search and notifications, stat cards showing KPIs, revenue chart using Recharts, and recent activity table. Make it fully responsive."
Claude will:
Prompt: "Create a user registration form with email, password, confirm password, and terms acceptance. Use react-hook-form with Zod validation. Show validation errors inline and disable submit until valid."
Claude will:
Prompt: "Design a hero section with gradient background, animated headline text, two CTA buttons, and three feature highlights below. Include subtle animations on scroll using framer-motion."
Claude will:
Be Specific About Components: Mention exact shadcn/ui components you want (Card, Button, Dialog, etc.) for consistent design system usage.
Request Mobile-First: Always specify "mobile-first responsive design" to ensure proper breakpoints and touch-friendly interactions.
Accessibility First: Ask for WCAG 2.2 Level AA compliance to get proper semantic HTML, ARIA labels, and keyboard navigation.
Server vs Client: Clarify if components need interactivity (Client Component with 'use client') or can be static (Server Component).
Animation Budgets: Request "performant animations" to get GPU-accelerated framer-motion transitions instead of heavy JavaScript.
Dark Mode: Specify "with dark mode support" to get proper color variable usage compatible with next-themes.
"Create a complete product details page with:
1. Image gallery with thumbnails (Client Component)
2. Product info section (title, price, description)
3. Add to cart button with quantity selector
4. Reviews section with star ratings
5. Related products carousel
6. Mobile-responsive layout with good UX
7. Loading states and error handling"
"Generate a set of reusable UI components:
1. CustomButton with variants (primary, secondary, outline, ghost)
2. CustomCard with header, content, footer slots
3. CustomInput with label, error message, help text
4. CustomSelect with search and multi-select
5. All components with TypeScript props, accessibility, and Storybook-ready"
"Build a data visualization dashboard component:
1. KPI summary cards at top (Revenue, Users, Conversion)
2. Line chart for 30-day trends using Recharts
3. Bar chart for category breakdown
4. Pie chart for traffic sources
5. Data table with sorting and filtering
6. Export to CSV functionality
7. Responsive grid that stacks on mobile"
"Create a complete authentication flow:
1. Login page with email/password and OAuth buttons
2. Registration page with form validation
3. Forgot password page with email input
4. Email verification pending page
5. Password reset page
6. All pages with consistent styling using shadcn/ui
7. Loading states and error handling"
Issue: Generated components don't match my design system colors Solution: Ask Claude to use CSS variables from globals.css (--primary, --secondary, etc.) instead of hardcoded color values. Specify "use our existing design tokens."
Issue: Components are not responsive on mobile Solution: Request "mobile-first responsive design with specific breakpoints: sm (640px), md (768px), lg (1024px)" and ask for preview at each breakpoint.
Issue: Too many client components affecting performance Solution: Ask Claude to "identify which components can be Server Components and only use 'use client' for interactive elements like forms, buttons with onClick."
Issue: Animations cause layout shift (CLS) Solution: Request "animations that don't affect layout, using transform and opacity only" to maintain good Core Web Vitals scores.
Issue: TypeScript errors with component props Solution: Ask Claude to "define explicit TypeScript interfaces for all component props with JSDoc comments" for better type safety.
V0 Rapid UI Prototyping Workflow Skill side by side with 2 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
2 trust signals differ across this comparison (Package trust, Source provenance).
| Field | Generate React UI with v0 (Vercel): produce shadcn/ui and Tailwind CSS components and full Next.js pages from prompts, then refine and add them to your app with the shadcn CLI. Open dossier | Vercel Labs' official Agent Skills collection for AI coding agents working on Vercel deployments, React and Next.js performance, React Native, web design guidelines, writing guidelines, composition patterns, view transitions, CLI token workflows, and Vercel optimization audits. Open dossier | Fill templated DOCX with data to produce reports, invoices, and formatted documents. Generate professional Word documents programmatically with python-docx or use Jinja2 templates with docxtpl for dynamic content insertion. Support tables, images, headers, footers, and custom styling. Open dossier |
|---|---|---|---|
| Next steps | |||
| Trust | |||
| Review status | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed |
| Package trustDiffers | Package verified2025-10-16 | Package not verified | Package verified2025-10-15 |
| Source provenanceDiffers | Source-backed | Source-backed | No submission link |
| Submitter | — | — | — |
| Install risk | Review first | Review first | Low risk |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Brand | — | — | |
| Category | skills | skills | skills |
| Source | first-party | source-backed | first-party |
| Author | JSONbored | Vercel Labs | JSONbored |
| Added | 2025-10-16 | 2026-06-18 | 2025-10-15 |
| Platforms | Claude CodeCodexWindsurfGeminiCursorCLI | Claude CodeCodexWindsurfGeminiCursorCLI | Claude CodeCodexWindsurfGeminiCursorCLI |
| Source repo | — | — | — |
| Safety notes | ✓`npx shadcn-ui@latest init` writes config and component files into your project; run it in a repo under version control and review the changes. Generated UI code is a starting point, not production-verified; review accessibility, validation, and security before shipping. | ✓The deploy-to-vercel and Vercel CLI token skills can guide agents toward git pushes, preview deployments, Vercel project linking, environment variable changes, and account-scoped CLI calls; keep human approval on those actions. The vercel-cli-with-tokens skill includes token-handling workflows. Prefer environment variables over command-line token flags and avoid echoing secrets into prompts, logs, screenshots, or public PRs. The vercel-optimize skill reads Vercel metrics, usage, project configuration, and code scan results; verify the linked project and team scope before collecting or acting on recommendations. The web-design-guidelines and writing-guidelines skills fetch current upstream rule documents at use time, so review fetched guidance before treating output as policy. React, Next.js, and React Native performance rules are strong defaults, but agents still need local tests, framework-version checks, and product-specific review before broad refactors. | ✓Setup downloads and unzips a package and installs Python libraries (python-docx/docxtpl); generating reports writes .docx files to disk, overwriting any file at the output path. Review before running. |
| Privacy notes | ✓v0 is a hosted Vercel service; the prompts and any context you send to generate UI are processed by Vercel under their terms. | ✓Deployment and optimization workflows may expose project names, team slugs, deployment URLs, routes, metrics, usage details, billing signals, source paths, build configuration, environment variable names, and CLI account context. Keep VERCEL_TOKEN, VERCEL_ORG_ID, VERCEL_PROJECT_ID, API keys, environment values, claim URLs, deployment logs, and private preview URLs out of public artifacts unless intentionally disclosed. Design, writing, React, and performance reviews can reveal proprietary UI, product copy, documentation strategy, source code, routes, and business priorities to the configured model provider. | ✓Report data you supply (templates and merged values) is rendered locally into Word documents; generated files can contain that data, so review them before sharing. |
| Prerequisites |
|
|
|
| Install | | | |
| Config | — | — | — |
| Citations | |||
| Claim | Unclaimed | Unclaimed | Unclaimed |
Source-backed guides for putting this to work.
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.