Sveltest skill
Agents get proven Svelte 5 test patterns for Vitest Browser Mode and Playwright through a skill and CLI, not invented mocks.
- 113 ★ on the repository
- Last commit
- MIT
Minimal access
Why this level
- The CLI downloads examples from the repository over the network.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/sveltestDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewMinimal accessThe tool runs nothing and makes no network calls.
- The CLI downloads examples from the repository over the network.
This is third-party code. Review the repository files before installing.
What it does
Sveltest is a reference repository and CLI of test patterns for `vitest-browser-svelte`. The agent pulls proven examples for components, SvelteKit server routes, SSR and end-to-end flows instead of writing them from memory. The `.agents/skills/svelte-testing` directory holds an Agent Skills skill: a quick start, locator rules and fixes for common failures. The `list`, `get` and `search` commands return an example by component name or topic such as `form`.
Who it is for. Svelte 5 and SvelteKit developers moving from `@testing-library/svelte` to tests that run in a real browser.
Good fit when
- An agent writes a test for a login form with validation.
- Tests fail on strict locators after moving to Vitest Browser Mode.
- A SvelteKit server route must be checked with real `FormData` and `Request` objects.
- A team wants one testing ruleset for Claude Code and Cursor.
Not a fit when
- The project is not on Svelte 5.
- Tests run only in jsdom with no browser.
- You need a testing framework rather than examples and rules.
Example request
I need to test a login form with validation. Find patterns with `pnpx sveltest search form` and write the test.Limitations
The author calls the approach opinionated and minimal on mocks: external services such as databases still need replacing. Examples target Svelte 5, Vitest 4 and Playwright, so check compatibility for other versions. The CLI fetches examples from the repository and needs network access. The repository is large, so copy only the skill directory into the project rather than the whole example. One author maintains the repository as a personal project, so the rules reflect that taste rather than a Svelte standard.
How to disable. Delete the `.agents/skills/svelte-testing` directory from the project and remove `pnpx sveltest` mentions from agent instructions.
FAQ
How do I get a test example?
Run `pnpx sveltest get button` with the component name. `list` shows all patterns and `search form` finds examples by topic.
Which agents work?
It is an Agent Skills skill and not tied to Claude. The repository ships setups for Claude Code and Cursor, and other clients copy the whole directory including `references/`.
How is this different from regular docs?
Examples are written for an AI assistant and served on request. The agent does not read the whole repository.
Do tests need a browser?
Yes, Vitest Browser Mode runs tests in a real browser through Playwright. The templates do not suit a browserless mode.
Does the skill suit SvelteKit?
Yes. Examples cover server routes, hooks, form actions and SSR checks. Client and server are aligned through shared validation.
Discussion
No questions or reviews yet.
Related
Skills57 reference files on Playwright tests in TypeScript: the agent pulls the one that fits the task, from locators to CI sharding
Seven QA agents and ten skills for test automation: Playwright in TypeScript, Selenium in Java, API, accessibility and ISTQB.
A skill that lets an agent write and run Playwright scripts: page tests, forms, screenshots and link checks
Guides for agents writing and fixing Playwright tests, with advice on locators, waiting and diagnosing CI failures
Validates Agent Skills packages: structure, links, token weight and instruction quality, with optional LLM-as-judge scoring
A skill that tests your agent's code in a real browser: reads your changes, builds a test plan and runs it through Playwright with your own cookies
README in short
The project demonstrates browser testing for Svelte 5: components, server routes, SSR and end-to-end checks. Client-server consistency relies on shared validation and real request objects.