nathabonfim59

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.

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.

Modify, debug, review, or operate PBVex's own Go/PocketBase implementation, including runtime contracts, HTTP and realtime routes, storage internals, schema activation, migrations, and the single-binary boundary. Use for PBVex repository work under backend/, not for building an application backend or a product platform with PBVex.

Initialize a new Convex backend from scratch with schema, auth, and basic CRUD operations. Use when starting a new project or adding Convex to an existing app.

Effect v4 (beta) development and v3 → v4 migration guidance. Use when building new Effect v4 code or upgrading from v3, including API renames, behavior changes, before/after examples, and v4-specific patterns for services, layers, generators, yieldable, error handling, and schema codecs.

General debugging methodology for complex or intermittent failures in any multi-layer system (pipelines, builds, network, DB, queues, integrations, CI). Use it when the symptom is generic/compressed (exit code, "error 500", timeout), when a theory-based fix doesn't change the behavior, or when there is more than one component between the cause and the symptom.

Reference for the Video.js HTML player's `<video-player>` custom element store API — state signals, actions (play/pause/seek/volume/fullscreen/pip/subtitles), lifecycle methods (attach/detach/destroy), feature presets, and feed unload/reload patterns. Activate whenever writing or debugging Video.js player code that accesses `player.store`.

Use the md-fetch CLI to retrieve web content as clean Markdown, save output to files, or run the local HTTP API server. Activate when users ask to fetch web pages, convert pages to Markdown, batch fetch URLs via API, or troubleshoot browser selection and fetch failures in this repository.

Look up Neovim (Nvim) help docs from the LOCAL runtime on disk (no network). Use whenever the task involves Nvim APIs, options, Lua stdlib, vim.pack, autocmds, lsp, lspconfig, filetype, plugin development, or any `:help <topic>` reference. Authoritative for the user's installed Nvim version.

Spawn `claude-kimi` as an interactive teammate in a tmux window so the user can watch/steer it live, while Claude and claude-kimi message each other via `tmux send-keys`. Use this whenever a user asks to delegate implementation to claude-kimi, or whenever the memory rule "delegate implementation to claude-kimi" applies and an interactive session is useful.

Test the dncensor TUI using tmux. Never run the app from the agent — always use a tmux pane so you can see the UI and interact properly.

Spawn `claude-zai` as an interactive teammate in a tmux window so the user can watch/steer it live, while Claude and claude-zai message each other via `tmux send-keys`. Use this whenever a user asks to delegate implementation to claude-zai, or whenever the memory rule "delegate implementation to claude-zai" applies and an interactive session is useful.