VDK Docs
CLI

CLI Commands

Canonical reference for VDK CLI commands and retrieval/deployment workflows

CLI Commands Reference

This page reflects the current vdk command surface and canonical AI Context Schema v3 behavior.

CLI command semantics are the runtime authority for the ecosystem. Hub and Wiki should mirror this behavior and not redefine retrieval/adaptation/deployment rules.

Command Overview

vdk [command] [options]

Core project commands

  • init - initialize VDK for a project
  • scan - re-analyze and refresh project rules
  • status - inspect VDK and integration status
  • validate - validate schema/platform compatibility
  • generate - generate platform-specific context files
  • import - import existing assistant context files
  • convert - convert context formats between platforms

Blueprint library commands

  • sync - sync blueprints from Hub/repository
  • browse - browse repository/community blueprints
  • search - canonical metadata search (kind/specificity/platform)
  • deploy - deploy a blueprint to active integrations
  • analyze - inspect dependencies/relationships for a blueprint
  • repo-stats - repository statistics and compliance summary
  • platform - list platform-compatible blueprints
  • create - scaffold a new blueprint document

Migration commands

  • migrate - migrate existing AI contexts/rules into VDK format
  • schema-migrate - migrate blueprints to schema v3
  • schema-upgrade - upgrade blueprint content from legacy schema versions

Ecosystem commands

  • hub-generate - generate package content from VDK Hub
  • publish - publish rule files to community channels
  • mcp - manage MCP servers and related integration state
  • plugin - manage VDK plugins
  • team:share - share team configuration
  • team:config - sync team configuration resources

Canonical retrieval and curation

search and deploy operate on canonical schema metadata:

  • Canonical kind taxonomy (for --kind):
    • project-memory, conditional-rule, skill, command, workflow, agent, hook, mcp-integration, plugin-distribution
  • Specificity layers (--specificity): L0, L1, L2, L3, L4
  • Default retrieval behavior:
    • blended selection across L0-L3
    • L4 provenance variants excluded unless --include-l4 is provided

High-value workflows

Initialize and validate project setup

vdk init --interactive
vdk status --verbose
vdk validate

Curated blueprint discovery and deployment

vdk search --kind skill --platform claude-code
vdk search --query nextjs --specificity L2
vdk deploy <blueprint-id>

Migration and schema alignment

vdk migrate --dry-run
vdk schema-migrate --verbose
vdk schema-upgrade

Notes

  • Use vdk --help for full command list.
  • Use vdk <command> --help to see command-specific options.
  • Option sets evolve over time; this page tracks canonical behavior and deployment workflow.

On this page