Agent skill

Sveltekit Svelte5 Tailwind Skill

by 302ai in 302ai/302-AI-Studio

Comprehensive integration skill for building sites with SvelteKit 2, Svelte 5, and Tailwind CSS v4

AGPL-3.0Auto-check passedFrontend & Design

Install Sveltekit Svelte5 Tailwind Skill

skills CLI
$ npx skills add 302ai/302-AI-Studio --skill sveltekit-svelte5-tailwind-skill -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install 302ai/302-AI-Studio sveltekit-svelte5-tailwind-skill --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/302ai/302-AI-Studio.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/sveltekit-svelte5-tailwind-skill .claude/skills/sveltekit-svelte5-tailwind-skill && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
sveltekit-svelte5-tailwind-skill
GitHub stars
132
Token cost
~3.5k tokens
SKILL.md length
1,080 words
Files
34 (incl. references)
Skills in repo
5
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Comprehensive integration skill for building sites with SvelteKit 2, Svelte 5, and Tailwind CSS v4

  • Works in 6 steps: Discover Available Documentation → Load Relevant Indexes → Reason About Candidates → …
  • Tasks that involve CSS and styling
  • SKILL.md covers About This Integration Stack, How to Use This Skill, Documentation Collections and Searching Documentation, plus 12 more sections
  • Calls npm

What it does

Sveltekit Svelte5 Tailwind Skill is an agent skill from 302ai/302-AI-Studio. Comprehensive integration skill for building sites with SvelteKit 2, Svelte 5, and Tailwind CSS v4

Its SKILL.md is about 3.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 35 other files, including reference files (for example `README.md`, `docs/adapters-reference.md` and `docs/advanced-routing.md`).

It sits in Frontend & Design, covering CSS and styling. It works with Tailwind CSS, SvelteKit and Svelte. The licence is AGPL-3.0.

When your agent uses it

  • Tasks that involve CSS and styling

Example prompts

  • “/sveltekit-svelte5-tailwind-skill”

Requirements

  • Node.js

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Discover Available Documentation
  2. Load Relevant Indexes
  3. Reason About Candidates
  4. Get Section Details
  5. Read Targeted Sections
  6. Synthesize and Answer

What it can do on your machine

Read from SKILL.md and the folder at commit 8b11163. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Sveltekit Svelte5 Tailwind Skill loads about 3.5k tokens when it runs, and up to ~93k if it reads all its reference files. Until then it costs about 33 tokens; SKILL.md has 1,080 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~33
When it runs · the whole SKILL.md, loaded when a task matches
~3.5k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~93k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from 302ai/302-AI-Studio at commit 8b11163, republished under its AGPL-3.0 licence (© 302ai). 1,080 words, ~3,472 tokens.

Download SKILL.mdSave it as .claude/skills/sveltekit-svelte5-tailwind-skill/SKILL.md (or your agent's skills folder). This skill also uses 33 other files; get the full folder from GitHub.
name
sveltekit-svelte5-tailwind-skill
description
Comprehensive integration skill for building sites with SvelteKit 2, Svelte 5, and Tailwind CSS v4
version
1.0.0
scope
integration
distribution
author-only

SvelteKit 2 + Svelte 5 + Tailwind v4 Integration Skill

This skill provides comprehensive guidance for building modern web applications with the SvelteKit 2 + Svelte 5 + Tailwind CSS v4 stack.

About This Integration Stack

SvelteKit 2 is a modern full-stack framework with:

  • File-based routing with layouts
  • Server-side rendering (SSR) and static site generation (SSG)
  • Form actions with progressive enhancement
  • Multiple deployment adapters (Vercel, Cloudflare, Node, static)

Svelte 5 introduces a new reactivity system with:

  • Runes: $state(), $derived(), $effect(), $props()
  • Simplified component authoring
  • Better TypeScript support
  • Snippets replacing slots

Tailwind CSS v4 offers:

  • CSS-first configuration
  • New Vite plugin architecture
  • Improved JIT performance
  • Simplified setup

Integration challenges this skill addresses:

  • Configuring all three tools to work together
  • Understanding Svelte 5 runes in SSR context
  • Progressive enhancement with form actions
  • CSS loading in development and production
  • Deployment across different platforms
  • Migration from earlier versions

How to Use This Skill

CRITICAL: Research-First Methodology

When a user asks you to build something with this stack:

  1. Research first - Search the documentation to understand:

    • How SvelteKit handles this use case
    • What Svelte 5 runes patterns apply
    • How to style with Tailwind v4
    • Common integration pitfalls to avoid
  2. Then execute - Implement the solution using the knowledge gained from documentation

Why this matters:

  • This integration has specific constraints (e.g., runes don't work in SSR)
  • The documentation provides authoritative guidance on configuration
  • Researching first prevents mistakes that require rework
  • You'll implement solutions that follow best practices

Workflow:

  1. User requests: "Help me build [feature] with SvelteKit/Svelte 5/Tailwind"
  2. You search documentation using the process below
  3. You understand the recommended approach
  4. You implement the solution correctly the first time

Documentation Collections

This skill includes two searchable documentation collections:

references/ (Problem-Focused Guides)

17 curated guides addressing specific integration challenges:

  • Setup: getting-started.md, project-setup.md
  • Core Concepts: svelte5-runes.md, routing-patterns.md, server-rendering.md, data-loading.md
  • Forms & Styling: forms-and-actions.md, styling-with-tailwind.md, styling-patterns.md
  • Deployment: deployment-guide.md
  • Migration: migration-svelte4-to-5.md, tailwind-v4-migration.md
  • Optimization: best-practices.md, performance-optimization.md
  • Troubleshooting: common-issues.md, troubleshooting.md
  • Search System: documentation-search-system.md
docs/ (Comprehensive Reference)

7 adapted documentation guides covering complete APIs:

  • sveltekit-configuration.md - Complete svelte.config.js and Vite config
  • svelte5-api-reference.md - All Svelte 5 runes and template syntax
  • tailwind-configuration.md - Tailwind v4 configuration options
  • adapters-reference.md - Deployment adapter specifications
  • advanced-routing.md - Advanced SvelteKit routing patterns
  • advanced-ssr.md - SSR hooks, streaming, and optimization
  • integration-patterns.md - Complete integration examples

Searching Documentation

IMPORTANT: Always search before implementing!

This skill uses a 5-stage search process for efficient documentation lookup:

Stage 0: Discover Available Documentation

Find all documentation indexes:

bash
find . -name "index.jsonl" -type f

Expected output:

  • ./references/index.jsonl (17 problem-focused guides)
  • ./docs/index.jsonl (7 comprehensive references)

Sample each collection to understand its scope:

Read references/index.jsonl with offset: 1, limit: 5
Read docs/index.jsonl with offset: 1, limit: 5

Determine which collection(s) are relevant to your query.

Stage 1: Load Relevant Indexes

Read the complete index file(s) for your chosen collection(s):

Read references/index.jsonl  # For how-to guides and troubleshooting
Read docs/index.jsonl         # For API reference and configuration
Stage 2: Reason About Candidates

Analyze the summaries to identify 3-4 most relevant files:

For setup questions → references/getting-started.md, references/project-setup.md For runes questions → references/svelte5-runes.md, docs/svelte5-api-reference.md For forms questions → references/forms-and-actions.md, docs/integration-patterns.md For styling questions → references/styling-with-tailwind.md, docs/tailwind-configuration.md For SSR questions → references/server-rendering.md, docs/advanced-ssr.md For deployment → references/deployment-guide.md, docs/adapters-reference.md For errors → references/common-issues.md, references/troubleshooting.md

Consider:

  • Query intent (how-to vs what-is vs troubleshooting)
  • Integration-specific vs single-package questions
  • Beginner vs advanced topics
Stage 3: Get Section Details

For your 3-4 candidates, read their sections.jsonl entries:

Read references/sections.jsonl with offset: {index}, limit: 1
Read docs/sections.jsonl with offset: {index}, limit: 1

Important: Index number from index.jsonl = line number in sections.jsonl

Analyze the section summaries to identify which sections address your query.

Stage 4: Read Targeted Sections

Read only the relevant sections:

Read references/getting-started.md with offset: 45, limit: 89
Read docs/svelte5-api-reference.md with offset: 120, limit: 65

Use the offset and limit from the sections.jsonl data for precise reading.

Stage 5: Synthesize and Answer

Combine information from multiple sources:

  1. Direct answer to the user's question
  2. Code examples (complete and runnable)
  3. Integration-specific considerations
  4. File references for further reading

Example file references:

See: references/svelte5-runes.md:156-245 (Server-Side Constraints)
See: docs/advanced-ssr.md:89-134 (SSR Load Functions)

For complete search methodology with examples, see references/documentation-search-system.md

Quick Start (5 Minutes)

For a complete walkthrough, search references/getting-started.md

Basic setup commands:

bash
# 1. Create SvelteKit project
npm create svelte@latest my-app
cd my-app
npm install

# 2. Add Tailwind v4
npm install -D tailwindcss@next @tailwindcss/vite@next

# 3. Configure Vite (vite.config.js)
import { sveltekit } from '@sveltejs/kit/vite';
import tailwindcss from '@tailwindcss/vite';

export default {
  plugins: [
    tailwindcss(),  // MUST be before sveltekit()
    sveltekit()
  ]
};

# 4. Create app.css
@import "tailwindcss";

# 5. Import in root layout (src/routes/+layout.svelte)
<script>
  import '../app.css';
</script>
<slot />

# 6. Verify
npm run dev

Critical configuration:

  • Tailwind plugin MUST come before SvelteKit plugin in vite.config.js
  • Import CSS in root +layout.svelte (not app.html)
  • Use @next tag for Tailwind v4 packages
Show full SKILL.md (450 more words)Show less

Common Use Cases

Setup and Configuration → Search: references/getting-started.md, references/project-setup.md → Key sections: Installation, Vite Configuration, Directory Structure

Svelte 5 Runes with SSR → Search: references/svelte5-runes.md → Critical: "Server-Side Constraints" section - $state() doesn't work in SSR!

Forms and Progressive Enhancement → Search: references/forms-and-actions.md → Key pattern: Manual enhance() for rune compatibility

Styling Components → Search: references/styling-with-tailwind.md, references/styling-patterns.md → Key topics: Dynamic classes, dark mode, component patterns

Data Loading → Search: references/data-loading.md, docs/advanced-ssr.md → Key pattern: Passing load() data to rune state

Deployment → Search: references/deployment-guide.md, docs/adapters-reference.md → Platform-specific: Vercel, Cloudflare, Node, static

Troubleshooting Errors → Search: references/common-issues.md first (quick fixes) → Then: references/troubleshooting.md (systematic debugging)

Common Issues and Quick Fixes

CSS not loading in production → Search: references/common-issues.md section "CSS Loading Issues" → Quick check: Vite plugin order, CSS import location

Runes causing SSR errors → Search: references/svelte5-runes.md section "Server-Side Constraints" → Quick fix: Don't use $state() or $effect() in SSR components

Form losing state on submit → Search: references/forms-and-actions.md section "Handling use:enhance Reactivity" → Quick fix: Use manual enhance() callback

HMR breaking → Search: references/common-issues.md section "Hot Module Reload Problems" → Quick fix: Check Vite plugin order and file watch settings

Tailwind classes not working → Search: references/styling-with-tailwind.md section "Content Detection and Purging" → Quick fix: Check content paths in config, use full class names

For systematic troubleshooting, see references/troubleshooting.md

Integration Patterns

Server + Client Component Split

svelte
<!-- +page.svelte (SSR-safe) -->
<script>
  export let data;
</script>

<ClientCounter initialCount={data.count} />

<!-- ClientCounter.svelte (client-only runes) -->
<script>
  let { initialCount } = $props();
  let count = $state(initialCount);
</script>

Form with Progressive Enhancement

svelte
<script>
	import { enhance } from "$app/forms";
	let { form } = $props();
	let submitting = $state(false);
</script>

<form
	method="POST"
	use:enhance={() => {
		submitting = true;
		return async ({ result, update }) => {
			submitting = false;
			await update();
		};
	}}
>
	<!-- form fields -->
</form>

Conditional Tailwind Classes

svelte
<script>
	let active = $state(false);
</script>

<!-- ✅ GOOD: Full class names -->
<div class:bg-blue-500={active} class:bg-gray-200={!active}>Button</div>

<!-- ❌ BAD: Dynamic class parts -->
<div class="bg-{active ? 'blue' : 'gray'}-500">Button</div>

For complete patterns, search docs/integration-patterns.md

Best Practices

Search references/best-practices.md for comprehensive guidance on:

  • Project organization and architecture
  • Component design patterns
  • State management strategies
  • Styling conventions
  • Performance optimization
  • Security considerations
  • Testing strategies
  • Accessibility guidelines

Migration Guides

Migrating from Svelte 4 to Svelte 5 in SvelteKit → Search: references/migration-svelte4-to-5.md → Key topics: Stores to runes, reactive statements to $derived, slots to snippets

Migrating from Tailwind v3 to v4 → Search: references/tailwind-v4-migration.md → Key topics: CSS-first config, Vite plugin, syntax changes

Performance Optimization

Search references/performance-optimization.md for:

  • Bundle size optimization
  • CSS purging and minification
  • Code splitting strategies
  • Image and font optimization
  • Lazy loading patterns
  • Core Web Vitals optimization
  • Lighthouse score improvements

Version Information

This skill covers:

  • SvelteKit: 2.x (latest stable)
  • Svelte: 5.x (with runes)
  • Tailwind CSS: 4.x (CSS-first configuration)

All code examples and patterns are tested with these versions.

Getting Help

  1. Start with search: Use the 5-stage search process above
  2. Check common issues: references/common-issues.md for quick fixes
  3. Systematic debugging: references/troubleshooting.md for methodology
  4. Consult references: Problem-focused guides for specific topics
  5. Check API docs: Comprehensive references for configuration details

Skill Structure

sveltekit-svelte5-tailwind-skill/
├── SKILL.md                           # This file
├── references/                        # Problem-focused guides (17 files)
│   ├── index.jsonl                    # Search index
│   ├── sections.jsonl                 # Section details
│   ├── index.meta.json               # Collection metadata
│   ├── documentation-search-system.md # Complete search methodology
│   ├── getting-started.md
│   ├── project-setup.md
│   ├── svelte5-runes.md
│   ├── forms-and-actions.md
│   ├── styling-with-tailwind.md
│   ├── server-rendering.md
│   ├── data-loading.md
│   ├── deployment-guide.md
│   ├── routing-patterns.md
│   ├── styling-patterns.md
│   ├── best-practices.md
│   ├── performance-optimization.md
│   ├── migration-svelte4-to-5.md
│   ├── tailwind-v4-migration.md
│   ├── common-issues.md
│   └── troubleshooting.md
├── docs/                              # Comprehensive references (7 files)
│   ├── index.jsonl                    # Search index
│   ├── sections.jsonl                 # Section details
│   ├── index.meta.json               # Collection metadata
│   ├── sveltekit-configuration.md
│   ├── svelte5-api-reference.md
│   ├── tailwind-configuration.md
│   ├── adapters-reference.md
│   ├── advanced-routing.md
│   ├── advanced-ssr.md
│   └── integration-patterns.md
├── provenance.jsonl                   # Source attribution
└── skill.manifest.json                # Skill metadata

Distribution Mode

This skill uses author-only distribution:

  • All content is newly authored
  • No verbatim vendor documentation
  • Source materials used for reference only
  • All guides cite sources in frontmatter (adapted_from)

Remember

Always search documentation before implementing! The research-first approach prevents common mistakes and ensures you follow integration best practices.

Start with Stage 0 (discover indexes) and work through the 5-stage search process for every question.

© 302ai, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 33 other files (references) in .agents/skills/sveltekit-svelte5-tailwind-skill of 302ai/302-AI-Studio.

  • SKILL.md
  • README.md
  • docs/adapters-reference.md
  • docs/advanced-routing.md
  • docs/advanced-ssr.md
  • docs/index.jsonl
  • docs/index.meta.json
  • docs/integration-patterns.md
  • docs/sections.jsonl
  • docs/svelte5-api-reference.md
  • docs/sveltekit-configuration.md
  • docs/tailwind-configuration.md
  • provenance.jsonl
  • references/best-practices.md
  • references/common-issues.md
  • references/data-loading.md
  • references/deployment-guide.md
  • references/documentation-search-system.md
  • references/forms-and-actions.md
  • … and 15 more

Open the folder on GitHubat commit 8b11163

Compare with similar skills

Sveltekit Svelte5 Tailwind Skill next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Sveltekit Svelte5 Tailwind Skill compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Sveltekit Svelte5 Tailwind Skill this skill302ai/302-AI-Studio132—~3.5kAutomated safety check: PassAGPL-3.0
Kill AI Slopyetone/kill-ai-slop1.3k—~1.4kAutomated safety check: PassApache-2.0
Design StyleCastor6/tactus3761 repos~2.1kAutomated safety check: PassApache-2.0
Svelte Code Writerkampsy/ui2882 repos~490Automated safety check: PassMIT
Kampsy UIkampsy/ui288—~3.6kAutomated safety check: PassMIT
UI UX Pro Maxsundial-org/awesome-openclaw-skills6632 repos~657Automated safety check: PassNone

Similar skills

  • Kill AI Slop

    yetone/kill-ai-slop

    Find and remove AI slop — the generic, machine-default visual and copy tics of vibe-coded products — from a web project.

    1.3k GitHub stars~1.4k tokensUpdated 26 days ago
    Frontend & DesignAuto-check passed
  • Design Style

    Castor6/tactus

    A skill your agent uses whenever the user asks to build, create, design, develop, improve, or style any frontend interface or visual element.

    376 GitHub starsUsed in 1 repo~2.1k tokens
    Frontend & DesignAuto-check passed
  • CLI tools for Svelte 5 documentation lookup and code analysis.

    288 GitHub starsUsed in 2 repos~490 tokens
    Frontend & DesignAuto-check passed
  • Kampsy UI

    kampsy/ui

    Consumer guide to build UIs with kampsy-ui (Svelte 5 + Tailwind v4, Geist-inspired).

    288 GitHub stars~3.6k tokensUpdated 12 days ago
    Frontend & DesignAuto-check passed
  • UI UX Pro Max

    sundial-org/awesome-openclaw-skills

    UI/UX design intelligence and implementation guidance for building polished interfaces.

    663 GitHub starsUsed in 2 repos~657 tokens
    Frontend & DesignAuto-check passed
  • Glide

    SrivarsanK/Glide

    Authoritative guide and toolset for AI agents to operate, configure, and visually design applications using Glide (@srivarsank/glide).

    120 GitHub stars~1.7k tokensUpdated 10 days ago
    Frontend & DesignAuto-check passed

More from 302ai/302-AI-Studio

  • Adversarial Reviewer

    302ai/302-AI-Studio

    Adversarial code review that breaks the self-review monoculture.

    132 GitHub starsUsed in 1 repo~3k tokens
    Auto-check passed
  • Electron

    302ai/302-AI-Studio

    Provides comprehensive guidance for Electron framework including main process, renderer process, IPC communication, window management, and desktop app development.

    132 GitHub stars~1.8k tokensUpdated 1 mo ago
    Auto-check passed
  • Commit And PR

    302ai/302-AI-Studio

    A skill your agent uses whenever the user wants to commit changes and create a Pull Request (e.g., 'commit and PR', 'push my changes', 'create a PR').

    132 GitHub stars~700 tokensUpdated 1 mo ago
    Auto-check passed
  • Create GitHub Pull Request for feature request from specification file using pullrequesttemplate.md template.

    132 GitHub starsUsed in 1 repo~406 tokens
    Auto-check passed

Questions about Sveltekit Svelte5 Tailwind Skill

What does Sveltekit Svelte5 Tailwind Skill do?

Comprehensive integration skill for building sites with SvelteKit 2, Svelte 5, and Tailwind CSS v4. Sveltekit Svelte5 Tailwind Skill is an agent skill from 302ai/302-AI-Studio.

When should I use Sveltekit Svelte5 Tailwind Skill?

Sveltekit Svelte5 Tailwind Skill fits situations like: tasks that involve CSS and styling.

How do I install Sveltekit Svelte5 Tailwind Skill in Claude Code?

Run `npx skills add 302ai/302-AI-Studio --skill sveltekit-svelte5-tailwind-skill -a claude-code`. Or copy the skill folder (.agents/skills/sveltekit-svelte5-tailwind-skill in 302ai/302-AI-Studio) into .claude/skills/sveltekit-svelte5-tailwind-skill in your project. Claude Code loads it when a task matches its description.

How do I install Sveltekit Svelte5 Tailwind Skill in Codex?

Run `npx skills add 302ai/302-AI-Studio --skill sveltekit-svelte5-tailwind-skill -a codex`. Or copy the skill folder (.agents/skills/sveltekit-svelte5-tailwind-skill in 302ai/302-AI-Studio) into .agents/skills/sveltekit-svelte5-tailwind-skill in your project. Codex loads it when a task matches its description.

Can I use Sveltekit Svelte5 Tailwind Skill in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add 302ai/302-AI-Studio --skill sveltekit-svelte5-tailwind-skill -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sveltekit-svelte5-tailwind-skill, .gemini/skills/sveltekit-svelte5-tailwind-skill, .github/skills/sveltekit-svelte5-tailwind-skill and .opencode/skills/sveltekit-svelte5-tailwind-skill in your project.

What does Sveltekit Svelte5 Tailwind Skill need to run?

Going by SKILL.md and its folder, Sveltekit Svelte5 Tailwind Skill needs the command-line tools its instructions call (npm). Our summary lists: Node.js.

Does Sveltekit Svelte5 Tailwind Skill access the network?

SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Sveltekit Svelte5 Tailwind Skill safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Sveltekit Svelte5 Tailwind Skill use?

Sveltekit Svelte5 Tailwind Skill is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Sveltekit Svelte5 Tailwind Skill use?

About 3.5k tokens (SKILL.md is roughly 14k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 89k tokens, read only when the agent opens those files.

What are the alternatives to Sveltekit Svelte5 Tailwind Skill?

Skills that share tags, products or a category with Sveltekit Svelte5 Tailwind Skill: Kill AI Slop (yetone/kill-ai-slop, 1.3k stars), Design Style (Castor6/tactus, 376 stars), Svelte Code Writer (kampsy/ui, 288 stars) and Kampsy UI (kampsy/ui, 288 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Sveltekit Svelte5 Tailwind Skill?

302ai (a GitHub organization) maintains it in 302ai/302-AI-Studio, which has 132 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on August 31, 2026.

Source: 302ai/302-AI-Studio on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.