
from shadcn-svelte8,726
Hands-on guidance for adding, updating, debugging, and composing shadcn-svelte UI components in Svelte projects, using the official CLI and project config.
This skill equips an agent to work with the shadcn-svelte design-system for Svelte: it explains project context, recommended imports and component composition, enforces styling and accessibility rules, and provides CLI-driven workflows for adding or updating components. It is explicitly focused on using the shadcn-svelte CLI (npx/pnpm/bunx runners), reading the project's components.json aliases, and ensuring component composition follows the package's conventions.
Use this skill when you need to add or update UI components in a Svelte project that uses shadcn-svelte, when you must fix styling or composition issues, or when running the CLI to init/add/update components. Triggers include tasks like shadcn-svelte init, add component, registry URLs, or when the repo contains a components.json alias mapping.
Best with agents that can run shell commands and read repository files (Copilot/Codex/GitHub CLI-capable agents).
Well-crafted skill for working with shadcn-svelte UI components in Svelte projects. The SKILL.md is thorough with specific triggers, detailed rules for styling/forms/composition/icons, and a clear workflow. No bundled scripts — purely a reference/guidance skill. Allowed-tools restricts execution to the shadcn-svelte CLI only, which is appropriate and safe.
Clean skill — no security concerns. The allowed-tools field properly scopes execution. SKILL.md references external rule files (./rules/styling.md, ./rules/forms.md, etc.) which couldn't be audited but are referenced by relative path, which is correct skill architecture.