メニュー
Change or review PBVex protocol and compatibility contracts across packages/protocol, TypeScript authoring/codegen, Go manifest and wire validation, runtime bridges, shared fixtures, canonical hashes, IDs, deployment artifacts, and protocol ADRs. Use for cross-language contributor work, not ordinary application code.
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-protocol |
| description | Change or review PBVex protocol and compatibility contracts across packages/protocol, TypeScript authoring/codegen, Go manifest and wire validation, runtime bridges, shared fixtures, canonical hashes, IDs, deployment artifacts, and protocol ADRs. Use for cross-language contributor work, not ordinary application code. |
Treat protocol changes as cross-language trust-boundary changes. A new manifest field, validator, wire value, error code, ID form, function kind, component definition, migration registration, or runtime bridge method must stay aligned across packages/protocol, packages/pbvex, Go deploy/schema/runtime code, clients, fixtures, and documentation.
Preserve canonical JSON, hashes, deterministic artifact/codegen output, strict unknown-key rejection, depth/node/byte budgets, and protocol-version behavior. Do not silently reinterpret persisted artifacts, IDs, cursors, migration history, or pinned deployment snapshots. Make compatibility or rejection explicit and test adversarial malformed input in both languages.
Update shared valid/invalid fixtures and golden vectors rather than writing isolated validators that can drift. Regenerate checked-in artifacts and API docs through their owning scripts. Update the owning protocol ADRs—ADR 001 for protocol/runtime shape and ADR 002 for migration modes/lifecycle—when durable contracts change; ADRs are not substitutes for executable parity tests.
Use focused tests while iterating, then run the complete protocol and backend parity gates:
pnpm --filter @pbvex/protocol test
pnpm --filter pbvex test
pnpm --filter @pbvex/client test
(cd backend && go test -count=1 ./internal/schema ./internal/deploy ./internal/runtime ./internal/pbvex)
pnpm docs:api && pnpm docs:verify
Pair this skill with pbvex-internals for Go runtime work and pbvex-operations for full PR/release verification. Consult CONTRIBUTING.md, the protocol ADRs, and current source before assuming an older ADR example is exhaustive.