메뉴
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.
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.
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.
Guide and configure a new PBVex deployment from initial topology decisions through backend provisioning, data directory, superuser credentials, TLS and proxy settings, canonical URL, environment bindings, storage, backups, application target configuration, first atomic deploy, smoke tests, and rollback readiness. Use when a user is setting up a local, staging, or production PBVex environment for the first time or wants an interactive deployment walkthrough.
| name | pbvex-client |
| description | 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. |
Use @pbvex/client with generated public references; application code must install the runtime package separately from this skill.
import { Client } from '@pbvex/client';
import { api } from '../pbvex/_generated/api.js';
const client = new Client('http://127.0.0.1:8090');
const rows = await client.query(api.messages.list, { channel: 'general' });
Call only public query, mutation, and action functions. Prefer generated references for typed visibility, arguments, and returns. String paths are a supported untyped fallback for dynamic or already-typed integrations; do not manufacture them when generated references are available. Never use deployment superuser tokens in a client. Read current exports/options before changing integration code:
sed -n '1,220p' packages/client/src/index.ts
rg -n "class Client|watch\(|authStore|authWith|setAuth|generateUpload|PBVexError" packages/client/src docs/guides
pnpm --filter @pbvex/client test
PBVex includes PocketBase auth routes and a native client auth API. Use pbvex-auth for collection provisioning, auth methods, stores, SSR, and token lifecycle rather than hand-written fetches.
For externally managed tokens, provide an application record token as auth (string or provider) or use setAuth/clearAuth; per-call auth can override it. An app token identifies a PocketBase record and cannot deploy. Never put a PocketBase superuser deployment token in client code. Server functions remain responsible for authorization and ownership regardless of sign-in method.
Use ClientOptions for injected fetch, URL/base URL, timeout, auth store, client-side limits, or a test realtime transport. Close clients with client.close() when their owner is destroyed; this is distinct from canceling in-flight calls.
Use client.watch for SSE query results and always retain its unsubscribe function. Load pbvex-realtime for initial-result, deduplication, retry, proxy, auth refresh, and transport-test semantics.
Handle structured backend failures with PBVexError and inspect its code, details, and requestId. Keep transport/proxy failures distinct from structured application errors. Pass AbortSignal in call options for cancellation and treat its AbortError separately from backend rejection. Inspect client.connectionState and realtime callbacks when diagnosing reconnects.
Storage is a two-step flow: an authorized server function creates a short-lived, single-use upload URL, the client POSTs bytes, then stores the returned opaque StorageId. Read trusted upload metadata instead of decoding image dimensions in the browser. Do not invent upload endpoints or retry a consumed URL.
Download URLs come from authorized server functions. Identity mode is the default; when created by an authenticated function it requires that same caller token, while an anonymously created identity URL needs no Authorization header but is itself sensitive until expiry. Capability mode is a short-lived bearer URL suitable for an image src; public mode is stable and CDN-cacheable for intentionally public assets. Use the pbvex-storage skill for image policies, thumbnail selectors, metadata trust boundaries, and lifecycle details.