// Follow up cleanup and refactors that **must** be done whenever a new shadcn component is added via the add cli command. This skill should be checked whenever a new file is added to the shadcn ui component directory (`src/components/ui`).
Conventions for authoring, modifying, testing, and documenting a Remeda utility function — including the migration mapping pages for Lodash/Ramda/Just users. Use this skill whenever editing a file under `packages/remeda/src/` or `packages/docs/src/content/mapping/{lodash,ramda,just}/`, when reviewing a PR or local changes touching those directories, or whenever an issue, PR, or chat refers to a specific Remeda function or to a migration mapping page.
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", or "switch to --preset".
| name | shadcn-add |
| description | Follow up cleanup and refactors that **must** be done whenever a new shadcn component is added via the add cli command. This skill should be checked whenever a new file is added to the shadcn ui component directory (`src/components/ui`). |
import * as React from "react"); only import the concrete types and utilities needed.React. prefixes, both in types and in runtime code.export { } block; add the export keyword to each declaration instead."use client" directives.exactOptionalPropertyTypes enabled. This might require removing props from destructurings.data-['xxx'] attributes to data-xxx, converting arbitrary sizes to concrete values, e.g. size-[3rem] to size-12).