// Research topics by verifying actual source content. Use when asked to research or study links and documentation.
SvelteKit remote functions guidance. Use for command(), query(), form() patterns in .remote.ts files.
Svelte component patterns. Use for web components, component libraries (Bits UI, Ark UI, Melt UI), form patterns, or third-party integration.
Svelte deployment guidance. Use for adapters, Vite config, pnpm setup, library authoring, PWA, or production builds.
Svelte runes guidance. Use for reactive state, props, effects, attachments, or migration. Covers $state, $derived, $effect, @attach. Prevents reactivity mistakes.
SvelteKit data flow guidance. Use for load functions, form actions, and server/client data. Covers +page.server.ts vs +page.ts, serialization, fail(), redirect(), error().
SvelteKit structure guidance. Use for routing, layouts, error handling, SSR, or svelte:boundary. Covers file naming, nested layouts, error boundaries, pending UI, and hydration.
| name | research |
| description | Research topics by verifying actual source content. Use when asked to research or study links and documentation. |
| allowed-tools | WebFetch, mcp__mcp-omnisearch__web_search, mcp__mcp-omnisearch__kagi_summarizer_process, Read, Grep, Bash, Task |
When researching, always fetch and verify actual sources:
# Always do this
WebFetch URL → read content → verify claims → present findings
# Never do this
WebSearch → present snippets without verification
Never present findings without examining actual source content.
Steps:
❌ Presenting search snippets as facts ❌ Trusting summaries without checking sources ❌ Citing sources you haven't read
If you can't verify (paywall, 404, contradictions): Say so explicitly. Don't present unverified info as fact.
For detailed patterns and examples: