vibesuite 1.3.3 → 2.0.2

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

@@ -52,26 +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 ~/.gemini/antigravity/skills/ 2>/dev/null   # Gemini / Antigravity
-ls ~/.kilocode/skills/ 2>/dev/null              # KiloCode
+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.
 
 ---
@@ -122,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 directory varies by client.** Check: `.agent/skills/`, `~/.gemini/antigravity/skills/`, `~/.kilocode/skills/`, or your system prompt.
-
-### 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,21 +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 ~/.gemini/antigravity/skills/ 2>/dev/null   # Gemini / Antigravity
-ls ~/.kilocode/skills/ 2>/dev/null              # KiloCode
-
-# 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/.agent/workflows/optimize-agent-context.md

@@ -0,0 +1,54 @@
+---
+description: Create, audit, or optimize agent.md / claude.md / cursorrules files using the Band-Aid Philosophy. Strips bloat, enforces minimalism.
+---
+
+# Workflow: Optimize Agent Context
+
+> Shortcut to the `optimize-agent-context` skill. Creates minimal, effective AI agent instruction files.
+
+---
+
+## Steps
+
+### 1. Load the Skill
+
+```bash
+cat .agent/skills/optimize-agent-context/SKILL.md
+```
+
+Read the full skill instructions before proceeding.
+
+---
+
+### 2. Determine Mode
+
+Ask the user which mode they need:
+
+| Mode | Trigger |
+|---|---|
+| **A: Create** | No existing file, or starting fresh |
+| **B: Audit** | Has an existing agent.md / claude.md to optimize |
+| **C: Band-Aid** | Quick fix for a specific agent mistake |
+
+---
+
+### 3. Execute
+
+Follow the corresponding Mode (A, B, or C) from the skill instructions exactly.
+
+---
+
+### 4. Deliver
+
+- Save the generated/optimized file to the user's preferred location
+- Show before/after line count (Mode B)
+- Confirm with user before overwriting any existing file
+
+---
+
+## When to Use
+
+- **New project** — Create a minimal agent.md from scratch
+- **Existing bloated file** — Audit and strip an overgrown context file
+- **Agent keeps messing up** — Add a targeted Band-Aid rule
+- **Cost optimization** — Reduce token overhead from verbose context files

package/assets/.agent/workflows/remotion-build.md

@@ -17,7 +17,7 @@ Before writing ANY Remotion code, you MUST read the relevant rule files. Do NOT
 ### Step 0.1: Read the Main Skill
 // turbo
 ```bash
-cat "C:/Users/johno/.gemini/antigravity/skills/remotion/SKILL.md"
+cat ".agent/skills/remotion/SKILL.md"
 ```
 
 ### Step 0.2: Read REQUIRED Rule Files
@@ -27,62 +27,62 @@ Based on what the video needs, you MUST read the corresponding rule files. This
 **For ANY animation work (ALWAYS READ THESE):**
 // turbo
 ```bash
-cat "C:/Users/johno/.gemini/antigravity/skills/remotion/rules/animations.md"
-cat "C:/Users/johno/.gemini/antigravity/skills/remotion/rules/timing.md"
-cat "C:/Users/johno/.gemini/antigravity/skills/remotion/rules/sequencing.md"
+cat ".agent/skills/remotion/rules/animations.md"
+cat ".agent/skills/remotion/rules/timing.md"
+cat ".agent/skills/remotion/rules/sequencing.md"
 ```
 
 **If using scene transitions:**
 // turbo
 ```bash
-cat "C:/Users/johno/.gemini/antigravity/skills/remotion/rules/transitions.md"
+cat ".agent/skills/remotion/rules/transitions.md"
 ```
 
 **If using text animations (typewriter, highlights, etc):**
 // turbo
 ```bash
-cat "C:/Users/johno/.gemini/antigravity/skills/remotion/rules/text-animations.md"
-cat "C:/Users/johno/.gemini/antigravity/skills/remotion/rules/fonts.md"
+cat ".agent/skills/remotion/rules/text-animations.md"
+cat ".agent/skills/remotion/rules/fonts.md"
 ```
 
 **If using images, videos, or audio:**
 // turbo
 ```bash
-cat "C:/Users/johno/.gemini/antigravity/skills/remotion/rules/assets.md"
-cat "C:/Users/johno/.gemini/antigravity/skills/remotion/rules/images.md"
-cat "C:/Users/johno/.gemini/antigravity/skills/remotion/rules/videos.md"
-cat "C:/Users/johno/.gemini/antigravity/skills/remotion/rules/audio.md"
+cat ".agent/skills/remotion/rules/assets.md"
+cat ".agent/skills/remotion/rules/images.md"
+cat ".agent/skills/remotion/rules/videos.md"
+cat ".agent/skills/remotion/rules/audio.md"
 ```
 
 **If using 3D elements:**
 // turbo
 ```bash
-cat "C:/Users/johno/.gemini/antigravity/skills/remotion/rules/3d.md"
+cat ".agent/skills/remotion/rules/3d.md"
 ```
 
 **If using captions/subtitles:**
 // turbo
 ```bash
-cat "C:/Users/johno/.gemini/antigravity/skills/remotion/rules/display-captions.md"
-cat "C:/Users/johno/.gemini/antigravity/skills/remotion/rules/transcribe-captions.md"
+cat ".agent/skills/remotion/rules/display-captions.md"
+cat ".agent/skills/remotion/rules/transcribe-captions.md"
 ```
 
 **If using charts/data visualization:**
 // turbo
 ```bash
-cat "C:/Users/johno/.gemini/antigravity/skills/remotion/rules/charts.md"
+cat ".agent/skills/remotion/rules/charts.md"
 ```
 
 **If using Lottie animations:**
 // turbo
 ```bash
-cat "C:/Users/johno/.gemini/antigravity/skills/remotion/rules/lottie.md"
+cat ".agent/skills/remotion/rules/lottie.md"
 ```
 
 **If using GIFs:**
 // turbo
 ```bash
-cat "C:/Users/johno/.gemini/antigravity/skills/remotion/rules/gifs.md"
+cat ".agent/skills/remotion/rules/gifs.md"
 ```
 
 > ⛔ **DO NOT PROCEED TO PHASE 1 UNTIL YOU HAVE READ THE RELEVANT RULES.**

package/assets/.agent/workflows/stitch.md

@@ -5,7 +5,7 @@ description: Google Stitch design-to-code workflow. Routes to the correct sub-sk
 # /stitch — Google Stitch Design Platform
 
 ## Overview
-This workflow orchestrates the full Stitch design-to-code pipeline. All skills live in `~/.gemini/antigravity/skills/stitch/`.
+This workflow orchestrates the full Stitch design-to-code pipeline. All skills live in `.agent/skills/stitch/`.
 
 **The Stitch bundle is NOT a pick-one-and-go system.** It's a **pipeline** of 6 skills that chain together. Your job is to guide the user through the journey, always suggesting the next logical step.
 
@@ -13,7 +13,7 @@ This workflow orchestrates the full Stitch design-to-code pipeline. All skills l
 // turbo
 Read the master SKILL.md — it contains the **Pipeline Orchestration Protocol** which you MUST follow:
 ```
-view_file ~/.gemini/antigravity/skills/stitch/SKILL.md
+view_file .agent/skills/stitch/SKILL.md
 ```
 
 ## Step 2: Identify the Entry Point
@@ -35,7 +35,7 @@ Use the decision tree from the master SKILL.md to determine WHERE the user enter
 // turbo
 Read the specific sub-skill's `SKILL.md`:
 ```
-view_file ~/.gemini/antigravity/skills/stitch/{sub-skill}/SKILL.md
+view_file .agent/skills/stitch/{sub-skill}/SKILL.md
 ```
 
 ## Step 4: Check for Supporting Resources
@@ -46,7 +46,7 @@ Each sub-skill may have `resources/`, `examples/`, and `scripts/` folders:
 - **scripts/**: Validation and networking helpers
 
 ```
-ls ~/.gemini/antigravity/skills/stitch/{sub-skill}/
+ls .agent/skills/stitch/{sub-skill}/
 ```
 
 ## Step 5: Execute the Sub-Skill

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": "1.3.3",
+  "version": "2.0.2",
   "description": "A Complete System for AI-Human Software Development Collaboration",
   "type": "module",
   "bin": {