vibesuite 2.0.1 → 2.0.2

package/README.md

@@ -9,17 +9,33 @@
 
 ## 🚀 Quick Start (Recommended)
 
-Spawn the complete VibeCode system directly into your project with a single command:
+### Option A: Global Install (Best for Multi-IDE Users) ⭐
+
+Install skills **once** and have them available across all your AI harnesses (Antigravity, KiloCode, Windsurf, Cursor, Gemini CLI):
 
 ```bash
-# Using npx (No installation required)
-npx vibesuite init
+# Using pnpm
+pnpm dlx vibesuite install
+
+# Using npx
+npx vibesuite install
+```
+
+This will:
+- 🔍 **Auto-detect** which AI harnesses are installed on your machine
+- 📦 **Create a global store** at `~/.vibesuite/`
+- 📡 **Sync skills & workflows** to every detected harness's global directory
+- 🔄 **Sync KiloCode YAMLs** to both CLI and VS Code extension paths
+
+### Option B: Per-Project Setup
 
-# Or using pnpm
+Spawn VibeCode into a single project's `.agent/` folder:
+
+```bash
 pnpm dlx vibesuite init
 ```
 
-This interactive CLI will let you choose exactly what you need:
+This interactive CLI lets you choose:
 - ✅ **.agent Folder** (For Cursor/Windsurf workflows)
 - ✅ **Kilo Code Agents** (YAML definitions)
 - ✅ **Legacy Protocols** (Manual prompts)
@@ -66,6 +82,52 @@ npx -y skills add https://github.com/JStaRFilms/VibeCode-Protocol-Suite --skill
 
 ---
 
+## 🌐 Global Skills Router (v2.0)
+
+VibeSuite v2.0 introduces the **Global Skills Router** — install skills once, route to every AI harness automatically. No symlinks, no admin privileges, works on Mac & Windows.
+
+### Supported Harnesses
+
+| Harness | Global Skills Path | Global Workflows Path |
+|---|---|---|
+| **Antigravity** | `~/.gemini/antigravity/skills/` | `~/.gemini/antigravity/global_workflows/` |
+| **KiloCode** | `~/.kilocode/skills/` | `~/.kilocode/workflows/` |
+| **Windsurf** | `~/.codeium/windsurf/skills/` | `~/.codeium/windsurf/global_workflows/` |
+| **Cursor** | `~/.cursor/skills/` | _(uses rules)_ |
+| **Gemini CLI** | `~/.gemini/skills/` | — |
+
+### CLI Commands
+
+| Command | What It Does |
+|---|---|
+| `vibesuite install` | One-time global setup — detect harnesses, create store, sync everything |
+| `vibesuite sync` | Re-sync from `~/.vibesuite/` to all linked harnesses |
+| `vibesuite add <url>` | Fetch skills from any GitHub repo into your global store |
+| `vibesuite harnesses` | Show detected harnesses and global store status |
+| `vibesuite init` | Per-project `.agent/` setup (backward compatible) |
+| `vibesuite update` | Update resources from GitHub (supports global store) |
+
+### Example: Add Remote Skills
+
+```bash
+# Pull skills from any GitHub repo into your global store
+pnpm dlx vibesuite add https://github.com/JStaRFilms/VibeCode-Protocol-Suite
+
+# Check what's detected
+pnpm dlx vibesuite harnesses
+
+# Re-sync after adding new skills
+pnpm dlx vibesuite sync
+```
+
+### KiloCode YAML Auto-Sync
+
+When KiloCode is detected, `vibesuite install` automatically syncs `custom_modes.yaml` to **both** locations:
+- CLI: `~/.kilocode/cli/global/settings/custom_modes.yaml`
+- Extension: `%APPDATA%/Antigravity/User/globalStorage/kilocode.kilo-code/settings/custom_modes.yaml`
+
+---
+
 ## 🌟 What is VibeCode?
 
 VibeCode isn't just a collection of prompts—it's a **complete workflow system** for collaborating with AI to build software. Think of yourself as the Visionary/CEO, and your AI assistants as a specialized, high-performance development team.

package/assets/.agent/workflows/agent_reset.md

@@ -21,14 +21,12 @@ You are exhibiting context degradation. Before doing ANYTHING:
 
 ### 0. Re-Discover Available Skills & Workflows
 
-You may have forgotten what tools are available. **Run this now:**
+You may have forgotten what tools are available.
 
-```bash
-# Global (always available)
-ls .agent/skills/
-ls .agent/workflows/
+**Your system prompt lists all available skills and workflows with their full absolute paths.** Check there FIRST.
 
-# Local (project-specific, if exists)
+Fallback (if not in system prompt):
+```bash
 ls .agent/skills/ 2>/dev/null
 ls .agent/workflows/ 2>/dev/null
 ```

package/assets/.agent/workflows/mode-orchestrator.md

@@ -52,25 +52,18 @@ Use `/mode-orchestrator` when:
 
 ## Phase 1: Ecosystem Scan (MANDATORY)
 
-### Scan Skills
+### Scan Skills & Workflows
 
+**Your system prompt lists all available skills and workflows with their full absolute paths.** Check there FIRST — do NOT guess paths.
+
+If your system prompt doesn't list them, fall back to scanning the filesystem:
 ```bash
-# MANDATORY: Do not skip this
-# Project-local skills
 ls .agent/skills/ 2>/dev/null
-
-# Global skills (path varies by AI client)
-ls .agent/skills/ 2>/dev/null   # Gemini / Antigravity
+ls .agent/workflows/ 2>/dev/null
+ls .agent/global_workflows/ 2>/dev/null
 ```
 
 Create a **Skills Registry** — which skills are relevant and which tasks they apply to.
-
-### Scan Workflows
-
-```bash
-ls .agent/workflows/
-```
-
 Create a **Workflows Registry** — which workflows map to which task phases.
 
 ---
@@ -121,20 +114,23 @@ Each task file (`01_task_name.task.md`) includes:
 ## 🔧 Agent Setup (DO THIS FIRST)
 
 ### Workflow to Follow
-> Load: `cat .agent/workflows/vibe-build.md`
+> Read the `/vibe-build` workflow. Your system prompt lists all workflows with
+> their full paths — use `view_file` on the path listed there.
+> Fallback: `cat .agent/workflows/vibe-build.md`
+> Fallback: `cat .agent/global_workflows/vibe-build.md`
 
 ### Prime Agent Context
 > MANDATORY: Run `/vibe-primeAgent` first
 
 ### Required Skills
-> | Skill | Path | Why |
-> |-------|------|-----|
-> | nextjs-standards | `[skills-dir]/nextjs-standards/SKILL.md` | Next.js project |
+> **Your system prompt lists all skills with their absolute paths.**
+> Look up each skill below in your system prompt and `view_file` its SKILL.md.
 >
-> **Skills are listed in your system prompt with full paths.** Project-local skills live in `.agent/skills/`.
-
-### Check Additional Skills
-> Scan all known skills directories for more relevant skills
+> | Skill | Why |
+> |-------|-----|
+> | nextjs-standards | Next.js project |
+>
+> Fallback (if not in system prompt): `ls .agent/skills/`
 ```
 
 Then: Objective, Scope, Context, Definition of Done, Expected Artifacts, Constraints.

package/assets/.agent/workflows/mode-visionary.md

@@ -78,20 +78,14 @@ Batch ALL questions into ONE message. Skip anything already answered:
 
 ### 1c. Scan Skills & Workflows
 
+**Your system prompt lists all available skills and workflows with their full absolute paths.** Check there FIRST.
+
+Fallback (if not in system prompt):
 ```bash
-# MANDATORY: Scan before making decisions
-# Project-local skills
 ls .agent/skills/ 2>/dev/null
-
-# Global skills (path varies by AI client)
-ls .agent/skills/ 2>/dev/null   # Gemini / Antigravity
-
-# Workflows (always project-local)
 ls .agent/workflows/ 2>/dev/null
 ```
 
-Use whichever location exists. The agent's system prompt may also list available skills.
-
 Note which skills and workflows are relevant — these will be injected into the Orchestrator handoff.
 
 ---

package/assets/VibeCode-Agents/vibe-orchestrator.yaml

@@ -111,25 +111,14 @@ customModes:
 
       **MANDATORY STEP — DO NOT SKIP.**
 
-      Before creating ANY task, scan the skills directory to understand what tools
-      are available for sub-agents:
+      **Your system prompt lists all available skills with their full absolute paths.** Check there FIRST — do NOT guess paths.
 
+      If your system prompt doesn't list them, fall back to scanning the filesystem:
       ```powershell
-      # Scan for skills — check all known locations
-      # Project-local skills
       ls .agent/skills/ 2>$null
-
-      # Global skills (path varies by AI client)
-      ls ~/.gemini/antigravity/skills/ 2>$null   # Gemini / Antigravity
-      ls ~/.kilocode/skills/ 2>$null              # KiloCode
-      # Add other client paths as discovered
-
-      # For each skill found, read the SKILL.md to understand its purpose
-      # Focus on the name, description, and triggers
       ```
 
-      **Use whichever skills directory exists.** If multiple exist, merge the lists.
-      The agent's system prompt may also list available skills — use that too.
+      For each relevant skill found, read its SKILL.md to understand its purpose.
 
       Create a skills registry for this session:
 
@@ -313,33 +302,25 @@ customModes:
       ### Workflow to Follow
       > **Primary Workflow:** `/vibe-build` (or whichever is assigned)
       >
-      > Load this workflow FIRST: `cat .agent/workflows/vibe-build.md`
-      > Follow its steps as your execution framework.
+      > Read the workflow from your system prompt — it lists all workflows with
+      > their full paths. Use `view_file` on the path listed there.
+      > Fallback: `cat .agent/workflows/vibe-build.md`
+      > Fallback: `cat .agent/global_workflows/vibe-build.md`
 
       ### Load Prime Agent Context
       > **MANDATORY:** Run `/vibe-primeAgent` before starting ANY work.
       > This loads coding guidelines, project state, and current work.
 
       ### Required Skills
-      > **Load these skills before starting work:**
+      > **Your system prompt lists all skills with their absolute paths.**
+      > Look up each skill below in your system prompt and `view_file` its SKILL.md.
       >
-      > | Skill | Relative Path | Why |
-      > |-------|---------------|-----|
-      > | `nextjs-standards` | `[skills-dir]/nextjs-standards/SKILL.md` | Project uses Next.js App Router |
-      > | `ai-sdk` | `[skills-dir]/ai-sdk/SKILL.md` | This task involves AI features |
+      > | Skill | Why |
+      > |-------|-----|
+      > | `nextjs-standards` | Project uses Next.js App Router |
+      > | `ai-sdk` | This task involves AI features |
       >
-      > **Skills directory varies by client.** Check these locations:
-      > - `.agent/skills/` (project-local)
-      > - `~/.gemini/antigravity/skills/` (Antigravity)
-      > - `~/.kilocode/skills/` (KiloCode)
-      > - Or check your system prompt for available skills
-      >
-      > **How to load:** `cat [path-to-skill]/SKILL.md` and follow the skill's instructions.
-
-      ### Check Available Skills
-      > Before starting, scan all known skills directories for any additional
-      > skills that may help with this specific task. If you find a relevant skill
-      > not listed above, load it.
+      > Fallback (if not in system prompt): `ls .agent/skills/`
 
       ---
 

package/assets/VibeCode-Agents/vibe-visionary.yaml

@@ -148,25 +148,15 @@ customModes:
 
       **CRITICAL: Before making any decisions, scan available skills and workflows.**
 
-      Skills can live in different locations depending on the AI coding client.
-      Check ALL known locations and use whichever exists:
+      **Your system prompt lists all available skills and workflows with their full absolute paths.** Check there FIRST — do NOT guess paths.
 
+      Fallback (if not in system prompt):
       ```powershell
-      # Scan for skills — check all known locations
-      # Project-local skills
       ls .agent/skills/ 2>$null
-
-      # Global skills (path varies by AI client)
-      ls ~/.gemini/antigravity/skills/ 2>$null   # Gemini / Antigravity
-      ls ~/.kilocode/skills/ 2>$null              # KiloCode
-      # Add other client paths as discovered
-
-      # Scan available workflows (always project-local)
       ls .agent/workflows/ 2>$null
+      ls .agent/global_workflows/ 2>$null
       ```
 
-      **Use whichever skills directory exists.** If multiple exist, merge the lists.
-      The agent's system prompt may also list available skills — use that too.
       These will be passed to the Orchestrator for injection into sub-agent tasks.
 
       ---

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "vibesuite",
-  "version": "2.0.1",
+  "version": "2.0.2",
   "description": "A Complete System for AI-Human Software Development Collaboration",
   "type": "module",
   "bin": {
@@ -38,4 +38,4 @@
     "url": "https://github.com/JStaRFilms/VibeCode-Protocol-Suite/issues"
   },
   "homepage": "https://github.com/JStaRFilms/VibeCode-Protocol-Suite#readme"
-}
+}