원클릭으로
new-shadcn-component
Installs a shadcn/ui component and creates a typed wrapper. Use when adding new UI primitives from the shadcn registry.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Installs a shadcn/ui component and creates a typed wrapper. Use when adding new UI primitives from the shadcn registry.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
PostHog integration for Next.js App Router applications
Use when a feature branch is complete and ready for PR — runs a full diff-based review of the current branch against main, reads every changed file, validates against project rules, and produces a concrete action plan. Do NOT use on main branch.
Identifies and executes the next pending POC task. Fast context pickup from docs/poc/context.json — no build/lint at start. Use for starting the next task, resuming in-progress work, or targeting a specific task by ID.
Use when the Antes da Tela POC needs a new task direction or clearer scope before handing work off to /create-poc-task in the documented AI workflow.
Analyzes current POC task state, creates a standardized new task file, and updates docs/poc/context.json and docs/poc/tasks/summary.md. Use when adding a new task to the Antes da Tela POC backlog.
Unified Figma implementation + refinement workflow that translates Figma designs into production-ready code, reconciles design tokens, and performs regression-safe metadata updates. Use live MCP data with canonical metadata under `docs/design-system/`.
| name | new-shadcn-component |
| description | Installs a shadcn/ui component and creates a typed wrapper. Use when adding new UI primitives from the shadcn registry. |
| argument-hint | [component-name] e.g. dialog, table, form, select |
| allowed-tools | Read, Write, Bash |
Install and scaffold the shadcn/ui component: $ARGUMENTS
yarn dlx shadcn@latest add $ARGUMENTS
Verify the installed file at components/ui/$ARGUMENTS.tsx.
Create a composed wrapper at components/$ARGUMENTS/$ARGUMENTS.tsx only if the component needs project-specific props, styling, or behavior (e.g., a <ConfirmDialog> built on top of <Dialog>):
import {
Dialog,
DialogContent,
DialogHeader,
DialogTitle,
DialogFooter,
} from "@/components/ui/dialog";
import { Button } from "@/components/ui/button";
import { cn } from "@/lib/utils";
interface ConfirmDialogProps {
open: boolean;
onOpenChange: (open: boolean) => void;
title: string;
description?: string;
onConfirm: () => void;
isLoading?: boolean;
className?: string;
}
export function ConfirmDialog({
open,
onOpenChange,
title,
description,
onConfirm,
isLoading,
className,
}: ConfirmDialogProps) {
return (
<Dialog open={open} onOpenChange={onOpenChange}>
<DialogContent className={cn(className)}>
<DialogHeader>
<DialogTitle>{title}</DialogTitle>
{description && <p className="text-sm text-muted-foreground">{description}</p>}
</DialogHeader>
<DialogFooter>
<Button variant="outline" onClick={() => onOpenChange(false)}>
Cancelar
</Button>
<Button onClick={onConfirm} disabled={isLoading}>
{isLoading ? "Processando..." : "Confirmar"}
</Button>
</DialogFooter>
</DialogContent>
</Dialog>
);
}
components/ui/ — they are managed by shadcn registry.cn() for className merging.className prop from callers (composability).