Skip to main content
Prompt template

shadcn Component Adapter for Cursor

A reusable prompt for asking an AI assistant to work as shadcn Component Adapter for Cursor.

Open the source

The full prompt is on this page. A prompt is not an installable skill package.

When to use this prompt

Use shadcn Component Adapter for Cursor when you want an AI assistant to start from a ready-made prompt template: paste it into the chat, then adapt its inputs, constraints and desired output to your task.

When not to use it

Skip shadcn Component Adapter for Cursor when you need an installable agent skill with its own files or scripts: a prompt template is plain text, not a SKILL.md package. A more specific prompt in the creativity category may also fit better.

What this prompt does

A reusable prompt for asking an AI assistant to work as shadcn Component Adapter for Cursor.

Use the template below as a starting point and adapt its inputs, constraints, and desired output to your task.

The prompt

# shadcn Component Visual Adapter

## ๐ŸŽฏ Objective
Refactor the existing `${component_name}` component located at `${component_file_path}` to match the **visual design, structure, and behavior** of the reference component available at:

> ${install_command:bunx --bun shadcn@latest add accordion}
${reference_url:}   โ† optional; leave blank if no docs page exists

Do NOT replace business logic, existing props interface, or data-fetching patterns. Preserve them.
Adapt only the **visual layer**: markup structure, class names, animations, and accessibility attributes.

---

## ๐Ÿ“‹ Step 1 โ€” Analyze the Existing Component

Before writing any code:

1. Read the full source of `${component_file_path}`.
2. Map out:
   - All **props and their types** (TypeScript interfaces or PropTypes).
   - Internal **state variables** (`useState`, `useReducer`, Zustand slices, etc.).
   - **Context providers or custom hooks** consumed.
   - **Child components** rendered and where they live.
   - **Event handlers** and callbacks exposed to the parent.
3. List every **import** โ€” flag any that will conflict with or can be replaced by the shadcn primitive.

Output a brief audit table before touching any code:

| Item | Current value | Action |
|------|--------------|--------|
| Props | ... | keep / rename / remove |
| State | ... | keep / migrate |
| Context/Hooks | ... | keep / replace |
| Sub-components | ... | keep / replace |
| Dependencies | ... | keep / install / remove |

---

## ๐Ÿ“ฆ Step 2 โ€” Dependency Resolution

Run the install command directly:

${install_command}

After the command completes, the generated files will appear in
${components_dir:components/ui}/. Proceed to Step 3 using those files.

---

## ๐Ÿ”ฌ Step 3 โ€” Review Reference Component

IF ${reference_url} is provided โ†’ fetch it and extract the visual spec as before.

IF ${reference_url} is blank โ†’ read the files downloaded by the CLI command
in Step 2 and extract the same information from the source code directly:
  - cva variant schema
  - data-state / data-disabled attributes
  - animation/transition classes
  - ARIA roles and props
  - cn() usage patterns

---

## ๐Ÿ›  Step 4 โ€” Refactor the Component

Apply the visual structure from Step 3 to the existing component from Step 1.

### Rules:
- โœ… Keep all **existing prop names and types** unless a direct shadcn equivalent exists.
- โœ… Keep all **data-fetching, business logic, and callbacks**.
- โœ… Wrap Radix primitives using **`forwardRef`** and spread `...props` to preserve flexibility.
- โœ… Use `cn()` for all className merging โ€” never string concatenation.
- โœ… Export named compound sub-components if the reference component uses them (e.g., `Accordion`, `AccordionItem`, `AccordionTrigger`, `AccordionContent`).
- โŒ Do NOT import the generated shadcn file and re-export it โ€” build the primitive inline in the refactored file to keep the logic co-located.
- โŒ Do NOT add Tailwind classes not present in the reference component without explicit instruction.

### Responsive behavior (`${responsive_breakpoints:sm md lg}`):
Apply mobile-first responsive classes. Confirm current breakpoints in `tailwind.config.ts` match the project's convention. If the reference uses container queries, install `@tailwindcss/container-queries`.

---

## ๐Ÿงฉ Step 5 โ€” Context Providers and Hooks

If the reference component requires a context provider (e.g., `ToastProvider`, `TooltipProvider`):

1. Check if it is already mounted in `${provider_file:app/layout.tsx}` or `${provider_file:app/providers.tsx}`.
2. If not, add it to the appropriate layout file. Provide the exact diff.
3. If a custom hook is required (e.g., `useToast`, `useDialog`), place it in `${hooks_dir:hooks/}` and import it from there.

---

## โ“ Step 6 โ€” Clarifying Questions (ask before generating if unknown)

If any of the following are not determinable from the existing code, **ask before writing**:

1. **Data/props**: What shape of data will be passed? (Provide a sample object if helpful.)
2. **State management**: Is component state local, or managed externally (Zustand, Redux, React Query)?
3. **Assets**: Are there required images, logos, or custom icons not covered by lucide-react?
4. **Responsive**: What is the expected layout at `${responsive_breakpoints:sm md lg}` breakpoints?
5. **Placement**: Where in the app routing/layout tree will this component live? (Important for context provider placement.)

---

## ๐Ÿ“ Step 7 โ€” Output Format

Provide the result as:

1. **`${component_file_path}`** โ€” full refactored component file.
2. **`${components_dir:components/ui}/${shadcn_component_slug}.tsx`** โ€” shadcn primitive (only if needed and not generated by CLI).
3. **`lib/utils.ts`** โ€” only if it needs to be created or updated.
4. **Layout/provider diff** โ€” only if a provider needs to be added.
5. A short **migration notes** section listing:
   - Removed dependencies
   - Renamed props (if any)
   - Any manual steps required (e.g., adding CSS variables to `globals.css`)

---

## ๐ŸŽจ Tailwind CSS Variables (shadcn design tokens)

Confirm that `globals.css` contains the required CSS custom properties. If the reference component uses tokens like `--radius`, `--background`, `--foreground`, `--primary`, `--ring`, append the missing variables. Use the shadcn default token set for `${color_theme:zinc}` unless the project already defines a custom theme.

---

## ๐Ÿšซ Constraints

- Framework: **${framework:Next.js 14+ App Router}**
- Styling: **Tailwind CSS ${tailwind_version:3}** only โ€” no inline styles, no CSS modules, no styled-components.
- TypeScript: **strict mode**. All new code must be fully typed.
- Do not upgrade or downgrade any existing dependency version unless there is a direct peer conflict.

Source: f/prompts.chat, dedicated to the public domain under CC0 1.0. View it at its source.

How to get started

The full prompt is on this page. A prompt is not an installable skill package.

View original source (opens a new tab)

Full install guide for Claude, Cursor, and Codex โ†’

What supports this recommendation?

55/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.

Documentation
41/100
Practical detail
52/100
Source evidence
63/100
Source signals
82/100
Model compatibility evidence
  • claudeinferred

    The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.

  • chatgptinferred

    The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.

  • geminiinferred

    The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.

  • copilotinferred

    The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.

  • llamainferred

    The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.

  • perplexityinferred

    The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.

  • mistralinferred

    The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.

  • grokinferred

    The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.

Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.

Intended uses

  • Ask an AI assistant to take on the shadcn Component Adapter for Cursor role.

Implementation notes

  • Replace example inputs and placeholders with details from your task.
  • Review the result before relying on it for consequential decisions.

Try it, then tell us how it went

A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.