By fubits1
Automate Svelte 5 workflows by enforcing code style rules on edits, generating structured JSDoc component docs, wiring Storybook stories as Vitest browser tests with MSW support, previewing stories via Playwright, and creating or fixing unit, SSR, and E2E tests.
Document a Svelte component using @component JSDoc. Auto-invoke when asked to document a .svelte component. Reads the component, analyzes its interface, and writes a structured @component comment block.
Svelte component code style rules. Auto-invoke when creating new .svelte files or editing Svelte component structure. Covers component documentation comments and Svelte-specific style conventions.
Svelte CSF (@storybook/addon-svelte-csf) + @storybook/addon-vitest — .stories.svelte as Vitest browser tests, vitest.config + test.projects, play on <Story>, tags, storybookUrl/script, preview MSW. Use when wiring or debugging Svelte Storybook tests in Vitest/CI — not for React/Vue/CSF3 .ts story files. If there is no vitest.config.* and Vitest only lives under vite.config test:, ask before restructuring.
Storybook workflow — MCP tools, fixtures, CSS import chains. Auto-invoke when working with Storybook stories or components.
Fix and create Svelte 5 tests with vitest-browser-svelte and Playwright. Use when fixing broken tests, debugging failures, writing unit/SSR/e2e tests, or working with vitest/Playwright.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Claude Code plugin marketplace for Svelte developers. Disciplined workflows for frontend development, Svelte components, and Svelte 5 migration.
Five plugins. Four with layered dependencies, one standalone:
agent <-- frontend <-- svelte-5 <-- svelte-5-migration
bonus (standalone)
| Plugin | Skills/Hooks | What it does |
|---|---|---|
| agent | 4 skills | Research, planning, self-checks, completion verification |
| frontend | 11 skills | Validation, pixel-perfect, editing, code style, testing, migration |
| svelte-5 | 5 skills | Svelte code style, component docs, Storybook, Svelte testing |
| svelte-5-migration | 1 skill | Svelte 3/4 to 5 migration workflow |
| bonus | 2 hooks | nogrep (force dedicated tools), formatter (auto-format after edits) |
/plugin marketplace add fubits1/svelte-skills
For local development/testing:
/plugin marketplace add /path/to/svelte-skills
Superpowers plugin (required by agent):
/plugin install superpowers
Svelte MCP (required by svelte-5 and svelte-5-migration). Provides svelte:svelte-code-writer, svelte:svelte-core-bestpractices, and the Svelte autofixer (mcp__svelte__svelte-autofixer):
/plugin marketplace add sveltejs/ai-tools
/plugin install svelte
Or directly via CLI:
claude mcp add -t stdio -s project svelte -- npx -y @sveltejs/mcp
Playwright MCP (required by frontend). Provides browser screenshots, navigation, and browser_evaluate for measurements:
claude mcp add playwright -- npx @playwright/mcp@latest
See Playwright MCP docs for options (headless, scope, etc.).
Storybook MCP (optional, used by svelte-5:storybook). Provides story instructions and preview tools:
pnpm add -D @storybook/addon-mcp
Then add @storybook/addon-mcp to your .storybook/main.ts addons. The MCP server runs at http://localhost:6006/mcp when Storybook is running. See @storybook/addon-mcp.
/plugin install agent
/plugin install frontend
/plugin install svelte-5
/plugin install svelte-5-migration
/plugin install bonus
bonus is standalone and optional — install it independently of the others.
See SETUP.md for copying template scripts, wiring package.json tasks, and installing dev dependencies.
Skills in this marketplace have auto-invocation triggers defined in their descriptions. Claude Code may invoke them automatically when it detects relevant context (e.g., editing a .svelte file, declaring a task done, starting a migration). You can also invoke any skill manually at any time via /skill-name. To disable auto-invocation for a specific skill, add disable-model-invocation: true to that skill's SKILL.md frontmatter.
Claude Code allocates 1% of context window (fallback: 8,000 chars) for skill descriptions. Each description is capped at 250 chars. With this marketplace (~21 skills) plus superpowers (~14) and Svelte MCP (~2), you'll have ~37 skill descriptions loaded.
Run /context to check for budget warnings. Override with SLASH_COMMAND_TOOL_CHAR_BUDGET=<chars>.
Source: Claude Code skills docs
grill-me (get relentlessly interviewed about a plan or design — or use it to grill the agent about its own plan before it starts implementing).These tools are referenced by the skills. Not all are required -- install what your project uses.
Frontend development discipline — validation, pixel-perfect measurement, editing, code style, testing, migration baselines.
Svelte 3/4 to 5 migration — phased workflow, pattern conversions, interop rules, known traps.
npx claudepluginhub fubits1/svelte-skills --plugin svelte-5Comprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.
Tools to maintain and improve CLAUDE.md files - audit quality, capture session learnings, and keep project memory current.
Lazy senior dev mode. Forces the simplest, shortest solution that actually works: YAGNI, stdlib first, no unrequested abstractions.
Develop, test, build, and deploy Godot 4.x games with Claude Code. Includes GdUnit4 testing, web/desktop exports, CI/CD pipelines, and deployment to Vercel/GitHub Pages/itch.io.
A growing collection of Claude-compatible academic workflow bundles. Covers scientific figures, manuscript writing and polishing, reviewer assessment, citation retrieval, data availability, paper reading, literature search, response letters, paper-to-PPTX conversion, and evidence-grounded Chinese invention patent drafting. Rules are organized as reusable skill folders with explicit workflows and quality checks.
Reliable automation, in-depth debugging, and performance analysis in Chrome using Chrome DevTools and Puppeteer