Agent skill

Svelte Testing

Fix and create Svelte 5 tests with vitest-browser-svelte and Playwright.

MITAuto-check passedTesting & QA

Install Svelte Testing

skills CLI

$ npx skills add spences10/sveltest --skill svelte-testing -a claude-code

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

GitHub CLI

$ gh skill install spences10/sveltest svelte-testing --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/spences10/sveltest.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/svelte-testing .claude/skills/svelte-testing && 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/

Paste into Claude Code

Install the "svelte-testing" agent skill from https://github.com/spences10/sveltest/tree/main/.agents/skills/svelte-testing into .claude/skills/svelte-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "svelte-testing", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/spences10/sveltest/tree/main/.agents/skills/svelte-testing

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add spences10/sveltest --skill svelte-testing -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install spences10/sveltest svelte-testing --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/spences10/sveltest.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/svelte-testing .agents/skills/svelte-testing && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "svelte-testing" agent skill from https://github.com/spences10/sveltest/tree/main/.agents/skills/svelte-testing into .agents/skills/svelte-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "svelte-testing", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add spences10/sveltest --skill svelte-testing -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install spences10/sveltest svelte-testing --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/spences10/sveltest.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/svelte-testing .cursor/skills/svelte-testing && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "svelte-testing" agent skill from https://github.com/spences10/sveltest/tree/main/.agents/skills/svelte-testing into .cursor/skills/svelte-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "svelte-testing", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/spences10/sveltest.git --path .agents/skills/svelte-testing

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add spences10/sveltest --skill svelte-testing -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install spences10/sveltest svelte-testing --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/spences10/sveltest.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/svelte-testing .gemini/skills/svelte-testing && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "svelte-testing" agent skill from https://github.com/spences10/sveltest/tree/main/.agents/skills/svelte-testing into .gemini/skills/svelte-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "svelte-testing", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install spences10/sveltest svelte-testing

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add spences10/sveltest --skill svelte-testing -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/spences10/sveltest.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/svelte-testing .github/skills/svelte-testing && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "svelte-testing" agent skill from https://github.com/spences10/sveltest/tree/main/.agents/skills/svelte-testing into .github/skills/svelte-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "svelte-testing", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add spences10/sveltest --skill svelte-testing -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install spences10/sveltest svelte-testing --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/spences10/sveltest.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/svelte-testing .opencode/skills/svelte-testing && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "svelte-testing" agent skill from https://github.com/spences10/sveltest/tree/main/.agents/skills/svelte-testing into .opencode/skills/svelte-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "svelte-testing", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: svelte-testing
GitHub stars: 113
Token cost: ~579 tokens
SKILL.md length: 114 words
Files: 9 (incl. references)
Skills in repo: 1
Repo updated: Oct 8, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Fix and create Svelte 5 tests with vitest-browser-svelte and Playwright.

Fixing broken tests
SKILL.md covers Quick Start, Core Principles, Reference Files and Notes
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
Debugging failures

What it does

Svelte Testing is an agent skill from spences10/sveltest. 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.

Its SKILL.md is about 580 tokens, which your agent loads only when the skill is triggered. The skill folder holds 9 other files, including reference files (for example `README.md`, `references/client-examples.md` and `references/client-server-alignment.md`).

It sits in Testing & QA, covering Unit testing, Browser testing and End-to-end testing. It works with Svelte, Playwright, Vitest and SvelteKit. The repository describes itself as: Comprehensive Svelte 5 testing examples and patterns using Vitest Browser Mode, Playwright, and vitest-browser-svelte. The licence is MIT.

When your agent uses it

Fixing broken tests
Debugging failures
Writing unit/SSR/e2e tests
Working with vitest/Playwright

Example prompts

“/svelte-testing”

What it can do on your machine

Read from SKILL.md and the folder at commit 54d345e. 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
No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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

Svelte Testing loads about 579 tokens when it runs, and up to ~5.3k if it reads all its reference files. Until then it costs about 50 tokens; SKILL.md has 114 words of instructions outside code blocks.

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

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 spences10/sveltest at commit 54d345e, republished under its MIT licence (© spences10). 114 words, ~579 tokens.

Download SKILL.mdSave it as .claude/skills/svelte-testing/SKILL.md (or your agent's skills folder). This skill also uses 8 other files; get the full folder from GitHub.

name: svelte-testing
description: 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.

Svelte Testing

Quick Start

typescript

// Client-side component test (.svelte.test.ts)
import { render } from 'vitest-browser-svelte';
import { expect } from 'vitest';
import Button from './button.svelte';

test('button click increments counter', async () => {
	const page = await render(Button);
	const button = page.getByRole('button', { name: /click me/i });

	await button.click();
	await expect.element(button).toHaveTextContent('Clicked: 1');
});

Core Principles

Always use locators: page.getBy*() methods, never containers
Multiple elements: Use .first(), .nth(), .last() to avoid strict mode violations
Use untrack(): When accessing $derived values in tests
Real API objects: Test with FormData/Request, minimal mocking

Reference Files

Notes

In component tests, test form state without submitting SvelteKit forms; use await expect.element() for locator assertions
In Playwright E2E, submit real forms and use await expect(locator)
Colocate .svelte.test.ts (client), .test.ts (Node), .ssr.test.ts (optional SSR), and .e2e.ts (Playwright)
CLI baseline: client/server projects and assertion enforcement; Playwright matches **/*.e2e.{ts,js}
Import page from vitest/browser; await render with renderer v3
Importing render registers cleanup without a setup file

<!--
PROGRESSIVE DISCLOSURE GUIDELINES:
- Keep this file ~50 lines total (max ~150 lines)
- Use 1-2 code blocks only (recommend 1)
- Keep description <200 chars for Level 1 efficiency
- Move detailed docs to references/ for Level 3 loading
- This is Level 2 - quick reference ONLY, not a manual
-->

Files

SKILL.md and 8 other files (references) in .agents/skills/svelte-testing of spences10/sveltest.

SKILL.md
README.md
references/client-examples.md
references/client-server-alignment.md
references/core-principles.md
references/critical-patterns.md
references/foundation-first.md
references/server-ssr-examples.md
references/troubleshooting.md

Open the folder on GitHubat commit 54d345e

Compare with similar skills

Svelte Testing 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.

Svelte Testing compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Svelte Testing this skillspences10/sveltest	113	—	~579	Automated safety check: Pass	MIT	today
Ha Frontend Testinghome-assistant/frontend	5.7k	—	~1.7k	Automated safety check: Pass	Apache-2.0	today
Frontend Typescript Testingshinpr/ai-coding-project-boilerplate	232	—	~1.5k	Automated safety check: Pass	MIT	4 days ago
Test CommanderEliasOulkadi/shokunin	114	—	~3k	Automated safety check: Notes	MIT	3 days ago
Frontend Typescript Testingshinpr/ai-coding-project-boilerplate	232	—	~843	Automated safety check: Pass	MIT	4 days ago
Frontend Typescript Testingshinpr/ai-coding-project-boilerplate	232	—	~692	Automated safety check: Pass	MIT	4 days ago

Similar skills

Ha Frontend Testing
home-assistant/frontend
Home Assistant frontend testing and validation workflow. An agent skill from home-assistant/frontend.
5.7k GitHub stars~1.7k tokensUpdated today
Testing & QAAuto-check passed
Frontend Typescript Testing
shinpr/ai-coding-project-boilerplate
Designs frontend tests using the repository's configured React test and browser harnesses, including RTL, MSW, Vitest, and Playwright when present.
232 GitHub stars~1.5k tokensUpdated 4 days ago
Testing & QAAuto-check passed
Test Commander
EliasOulkadi/shokunin
Generate unit, integration, E2E, and visual regression tests following the Testing Trophy methodology (80% integration).
114 GitHub stars~3k tokensUpdated 3 days ago
Testing & QAAuto-check: notes
Frontend Typescript Testing
shinpr/ai-coding-project-boilerplate
リポジトリで設定済みのReactテスト・ブラウザハーネスを使用してフロントエンドテストを設計。RTL、MSW、Vitest、Playwrightが存在する場合に適用。コンポーネント、loading/error state、統合、フロントエンドE2Eテストの追加・レビュー時に使用。
232 GitHub stars~843 tokensUpdated 4 days ago
Testing & QAAuto-check passed
Frontend Typescript Testing
shinpr/ai-coding-project-boilerplate
使用仓库已配置的 React 测试与浏览器测试工具（包括 RTL、MSW、Vitest，以及存在时的 Playwright）设计前端测试。适用于新增或评审组件测试、加载/错误状态测试、集成测试或前端 E2E 测试时。
232 GitHub stars~692 tokensUpdated 4 days ago
Testing & QAAuto-check passed
Angular Testing
Kilo-Org/kilo-marketplace
Write unit and integration tests for Angular v20+ applications using Vitest or Jasmine with TestBed and modern testing patterns.
190 GitHub stars~2.9k tokensUpdated 9 days ago
Testing & QAAuto-check passed

Works with

Questions about Svelte Testing

What does Svelte Testing do?

Fix and create Svelte 5 tests with vitest-browser-svelte and Playwright. Svelte Testing is an agent skill from spences10/sveltest. Fix and create Svelte 5 tests with vitest-browser-svelte and Playwright.

When should I use Svelte Testing?

Svelte Testing fits situations like: fixing broken tests; debugging failures; writing unit/SSR/e2e tests; working with vitest/Playwright.

How do I install Svelte Testing in Claude Code?

Run `npx skills add spences10/sveltest --skill svelte-testing -a claude-code`. Or copy the skill folder (.agents/skills/svelte-testing in spences10/sveltest) into .claude/skills/svelte-testing in your project. Claude Code loads it when a task matches its description.

How do I install Svelte Testing in Codex?

Run `npx skills add spences10/sveltest --skill svelte-testing -a codex`. Or copy the skill folder (.agents/skills/svelte-testing in spences10/sveltest) into .agents/skills/svelte-testing in your project. Codex loads it when a task matches its description.

Can I use Svelte Testing 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 spences10/sveltest --skill svelte-testing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/svelte-testing, .gemini/skills/svelte-testing, .github/skills/svelte-testing and .opencode/skills/svelte-testing in your project.

What does Svelte Testing need to run?

SKILL.md names no scripts, command-line tools or credentials: Svelte Testing is instructions for the agent only.

Does Svelte Testing access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Svelte Testing 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 Svelte Testing use?

Svelte Testing is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Svelte Testing use?

About 579 tokens (SKILL.md is roughly 2.3k 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 4.7k tokens, read only when the agent opens those files.

What are the alternatives to Svelte Testing?

Skills that share tags, products or a category with Svelte Testing: Ha Frontend Testing (home-assistant/frontend, 5.7k stars), Frontend Typescript Testing (shinpr/ai-coding-project-boilerplate, 232 stars), Test Commander (EliasOulkadi/shokunin, 114 stars) and Frontend Typescript Testing (shinpr/ai-coding-project-boilerplate, 232 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Svelte Testing?

spences10 (a GitHub user) maintains it in spences10/sveltest, which has 113 GitHub stars. The repository was last updated on October 8, 2026.

Source: spences10/sveltest on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Svelte Testing

Facts

At a glance

What it does

When your agent uses it

Example prompts

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Svelte Testing

Quick Start

Core Principles

Reference Files

Notes

Files

Compare with similar skills

Similar skills

Ha Frontend Testing

Frontend Typescript Testing

Test Commander

Frontend Typescript Testing

Frontend Typescript Testing

Angular Testing

Related

Questions about Svelte Testing