From ss-svelte-coding
Use shadcn-svelte components in SvelteKit projects. Detects whether the current project is a SvelteKit app with shadcn-svelte installed, lists available components, and provides access to full component documentation via the official llms.txt. Helps choose the right UI components for the job — buttons, forms, dialogs, tables, charts, and more — following shadcn-svelte best practices. Use this skill whenever the user is working in a SvelteKit project and wants to: add UI components, build forms, create dialogs or modals, add a data table, use a date picker, build a sidebar or navigation, add charts, use a combobox or select, create an alert or toast notification, or generally build UI with pre-built accessible components. Also trigger when the user mentions "shadcn", "shadcn-svelte", "bits-ui", or asks about available components in their Svelte project.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ss-svelte-coding:ss-shadcn-svelteThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use the right shadcn-svelte components when building UI in SvelteKit projects. This skill detects your project setup, shows what's available, and gives you access to full component documentation.
Use the right shadcn-svelte components when building UI in SvelteKit projects. This skill detects your project setup, shows what's available, and gives you access to full component documentation.
The project must be a SvelteKit app with shadcn-svelte initialized:
# Initialize shadcn-svelte in an existing SvelteKit project
npx shadcn-svelte@latest init
Run the detection script to verify this is a SvelteKit project with shadcn-svelte and see which components are already installed:
bash <skill-path>/scripts/detect.sh .
This will:
svelte.config.js/ts and @sveltejs/kit in package.json)components.json, bits-ui, or shadcn-svelte in package.json)If the script exits with code 1, the project either isn't SvelteKit or doesn't have shadcn-svelte — do not proceed with shadcn-svelte components in that case.
The full component documentation for LLMs is available at:
https://www.shadcn-svelte.com/llms.txt
Fetch this URL to get a structured index of all available components organized by category, with links to individual component documentation pages (in .md format).
When you need to use a specific component, read its individual documentation page from the links provided in llms.txt. Each component doc includes:
When building UI, follow this decision process:
npx shadcn-svelte@latest add <component-name>
shadcn-svelte components are organized into these categories:
| Category | Components |
|---|---|
| Layout | Aspect Ratio, Collapsible, Resizable, Scroll Area, Separator, Sidebar |
| Form & Input | Button, Calendar, Checkbox, Combobox, Date Picker, Input, Input OTP, Label, Radio Group, Range Calendar, Select, Slider, Switch, Textarea, Toggle, Toggle Group |
| Data Display | Accordion, Avatar, Badge, Card, Carousel, Chart, Table, Data Table |
| Feedback | Alert, Alert Dialog, Progress, Skeleton, Sonner (Toast) |
| Overlay | Context Menu, Dialog, Drawer, Dropdown Menu, Hover Card, Menubar, Popover, Sheet, Tooltip |
| Navigation | Breadcrumb, Command, Pagination, Tabs |
| Typography | Typography |
# Add a single component
npx shadcn-svelte@latest add button
# Add multiple components
npx shadcn-svelte@latest add button card dialog
# List all available components
npx shadcn-svelte@latest add
Components are typically imported from the project's $lib/components/ui directory:
<script lang="ts">
import { Button } from "$lib/components/ui/button";
import * as Card from "$lib/components/ui/card";
import * as Dialog from "$lib/components/ui/dialog";
</script>
Some components use namespace imports (with * as) when they have multiple sub-components (Card, Dialog, Sheet, Table, etc.), while simpler components use named imports (Button, Input, Badge, etc.).
components.json configuration$state, $derived, $effect) and snippet-based compositionGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub rajnandan1/such-skills --plugin ss-svelte-coding