shadcn-svelte-management
Manage UI components using MCP tools with primary focus on Svelte ecosystem. Specialized in Svelte component libraries including shadcn-svelte, Skeleton UI, and Melt UI. Use when user needs to: (1) Add new Svelte UI components to a project (2) Build complex UI features requiring multiple components (3) Research component implementations and examples (4) Get component installation commands (5) Choose appropriate Svelte component library Triggers: "add components", "UI components", "build UI", "install component", "create form", "create dialog", "svelte components", "shadcn-svelte", "skeleton ui"
What this skill does
# Svelte Component Management
## Primary Focus: Svelte Ecosystem
Specialized in Svelte component libraries and their management:
- **shadcn-svelte**: Svelte adaptation of shadcn/ui
- **Skeleton UI**: Modern, accessible Svelte component library
- **Melt UI**: Headless components for Svelte
- **Custom components**: Built from scratch with Tailwind CSS
## Prerequisites
### For Svelte Projects
Verify project setup:
```bash
# Check if SvelteKit project
ls src/routes/ src/lib/
```
### For shadcn-svelte Projects
If using shadcn-svelte:
```bash
npx shadcn-svelte@latest init
```
### For Skeleton UI Projects
If using Skeleton UI:
```bash
npm install @skeletonlabs/skeleton
```
## Quick Add Workflow for Svelte
For simple component additions (e.g., "add a date picker"):
### Option 1: shadcn-svelte
```bash
npx shadcn-svelte@latest add button
npx shadcn-svelte@latest add card
npx shadcn-svelte@latest add dialog
```
### Option 2: Skeleton UI
```bash
npm install @skeletonlabs/skeleton
# Import in app.css: @import '@skeletonlabs/skeleton/theme';
```
### Option 3: Custom Component
Create custom component with Tailwind CSS:
```svelte
<!-- src/lib/components/DatePicker.svelte -->
<script lang="ts">
import { createEventDispatcher } from 'svelte';
export let value: Date = new Date();
export let placeholder = 'Select date';
const dispatch = createEventDispatcher();
</script>
<input
type="date"
bind:value
{placeholder}
on:change={(e) => dispatch('change', { value: e.target.value })}
class="w-full px-3 py-2 border rounded-lg focus:ring-2 focus:ring-blue-500"
/>
```
## Complex Build Workflow for Svelte
For multi-component features (e.g., "build a login form"), see [references/workflows.md](references/workflows.md).
**When to use Complex Build:**
- Feature requires 3+ components
- Need component hierarchy planning
- Building complete sections (forms, dashboards, modals)
- Integrating with SvelteKit's form actions and load functions
**Svelte-specific considerations:**
- Use SvelteKit's form actions for form handling
- Leverage progressive enhancement patterns
- Consider accessibility with Svelte's ARIA support
- Use Svelte stores for state management
## Svelte Component Patterns
### Common Component Categories
- **Forms**: `form`, `input`, `select`, `checkbox`, `radio-group`, `textarea`
- **Layout**: `card`, `dialog`, `sheet`, `drawer`, `tabs`, `container`
- **Feedback**: `alert`, `toast`, `skeleton`, `progress`, `spinner`
- **Navigation**: `button`, `dropdown-menu`, `navigation-menu`, `breadcrumb`
- **Data Display**: `table`, `badge`, `avatar`, `accordion`, `carousel`
### Svelte-specific Patterns
- **Form Actions**: Integration with SvelteKit's form handling
- **Progressive Enhancement**: Works without JavaScript, enhanced with it
- **Reactive Components**: Using Svelte's reactivity for dynamic UI
- **Transitions**: Built-in Svelte transitions for smooth animations
### Installation Examples
```bash
# shadcn-svelte
npx shadcn-svelte@latest add button card form
# Skeleton UI
npm install @skeletonlabs/skeleton
# Add to app.css: @import '@skeletonlabs/skeleton/theme';
# Melt UI
npm install @melt-ui/svelte
```
## After Implementation
Always run audit:
```
shadcn___get_audit_checklist
```
## Custom Styling & Theming
Shadcn provides **structural foundation** with default styling. For custom aesthetics:
## Svelte Component Library Ecosystem
### Primary Libraries
**1. shadcn-svelte**
```bash
npx shadcn-svelte@latest init
npx shadcn-svelte@latest add [component-name]
```
- Components in: `src/lib/components/ui/`
- Theme in: `src/app.css`
- Config: `components.json`
**2. Skeleton UI**
```bash
npm install @skeletonlabs/skeleton
```
- Import in: `src/app.css` → `@import '@skeletonlabs/skeleton/theme';`
- Components: Import from `@skeletonlabs/skeleton`
- Theme: CSS variables in `src/app.css`
**3. Melt UI**
```bash
npm install @melt-ui/svelte
```
- Headless components
- Build with Tailwind CSS
- Full accessibility support
- Works with SvelteKit
**4. Custom Components**
- Build from scratch with Tailwind CSS
- Use Svelte transitions and actions
- Integrate with SvelteKit patterns
### Customization Strategies
**For shadcn-svelte:**
1. Modify CSS variables in `src/app.css`
2. Extend Tailwind config for custom themes
3. Override component styles with `class:` directives
**For Skeleton UI:**
1. Use CSS custom properties for theming
2. Leverage Skeleton's theme system
3. Combine with custom Tailwind utilities
**For Custom Components:**
1. Build with Svelte's component syntax
2. Use Tailwind for styling
3. Add Svelte transitions for animations
4. Ensure accessibility with ARIA attributes
**Invoke `frontend-design` skill when:**
- User wants unique/distinctive visual style beyond default theme
- Need custom typography, color schemes, or motion effects
- Building landing pages or marketing sites requiring creative design
- User mentions "custom styling", "unique design", "not generic"
**Workflow for Svelte projects:**
1. Choose appropriate component library (shadcn-svelte, Skeleton, Melt, or custom)
2. Use `shadcn-svelte-management` patterns adapted for Svelte
3. Invoke `frontend-design` for visual customization:
- Custom CSS variables in `src/app.css`
- Tailwind theme extensions in `tailwind.config.js`
- Svelte transitions and animations
- Typography and color refinements
**Customization targets:**
- `src/app.css` - CSS variables, custom fonts, theme imports
- `tailwind.config.js` - theme colors, fonts, animations
- `src/lib/components/ui/` - component-level overrides
- Component-level `class:` directives for dynamic styling
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.