base

Enforce Node.js 22+ and Next.js 15+ governance for Vovk.ts skills.

52|Updated Jul 12, 2023
One-click install
npx skills add https://github.com/finom/vovk --skill base-finom
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: base
Source: https://github.com/finom/vovk/tree/main/packages/claude-plugin/skills/base
Command: npx skills add https://github.com/finom/vovk --skill base-finom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a canonical base governance layer for Vovk skills, ensuring consistent policy, runtime requirements, and contract points across the codebase.

Core Features & Use Cases

  • Establishes a single source of truth for schema artifacts, templates, and environment requirements (Node 22+, Next 15+) that all vovk:* skills reference.
  • Serves as the default, always-loaded context whenever a new vovk skill is added, ensuring safe, predictable behavior and alignment with project conventions.
  • Documents conventions like schema endpoint, template names, and policy push rules to accelerate onboarding and auditing.

Quick Start

Ensure this base context is loaded alongside any vovk:* skill when configuring a Next.js project.

Frequently Asked Questions about base

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce consistent schema conventions and runtime policies across a Next.js project?

To enforce consistent schema conventions, you need a foundational governance layer that preserves policy, templates, and runtime requirements across all segments. This establishes a single source of truth ensuring predictable behavior and alignment during codegen.

What are the Node.js and Next.js version requirements for Vovk.ts development?

The Vovk.ts development environment requires Node.js 22+ and Next.js 15+ as prerequisites. These versions are enforced by the base governance layer to ensure compatibility with the canonical policy surface and runtime behavior.

How do I onboard a new Vovk skill into an existing codebase?

To onboard a new Vovk skill, load the base context alongside it to ensure safe, predictable behavior. This default context aligns the new skill with existing schema artifacts, template names, and policy push conventions.

Why does my Vovk.ts codegen output differ across project segments?

Codegen output differs across segments when a single source of truth for schema artifacts and templates is missing. Applying a foundational governance layer documents canonical conventions and ensures consistent behavior across multi-segment projects.

What is the canonical policy surface for Vovk.ts skills?

The canonical policy surface for Vovk.ts skills is a documented set of schema conventions, template names, and _schema_ endpoint rules. It is established by a base governance layer to accelerate onboarding and auditing.