メニュー
Build, review, or test Svelte 5 PBVex integrations using @pbvex/svelte, with runes-first query state, context-provided clients, reactive arguments, conditional queries, and component-lifecycle cleanup. Use for Svelte components consuming PBVex.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Implement or troubleshoot PBVex and PocketBase application authentication, including auth collections, signup, password, OTP, OAuth2, MFA, auth stores, refresh, impersonation, logout, SSR initialization, and server-side authorization. Use for user identity and token lifecycle work, not deployment credentials.
Build or review PBVex application backends, including deployed function and return contracts, strict object validators and DTOs, application errors, schema, indexed queries and pagination, mutations, actions, authorization, relationships, outbound HTTP, HTTP actions, email templates, generated references, nested calls, and scheduling. Use for application code under pbvex/ and generated-contract workflows.
Route PBVex application and repository work across TypeScript authoring, database queries, authentication and authorization, the Go/PocketBase backend, typed clients, UI integrations, components, deployment, and documentation. Use when starting, planning, debugging, reviewing, or making an end-to-end PBVex change and when selecting a specialized PBVex skill.
Implement, review, troubleshoot, or operate PBVex file and image storage, including upload URLs, StorageId fields, trusted metadata, identity/capability/public downloads, CDN caching, schema-declared thumbnails, local or S3 object storage, limits, deletion, and migration behavior.
Implement or troubleshoot typed PBVex client calls, configuration, structured errors, cancellation, and client-side storage transfers with @pbvex/client. Use for browser, Node, or framework-agnostic integration; pair with pbvex-auth or pbvex-realtime for those subsystems.
Define, mount, evolve, or troubleshoot PBVex components, including component schemas, function bindings, typed mount arguments, environment declarations, generated namespaces, and isolated component data. Use for code involving defineComponent, defineApp, mount, or component references.
| name | pbvex-svelte |
| description | Build, review, or test Svelte 5 PBVex integrations using @pbvex/svelte, with runes-first query state, context-provided clients, reactive arguments, conditional queries, and component-lifecycle cleanup. Use for Svelte components consuming PBVex. |
Use @pbvex/svelte as a Svelte 5, runes-first layer over an independently installed @pbvex/client. Set a client in Svelte context during component initialization, then use the current package exports from child components. Prefer rune state and markup reads over Svelte stores.
The current package is Svelte 5 runes-first and intentionally breaks from the legacy store API. Inspect the installed/versioned exports and types before coding because an application may have a different package version.
sed -n '1,240p' packages/svelte/src/index.ts
sed -n '1,240p' packages/svelte/package.json
rg -n "export |useQuery|setClient|skip|QueryState" packages/svelte/src packages/svelte/dist
pnpm --filter @pbvex/svelte test
Use setClient in a layout/root during initialization and getClient only where context is available. Use the primary query utility with generated public references. Treat query output as reactive rune-backed state and read its data, error, and loading fields directly in markup—do not $-subscribe or use svelte/store helpers unless the installed API explicitly says it exposes a store.
When arguments depend on $state() or $props(), supply the supported reactive getter so a changed argument replaces the watch. Use the exported skip sentinel for a disabled conditional query. Use the mutation/action utilities for typed async calls. Let component destruction clean up query subscriptions, and explicitly close a client only at its true application/test owner.
Under SvelteKit SSR, create browser-backed auth storage and live subscriptions only in the browser lifecycle; do not read localStorage during server initialization or share an authenticated client/store across server requests. Use pbvex-auth for token stores and pbvex-realtime for transport semantics.
Mount a small Svelte harness so rune APIs run during component initialization. Use the supported explicit/test client form, drive state with Svelte test utilities, then assert reactive state and unsubscribe cleanup after unmount. Do not test current rune query state as a legacy readable store.
Do not edit packages/svelte or Svelte documentation as part of application integration work unless explicitly asked; verify the installed version instead.