# sveltekit-svelte5-tailwind-skill

A skill that helps an agent build sites on SvelteKit 2, Svelte 5 and Tailwind CSS v4. Useful when runes and Vite config keep tripping the model up.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 561 installs · ★ 30
- Author: claude-skills
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/claude-skills/sveltekit-svelte5-tailwind-skill/tree/HEAD/SKILL.md
- Updated: 2025-10-28
- HTML: https://affpapa.org/en/nevibecode/skills/sveltekit-svelte5-tailwind-skill

## What it does

The skill covers wiring the three tools into one stack: SvelteKit 2 with file-based routing, SSR and adapters for Vercel, Cloudflare, Node and static output; Svelte 5 with the `$state()`, `$derived()`, `$effect()` and `$props()` runes; Tailwind CSS v4 with CSS-first config and its Vite plugin. Two documentation sets ship inside: 17 problem-focused guides under `references/` and 7 API references under `docs/`.

The workflow is research before code. The agent scans `index.jsonl` and `sections.jsonl`, picks 3–4 candidate files, reads only the matching sections by offset and limit, then implements. That order matters because the integration has sharp edges: runes do not work in SSR, and `tailwindcss()` has to sit above `sveltekit()` in `vite.config.js`. Separate guides handle form actions with progressive enhancement, moving off Svelte 4 and Tailwind v3, deployment, and common errors.

A five-minute path is included: scaffold with `npm create svelte@latest my-app`, add `tailwindcss@next` and `@tailwindcss/vite@next`, edit the Vite config, then put `@import "tailwindcss"` in `app.css`. No API keys or external services are involved; everything lives in the skill's own files.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add claude-skills/sveltekit-svelte5-tailwind-skill --skill sveltekit-svelte5-tailwind-skill -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/sveltekit-svelte5-tailwind-skill/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/sveltekit-svelte5-tailwind-skill/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add claude-skills/sveltekit-svelte5-tailwind-skill --skill sveltekit-svelte5-tailwind-skill -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/sveltekit-svelte5-tailwind-skill/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add claude-skills/sveltekit-svelte5-tailwind-skill --skill sveltekit-svelte5-tailwind-skill -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/sveltekit-svelte5-tailwind-skill/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install claude-skills/sveltekit-svelte5-tailwind-skill sveltekit-svelte5-tailwind-skill
```

2. **Manually: put the files in place**
- File: `.github/skills/sveltekit-svelte5-tailwind-skill/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add claude-skills/sveltekit-svelte5-tailwind-skill --skill sveltekit-svelte5-tailwind-skill -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/claude-skills/sveltekit-svelte5-tailwind-skill
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/sveltekit-svelte5-tailwind-skill/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add claude-skills/sveltekit-svelte5-tailwind-skill --skill sveltekit-svelte5-tailwind-skill -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/claude-skills/sveltekit-svelte5-tailwind-skill/tree/HEAD/SKILL.md

## When to use it
- get SvelteKit 2, Svelte 5 and Tailwind v4 working in one project
- find out why runes fail during server-side rendering
- order the plugins in `vite.config.js` correctly
- build a form with progressive enhancement on server actions
- move a project from Svelte 4 and Tailwind v3 to the new versions

## Example prompts
- Build a catalog page with SvelteKit 2, Svelte 5 runes and Tailwind v4 styles
- Why doesn't `$state()` update under SSR? Check the skill docs and show me an example
- Create a newsletter form using SvelteKit server actions with progressive enhancement

## Similar
- [frontend-design](https://affpapa.org/en/nevibecode/skills/frontend-design.md) — skill · 1025790 installs
- [design-taste-frontend](https://affpapa.org/en/nevibecode/skills/design-taste-frontend.md) — skill · 678700 installs
- [prototype](https://affpapa.org/en/nevibecode/skills/prototype.md) — skill · 986201 installs
- [hyperframes](https://affpapa.org/en/nevibecode/skills/heygen-com-hyperframes.md) — skill · 1200000 installs
- [hyperframes-cli](https://affpapa.org/en/nevibecode/skills/heygen-com-hyperframes-cli.md) — skill · 1300000 installs
- [webapp-testing](https://affpapa.org/en/nevibecode/skills/webapp-testing.md) — skill · 186758 installs

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md