vcp-init

Create global and project VCP config files and detect plugin paths.

14|3|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/Z-M-Huang/vcp --skill vcp-init
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vcp-init
Source: https://github.com/Z-M-Huang/vcp/tree/main/plugins/vcp/skills/vcp-init
Command: npx skills add https://github.com/Z-M-Huang/vcp --skill vcp-init

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Initialize VCP configuration for new projects by creating global and project config files, and by detecting the plugin path for seamless setup.

Core Features & Use Cases

  • Creates a global config at ~/.vcp/config.json and a project config at .vcp/config.json to store standards references and plugin paths.
  • Detects frameworks, scopes, and plugin paths to tailor the setup for the current project.
  • Guides through a structured initialization workflow with prompts to confirm standards URL, plugin path, scopes, and defaults.

Quick Start

Run this skill to initialize both global and project configs for a new project.

Frequently Asked Questions about vcp-init

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

FAQPage Schema
How do I initialize project configuration files for VCP?

VCP project configuration initialization creates a global config at ~/.vcp/config.json and a project config at .vcp/config.json. It validates required files and prompts for defaults to enforce consistent standards across environments.

What is the VCP plugin path discovery process during project setup?

The VCP plugin path discovery process detects frameworks, scopes, and plugin locations during project initialization. It writes configuration data following the official vcp schema to enable seamless project setup and consistent standards enforcement across environments.

Do I need any dependencies to set up VCP config for a new project?

No dependencies are required to set up VCP config for a new project. The initialization workflow is self-contained, guiding you through prompts to confirm standards URL, plugin path, scopes, and defaults before writing the configuration data.

Can I customize scopes and defaults when creating VCP config files?

Yes, you can customize scopes and defaults when creating VCP config files. The structured initialization workflow prompts for user input to confirm the standards URL, plugin path, scopes, and defaults tailored to the current project environment.

Why does VCP initialization create both global and project config files?

VCP initialization creates both global and project config files to separate environment-wide standards from project-specific settings. The global config at ~/.vcp/config.json stores overarching standards, while the project config at .vcp/config.json tailors scopes and plugin paths.

How to validate required files before writing VCP config data?

To validate required files before writing VCP config data, the initialization skill checks for the presence of necessary files in your project directory. It ensures the environment meets official vcp schema requirements before prompting for user input.