AI SummaryVCG is a shorthand alias for the vc-router that prioritizes fast iteration and shipping working baselines over perfection. Best suited for developers who want quick, opinionated coding decisions without lengthy deliberation.
Install
Copy this and paste it into Claude Code, Cursor, or any AI assistant:
I want to install the "vcg" skill in my project. Please run this command in my terminal: # Install skill into your project (2 files) mkdir -p .claude/skills/vcg && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/vcg/SKILL.md "https://raw.githubusercontent.com/majiayu000/claude-skill-registry/main/skills/data/vcg/SKILL.md" && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/vcg/metadata.json "https://raw.githubusercontent.com/majiayu000/claude-skill-registry/main/skills/data/vcg/metadata.json" Then restart Claude Code (or reload the window in Cursor) so the skill is picked up.
Description
Short, explicit alias for vc-router. Use only when the user explicitly invokes `use vcg:` and wants the shortest reliable router command.
VC Defaults
• Prefer fast iteration and shipping a working baseline over perfection. • Make safe default choices without pausing; record assumptions briefly. • Ask questions only after delivering an initial result, unless the workflow requires confirmation for safety/legal reasons. • Keep outputs concise, actionable, and easy to extend. • Assume the user is non-technical; avoid long explanations and provide copy/paste steps when actions are required. • Treat non-explicit triggers (e.g., "vc go") as normal text; ask the user to rephrase using use vcg:.
VC Fast Path
• Classify the task in one pass. • Select a single best-fit skill; avoid chaining unless required. • Execute immediately; collect assumptions and questions for the end. • If the task is multi-step or open-ended, default to a finish-style workflow.
Sub-Agent Assist (Optional)
If the request is large/ambiguous and collaboration tools are available, spawn 1–2 sub-agents to parallelize: • Repo scan (within scope roots): locate relevant files/config and constraints • Risk/validation scan: test strategy, edge cases, safety concerns Rules: • Timebox and keep outputs short. • Sub-agents report findings only; main agent decides routing and applies changes.
Scope Lock (Required)
• Before any file search, determine scope roots: • If a .vc-scope file exists in the current directory or any parent, use the closest one. • Each non-empty, non-comment line is an allowed path. • Relative paths are resolved from the .vc-scope file directory. • Else, if inside a git repo, use the repo root. • Else, use the current working directory. • Only run rg, find, or any filesystem scans inside the scope roots. • Never scan $HOME or / unless the user explicitly asks.
Discussion
Health Signals
My Fox Den
Community Rating
Sign in to rate this booster