Individual skill
scaffold-tests
Set up Vitest for pracht routes, loaders, and middleware in browser mode or JSDOM, with `@pracht/test` helpers and runnable example tests. Use for "scaffold tests", "set up Vitest", "add unit tests", "test this loader", "test this route".
skills/scaffold-tests/SKILL.md
Source commit e7c088a615e0bc16659d7a307fe92910ae6bd546
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 8, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 106
- Repository last updated
- Nov 9, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- ai-agents Repository topic
- cloudflare-workers Repository topic
- framework Repository topic
- full-stack Repository topic
- llms-txt Repository topic
- mcp Repository topic
- preact Repository topic
- ssg Repository topic
- ssr Repository topic
- testing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
Read excerpt
# Pracht Scaffold Tests
Generate Vitest tests aligned with pracht's testing recipe
(<https://pracht.resynapse.dev/docs/recipes/testing>). Loaders and API handlers
are plain async functions — they test directly with no framework bootstrap.
Component tests need a renderer; the user picks the flavor.
## Step 1: Pick the rendering strategy
Use `AskUserQuestion` to choose between:
1. **Browser mode** — `vitest` with `@vitest/browser` and
`vitest-browser-preact`.
- Pros: real browser, real events, fewer hydration false positives,