VDK CLI Overview

VDK-CLI is the execution core of the VDK ecosystem.

It turns canonical blueprint metadata into runtime behavior:

• selects relevant curated blueprints,
• adapts them to tool-native carriers,
• deploys them into user projects deterministically.

CLI Role in the Ecosystem

The ecosystem operates in this strict order:

1. ai-context-schema defines semantics
2. VDK-Blueprints stores curated inventory
3. VDK-CLI executes retrieval/adaptation/deployment
4. VDK-Hub exposes synchronized discovery/install surfaces
5. VDK-Wiki documents contract and behavior

CLI behavior is authoritative for runtime semantics.

What CLI Does

1) Detect project context

• language/framework/runtime signals
• repository and directory context
• integration targets (tool/platform)

2) Retrieve curated candidates

• canonical kind-based filtering
• specificity-aware retrieval (L0..L4)
• default curated blend across L0-L3
• optional L4 inclusion only when explicitly requested

3) Adapt safely

Adapter output classification is explicit:

• lossless
• lossy
• unsupported

4) Deploy deterministically

Selected artifacts are installed into the correct target carrier paths through:

• vdk deploy <blueprint-id>

Standardized Curated Library Behavior

CLI operational defaults are designed to avoid noise while preserving coverage:

• include generic + specific layers (L0-L3)
• exclude provenance variants (L4) by default
• preserve explicit adaptation outcome on conversion/deployment

This enables one standardized blueprint library to serve broad and specialized use cases without flooding users with duplicates.

Common Command Flow

• vdk search --kind skill --platform claude-code
• vdk search --query nextjs --specificity L2
• vdk search --query nextjs --include-l4 (audit/provenance mode)
• vdk deploy <blueprint-id>

Relationship to Hub and Wiki

• Hub should reflect CLI filters and defaults.
• Wiki should document CLI behavior as operational truth.
• Neither should invent alternative retrieval/deployment rules.

Practical Outcome

With CLI as runtime interpreter and curated blueprint inventory as input, users can deploy generic and specialized blueprints to their projects with consistent, low-noise, and deterministic behavior.