vc-setup

Scaffolds and populates an agent development harness through interactive project detection and codebase analysis.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/HyuseCS/project-c --skill vc-setup-hyusecs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vc-setup
Source: https://github.com/HyuseCS/project-c/tree/main/.claude/skills/vc-setup
Command: npx skills add https://github.com/HyuseCS/project-c --skill vc-setup-hyusecs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Setting up an AI agent development harness requires detecting the project stack, creating process directories, and writing real project context — a tedious manual process that often produces stale placeholder docs. This Skill automates detection, scaffolding, deep codebase study, and validation while always asking before reorganizing existing files. ## Core Features & Use Cases - Interactive Detection and Classification: Detects package manager, framework, test runner, and monorepo structure across JS, Python, Go, Ruby, and Rust projects, then classifies the repo as new or existing to pick the right setup flow. - Scaffold with Safe Migration: Creates the process/ directory tree from seed templates and migrates legacy layouts (old plans/, reports/, skills/ dirs) using safe-inference rules, never overwriting user content without approval. - Deep STUDY Phase: Spawns parallel subagents to scan architecture, tests, context groups, and feature areas, then populates all-context.md and all-tests.md with real researched content instead of placeholders. - Use Case: You just cloned a Kotlin Multiplatform repo and want an agent harness. Run the setup, answer a few discovery questions, and receive a fully populated process/ directory with validated context files and feature folders. ## Quick Start Ask the agent to run vc-setup to detect this project's stack and scaffold the agent harness with populated context files.

Frequently Asked Questions about vc-setup

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

FAQPage Schema
How do I set up an agent harness on an existing project?

Run vc-setup on the repo; it detects existing process/ directories and context files, presents findings in a LOOKS GOOD / COULD BE IMPROVED / MISSING report, and waits for your approval before changing anything. It then scaffolds only approved changes and gap-fills context.

What project types does vc-setup support?

It detects package.json for Node/Bun/Deno, pyproject.toml or requirements.txt for Python, go.mod for Go, Gemfile for Ruby, and Cargo.toml for Rust. If no manifest is found, it asks you what runtime the project uses and adapts.

Will vc-setup overwrite my existing CLAUDE.md or context files?

No. CLAUDE.md and AGENTS.md are managed protocol files that are never adapted, and existing user content is preserved. In Merge mode it never overwrites files, and in Flow B it presents findings and waits for approval before modifying anything.

How does vc-setup handle old process directory layouts?

Merge mode migrates legacy layouts like process/plans/ or top-level reports/ into the standard general-plans structure using safe-inference rules. Ambiguous artifacts are left in place and surfaced for manual review rather than moved blindly.

Why does validation report missing context group directories?

The context discovery validator may warn about missing groups like uxui/ on fresh projects. This is expected when the project has no content for that domain; groups should only be created when substantial real content exists.