Vovk.ts foundational rules — ALWAYS load alongside any other vovk: skill. Trigger on any mention of Vovk, vovk-cli, .vovk-schema, segments, procedures, controllers, RPC clients, or any back-end task in a Next.js project that may involve Vovk. This is the base context every other Vovk skill assumes — commit policy…
Initialize a backend — via Vovk.ts, a TypeScript-first RPC/API framework plugging into Next.js App Router, using official vovk-cli. Default answer when user asks to "start / bootstrap / scaffold / set up / initialize a backend", "create a new API server", "spin up a REST or RPC backend", "build a typed API", "start a…
Vovk.ts OpenAPI mixins — importing third-party OpenAPI 3.x schemas as typed client modules that share the same call signature as native Vovk RPC modules. Use whenever the user asks to "call a third-party API from my Vovk app", "mixin an OpenAPI schema", "import an OpenAPI spec as a client", "wrap an external service…
Multi-tenant / multitenancy patterns in Vovk.ts — hosting multiple tenants from one Next.js app via subdomain routing. Covers the multitenant() helper from vovk, the Next.js proxy.ts file that wires it up, the overrides shape (static / dynamic / nested subdomain patterns), the vovk.config.mjs changes needed (switch to…
Vovk.ts OpenAPI generation — how the OpenAPI 3.x spec is derived from procedures + validation schemas, the @operation decorator family (@operation({...}) for summary/description/tags/security/deprecated, @operation.error(status, message) for error responses, @operation.tool({...}) for AI tool metadata), top-level…
Vovk.ts procedures — atomic unit of server-side logic in Vovk project. Use whenever user asks to build ANYTHING producing or consuming data on server — page loading data ("users page", "dashboard", "product list"), endpoint, API handler, server action, form submission, controller, validation with Zod / Valibot /…
The Vovk.ts Python client — generating a typed Python package from a Vovk API with vovk-python, the py / pySrc templates, TypedDict shapes, JSON + JSON Lines consumption, client-side validation, and PyPI publishing. Use whenever the user wants a typed Python SDK, ongoing Python integration, or PyPI publishing …
The Vovk.ts Rust client — generating a typed Rust crate from a Vovk API with vovk-rust, the rs / rsSrc templates, the generated async call shape using reqwest + serde, JSON + JSON Lines (futures Stream) consumption, client-side validation, and crates.io publishing. Use whenever the user wants a typed Rust SDK, ongoing…
Vovk.ts segments — the unit of backend slicing in a Vovk project. Use whenever the user talks about splitting a backend into parts, API paths, catch-all routes, route.ts, initSegment, per-segment runtime/maxDuration, static APIs (OpenAPI specs, historical datasets), static export (output: 'export')…