vibe-instruction

Orient agents and developers to Vibe Center repository workflows and commands.

6|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/jacobcy/vibe-coding-control-center --skill vibe-instruction
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vibe-instruction
Source: https://github.com/jacobcy/vibe-coding-control-center/tree/main/skills/vibe-instruction
Command: npx skills add https://github.com/jacobcy/vibe-coding-control-center --skill vibe-instruction

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

New contributors and agents need a single, concise orientation that explains the dual implementation (V2 shell and V3 Python), which commands to use in which contexts, and the standard development and handoff workflows to avoid misusing tools or duplicating state management.

Core Features & Use Cases

  • Project structure overview: Explains the role of bin, lib, src/vibe3, skills, and .agent so users know where to look for capabilities and governance.
  • Command and workflow guidance: Clarifies when to use V2 shell aliases versus V3 orchestration commands, how to register and bind flows, and how to run, plan, and handoff tasks.
  • Troubleshooting and governance: Summarizes status and check commands, recovery actions for auto-tasks, and where truth and handoff artifacts are stored for reproducible collaboration.
  • Use case: Onboarding a new developer or configuring an agent to run a task while preserving branch and flow semantics.

Quick Start

Ask the vibe-instruction skill for a concise project overview, the recommended commands to run for onboarding, and the standard flow-based development workflow.

Frequently Asked Questions about vibe-instruction

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

FAQPage Schema
How do I onboard a new developer to Vibe Center workflows?

Onboarding a new developer to Vibe Center workflows requires a concise project overview explaining the bin, lib, src/vibe3, skills, and .agent directories, plus the standard flow-based development steps for branch and task execution.

When should I use V2 shell aliases versus V3 Python orchestration commands?

Choosing between V2 shell aliases and V3 Python orchestration commands depends on context: the orientation clarifies command semantics for both implementations to prevent tool misuse and avoid duplicating state management during agent task execution.

What is the standard flow-based development workflow for agent handoff?

The standard flow-based development workflow for agent handoff involves registering and binding flows, running and planning tasks, and storing truth and handoff artifacts to ensure reproducible collaboration and correct branch semantics.

How do I troubleshoot auto-tasks and recover state in Vibe3?

Troubleshooting auto-tasks and recovering state in Vibe3 involves using summarized status and check commands to verify flow lifecycle steps and executing recommended recovery actions to preserve branch and flow semantics.

Does agent orchestration require understanding both V2 and V3 implementations?

Yes, agent orchestration requires understanding both V2 and V3 implementations because the dual structure clarifies where to find capabilities and governance, ensuring correct command usage and preventing state duplication across tasks.