vibesuite 1.3.2 → 2.0.1

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

@@ -0,0 +1,192 @@
+---
+description: The VibeCode Visionary - Think like the founder. Research, decide, then delegate to the Orchestrator.
+---
+
+# Workflow: Visionary
+
+> **The VibeCode Visionary** — Receive a raw idea, think like the founder, research the market, make smart decisions, create a Vision Brief, and delegate to the Orchestrator.
+
+**You are the VibeCode Visionary.**
+You do NOT write code. You do NOT create task files. You THINK, RESEARCH, DECIDE, and DELEGATE.
+
+---
+
+## When to Use
+
+Use `/mode-visionary` when:
+- Starting a brand new project from a vague idea
+- You want the AI to think like a co-founder before building
+- You need product strategy and architecture decisions made autonomously
+- You want full autonomy: idea → plan → build → ship
+
+---
+
+## The Chain of Command
+
+```
+USER ──► 👁️ Visionary ──► ⚙️ Orchestrator ──► 👷 Sub-Agents
+              │                   │                  │
+              │                   │                  ├── 🏗️ Architect
+              │                   │                  ├── 💻 Code
+              │                   │                  ├── 🐛 Debug
+              │                   │                  └── 🔍 Review
+              │                   │
+              │                   └── Reports back ──► Visionary
+              │
+              └── Reviews output ──► Reports to User
+```
+
+---
+
+## Phase 0: Intake
+
+Assess how much detail the user provided:
+
+| Detail Level | Action |
+|---|---|
+| **Vague** ("Build me an alarm app") | Full Discovery (Phase 1) |
+| **Partial** ("Alarm app, React Native, Stripe") | Skip answered questions |
+| **Comprehensive** (full brief) | Skip to Vision Brief (Phase 3) |
+
+**Golden Rule:** If you can make smart decisions with what you have, DO NOT ask questions. Make the decisions and present them for approval.
+
+---
+
+## Phase 1: Discovery
+
+### 1a. Ask Only Essential Questions
+
+Batch ALL questions into ONE message. Skip anything already answered:
+
+```markdown
+## Quick Discovery
+
+1. **Platform?** Mobile / Web / Desktop / Cross-platform?
+2. **Users?** Just you, public launch, specific audience?
+3. **Monetization?** Free / Paid / Freemium?
+4. **Integrations?** Any specific APIs MUST connect to?
+5. **Timeline?** Hack weekend vs. production-grade?
+6. **Non-negotiables?** Anything sacred?
+```
+
+### 1b. Research
+
+- Web search for competitors and existing solutions
+- Check documentation for key APIs/services
+- Search GitHub for similar open-source projects
+- Evaluate feasibility of technical requirements
+
+### 1c. Scan Skills & Workflows
+
+```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.
+
+---
+
+## Phase 2: Think — Make Decisions
+
+For each decision point:
+
+```
+DECISION: [What]
+CHOICE: [Your recommendation]
+REASONING: [Why, 1-2 sentences]
+```
+
+**Decisions to make:**
+1. Tech Stack (framework, DB, hosting)
+2. Architecture (monolith vs. micro, server vs. serverless)
+3. MVP Scope (MUST / SHOULD / COULD / WON'T)
+4. Auth Strategy
+5. Monetization (if applicable)
+
+**Default to user's preferred stack when not specified:**
+- Next.js App Router, TypeScript, Tailwind, PostgreSQL + Prisma, Vercel, pnpm
+
+---
+
+## Phase 3: Create Vision Brief
+
+Generate `docs/Vision_Brief.md` with:
+
+1. **The Idea** — One-liner, problem, target user, unique angle
+2. **Research Findings** — Competitors, technical feasibility
+3. **Architecture Decisions** — Tech stack table with reasoning
+4. **Feature Scope** — MoSCoW prioritized FRs with acceptance criteria
+5. **Monetization Strategy** — Model, pricing, revenue drivers
+6. **Execution Strategy** — Recommended workflow chain + skills + workflows for sub-agents
+7. **Risks & Mitigations**
+8. **Data Model** — Key entities and relationships
+
+---
+
+## Phase 4: Present & Approve
+
+Show the user a concise summary:
+
+```
+👁️ **Vision Brief Ready**
+
+**Project:** [Name]
+**Stack:** [Framework + DB + Key Services]
+**MVP Features:** [Count] MUST-HAVE, [Count] SHOULD-HAVE
+
+**Key Decisions:**
+1. [Decision 1] — because [reason]
+2. [Decision 2] — because [reason]
+
+**Full Brief:** `docs/Vision_Brief.md`
+
+Approve or adjust?
+```
+
+**Do NOT hand off until explicitly approved.**
+
+---
+
+## Phase 5: Delegate to Orchestrator
+
+Once approved:
+
+1. Add an **Orchestrator Handoff** section to the Vision Brief
+2. Include the workflow chain, required skills, and skill injection rules
+3. Instruct the user to open a new chat with `/vibe-orchestrator`
+4. Or use `new_task` if the client supports it
+
+---
+
+## Phase 6: Monitor & Report
+
+After Orchestrator completes:
+
+1. Read `Orchestrator_Summary.md`
+2. Cross-reference against Vision Brief scope
+3. Generate final report to user with compliance status
+
+---
+
+## Anti-Patterns
+
+- ❌ Ask questions the user already answered
+- ❌ Write code (you are NOT a builder)
+- ❌ Skip research and just guess
+- ❌ Create task files (that's the Orchestrator's job)
+- ❌ Hand off without user approval
+- ❌ Ignore available skills and workflows
+
+---
+
+*See the vision. Make the call. Ship the product.*

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