antigravity-ide 4.2.1 → 4.3.3

package/web/src/app/docs/guide/examples/brainstorm/page.mdx

@@ -1,91 +0,0 @@
-export const metadata = {
-  title: "Example: Structured Brainstorming | Antigravity Kit",
-  description: "Learn how to use the /brainstorm workflow to explore multiple options before committing to an implementation.",
-};
-
-import { Callout, StepList, Step, Terminal, TerminalLine, TerminalBlock, ProTips, Tip, FeatureGrid, Feature } from '@/components/mdx'
-
-# Structured Brainstorming
-
-Explore multiple approaches before writing code with the `/brainstorm` workflow.
-
-## Overview
-
-The `/brainstorm` command activates a **structured ideation mode**.
-Instead of jumping straight to code, the agent explores at least 3 different approaches,
-analyzes pros and cons, and helps you make an informed decision.
-
-<FeatureGrid>
-  <Feature title="No Code" description="Ideas only" />
-  <Feature title="3+ Options" description="Always compare" />
-  <Feature title="Pros/Cons" description="Honest tradeoffs" />
-  <Feature title="You Decide" description="Final choice" />
-</FeatureGrid>
-
-## The Process
-
-<StepList>
-  <Step number={1} title="Describe Your Challenge">
-    Tell the agent what you want to explore. Be specific about constraints.
-
-    ```bash
-    /brainstorm authentication system for my SaaS app
-    ```
-  </Step>
-  <Step number={2} title="Review Options">
-    The agent presents 3+ approaches with pros, cons, and effort levels.
-  </Step>
-  <Step number={3} title="Make Decision">
-    Choose an option, then use `/enhance` or `/create` to implement.
-  </Step>
-</StepList>
-
-## Example Session
-
-<Terminal>
-  <TerminalLine type="user">/brainstorm state management for complex form</TerminalLine>
-
-  <TerminalBlock>
-    <TerminalLine type="agent">**Exploring Options...**</TerminalLine>
-  </TerminalBlock>
-
-  <div className="space-y-4 pl-8 mb-4">
-    <div className="border-t border-zinc-800 pt-3">
-      <strong className="text-purple-400">Option A: React Hook Form + Zod</strong>
-      <div className="text-xs mt-1 space-y-1">
-        <div className="text-green-400">✅ Minimal re-renders, great DX</div>
-        <div className="text-red-400">❌ Learning curve</div>
-        <div className="text-yellow-400">📊 Effort: Low</div>
-      </div>
-    </div>
-    <div className="border-t border-zinc-800 pt-3">
-      <strong className="text-purple-400">Option B: Zustand</strong>
-      <div className="text-xs mt-1 space-y-1">
-        <div className="text-green-400">✅ Full control, persists across routes</div>
-        <div className="text-red-400">❌ More boilerplate</div>
-        <div className="text-yellow-400">📊 Effort: Medium</div>
-      </div>
-    </div>
-  </div>
-
-  <TerminalBlock highlight>
-    <TerminalLine type="agent">**💡 Recommendation: Option A**</TerminalLine>
-    For 20+ fields, RHF minimizes re-renders.
-  </TerminalBlock>
-</Terminal>
-
-## Pro Tips
-
-<ProTips>
-  <Tip title="Provide Context">
-    Mention constraints: "I need SSR support", "Must work offline".
-  </Tip>
-  <Tip title="Ask Follow-ups">
-    "Tell me more about Option B's scalability" before deciding.
-  </Tip>
-</ProTips>
-
-## Next Steps
-
-- Try `/brainstorm` for your next architecture decision
-- After deciding, use [Add New Feature](/docs/guide/examples/new-feature) to implement

package/web/src/app/docs/guide/examples/create/page.mdx

@@ -1,84 +0,0 @@
-export const metadata = {
-  title: "Example: Create New Application | Antigravity Kit",
-  description: "Learn how to use the /create workflow to build new applications from scratch with AI-powered wizards.",
-};
-
-import { Callout, StepList, Step, Terminal, TerminalLine, TerminalBlock, ProTips, Tip } from '@/components/mdx'
-
-# Create New Application
-
-Build complete applications from scratch with the `/create` wizard.
-
-## Overview
-
-The `/create` command is your **application creation wizard**.
-It guides you through an interactive dialogue, understands your requirements,
-plans the architecture, and orchestrates specialist agents to build your app.
-
-<Callout type="info">
-  **From idea to running app:** Just describe what you want, and the wizard handles tech stack, file structure, database schema, and implementation.
-</Callout>
-
-## The Process
-
-<StepList>
-  <Step number={1} title="Describe Your App">
-    Tell the wizard what you want to build. It will ask clarifying questions if needed.
-
-    ```bash
-    /create e-commerce site with product listing and cart
-    ```
-  </Step>
-  <Step number={2} title="Review Plan">
-    The `project-planner` agent creates a detailed plan. Approve to proceed.
-  </Step>
-  <Step number={3} title="Agents Build">
-    Specialist agents work in parallel: database-architect, backend, frontend.
-  </Step>
-</StepList>
-
-## Example Session
-
-<Terminal>
-  <TerminalLine type="user">/create todo app with dark mode</TerminalLine>
-
-  <TerminalBlock>
-    <TerminalLine type="agent">**Analyzing request...**</TerminalLine>
-    Tech Stack: Next.js + Tailwind + Zustand
-    <span className="text-yellow-300">Proceed? (Y/N)</span>
-  </TerminalBlock>
-
-  <TerminalLine type="user">Y</TerminalLine>
-
-  <div className="space-y-2 pl-8 mb-4">
-    <div className="flex items-center gap-2">
-      <span className="w-2 h-2 rounded-full bg-blue-500 animate-pulse"></span>
-      <span><strong>Backend:</strong> Creating store...</span>
-    </div>
-    <div className="flex items-center gap-2">
-      <span className="w-2 h-2 rounded-full bg-pink-500 animate-pulse"></span>
-      <span><strong>Frontend:</strong> Building components...</span>
-    </div>
-  </div>
-
-  <TerminalBlock highlight>
-    <TerminalLine type="agent">**🚀 App Created!**</TerminalLine>
-    Preview: <span className="text-blue-400">http://localhost:3000</span>
-  </TerminalBlock>
-</Terminal>
-
-## Pro Tips
-
-<ProTips>
-  <Tip title="Be Specific">
-    "E-commerce with Stripe" beats "online store".
-  </Tip>
-  <Tip title="Start Simple">
-    Create MVP first, use `/enhance` to iterate.
-  </Tip>
-</ProTips>
-
-## Next Steps
-
-- Run `/create` followed by your app idea
-- Use [Add New Feature](/docs/guide/examples/new-feature) to extend

package/web/src/app/docs/guide/examples/debugging/page.mdx

@@ -1,83 +0,0 @@
-export const metadata = {
-  title: "Example: Systematic Debugging | Antigravity Kit",
-  description: "Learn how to solve complex issues using the /debug workflow's 4-phase investigation protocol.",
-};
-
-import { Callout, StepList, Step, Terminal, TerminalLine, TerminalBlock, ProTips, Tip } from '@/components/mdx'
-
-# Systematic Debugging
-
-Solve complex issues using the rigorous `/debug` workflow.
-
-## Overview
-
-The `/debug` workflow enforces a **4-phase investigation protocol** (Discovery, Hypothesis, Verification, Resolution). It prevents guess-driven development by requiring evidence before code changes.
-
-<Callout type="info" title="When to use:">
-  - "The login button does nothing"
-  - "API returns 500 error intermittently"
-  - "App crashes on mobile only"
-</Callout>
-
-## The Process
-
-<StepList>
-  <Step number={1} title="Discovery">
-    Gathers facts: Error logs, user reports, reproduction steps.
-
-    ```bash
-    /debug Login returns 403 even with correct credentials
-    ```
-  </Step>
-  <Step number={2} title="Hypothesis">
-    Formulates potential causes prioritized by likelihood.
-  </Step>
-  <Step number={3} title="Verification">
-    Systematically tests each hypothesis using scripts or logs.
-  </Step>
-  <Step number={4} title="Resolution">
-    Implements the fix and adds a regression test.
-  </Step>
-</StepList>
-
-## Example Session
-
-<Terminal>
-  <TerminalLine type="user">/debug Form submission fails silently</TerminalLine>
-
-  <TerminalBlock>
-    <TerminalLine type="agent">**Phase 1: Discovery**</TerminalLine>
-    Reading `CheckoutForm.tsx`... Found `handleSubmit`.
-    <span className="text-red-400">ERROR: Cannot read properties of undefined</span>
-  </TerminalBlock>
-
-  <TerminalBlock>
-    <TerminalLine type="agent">**Phase 2: Hypothesis**</TerminalLine>
-    <div className="text-xs mt-1">
-      1. `emailRef.current` is null on mount<br/>
-      2. Event handler not bound correctly
-    </div>
-  </TerminalBlock>
-
-  <TerminalBlock highlight>
-    <TerminalLine type="agent">**Phase 4: Resolution**</TerminalLine>
-    Fix applied: Added null check to `emailRef`.
-    <span className="text-green-400">✅ Test passed: Form submits successfully.</span>
-  </TerminalBlock>
-</Terminal>
-
-## Pro Tips
-
-<ProTips>
-  <Tip title="Provide Context">
-    Paste the exact error message or stack trace for faster discovery.
-  </Tip>
-  <Tip title="Trust, Verify">
-    Ask the agent to run the reproduction case again to confirm it's solved.
-  </Tip>
-</ProTips>
-
-## Next Steps
-
-- Try `/debug` on an existing bug
-- See [Deployment](/docs/guide/examples/deployment) to ship your fix

package/web/src/app/docs/guide/examples/deployment/page.mdx

@@ -1,93 +0,0 @@
-export const metadata = {
-  title: "Example: Production Deployment | Antigravity Kit",
-  description: "Learn how to strictly and safely deploy applications using the /deploy workflow.",
-};
-
-import { Callout, StepList, Step, Terminal, TerminalLine, TerminalBlock, ProTips, Tip } from '@/components/mdx'
-
-# Production Deployment
-
-Ship with confidence using the safety-first `/deploy` workflow.
-
-## Overview
-
-The `/deploy` command is an **Audit & Release Conductor**.
-It forces your code to pass a rigorous health check before deployment.
-
-<Callout type="info" title="It stops you from deploying if:">
-  - Security vulnerabilities are found
-  - Linting errors exist
-  - TypeScript types are invalid
-  - Critical tests fail
-</Callout>
-
-## The Process
-
-<StepList>
-  <Step number={1} title="Execute Command">
-    When your code is ready, trigger the deployment pipeline.
-
-    ```bash
-    /deploy
-    ```
-  </Step>
-  <Step number={2} title="Pre-Flight Checklist">
-    The agent automatically audits your project health.
-
-    <div className="grid grid-cols-1 md:grid-cols-2 gap-4 mt-4">
-      <div className="bg-zinc-50 dark:bg-zinc-900 border border-zinc-200 dark:border-zinc-800 rounded-lg p-3">
-        <h4 className="text-sm font-semibold mb-1">🛡️ Security</h4>
-        <p className="text-xs text-zinc-500 dark:text-zinc-400 m-0">Scans for vulnerabilities & secrets</p>
-      </div>
-      <div className="bg-zinc-50 dark:bg-zinc-900 border border-zinc-200 dark:border-zinc-800 rounded-lg p-3">
-        <h4 className="text-sm font-semibold mb-1">📋 Quality</h4>
-        <p className="text-xs text-zinc-500 dark:text-zinc-400 m-0">Enforces Linting & Type Safety</p>
-      </div>
-    </div>
-  </Step>
-  <Step number={3} title="Release">
-    If checks pass, it builds and pushes to your platform (Vercel, Docker, etc).
-  </Step>
-</StepList>
-
-## Example Session
-
-<Terminal>
-  <TerminalLine type="user">/deploy</TerminalLine>
-
-  <TerminalBlock>
-    <TerminalLine type="agent">**Running Pre-Flight Checks...**</TerminalLine>
-    <div className="space-y-1 mt-2">
-      <div>🔄 Security Scan... <span className="text-green-400">PASSED</span></div>
-      <div>🔄 Lint Check... <span className="text-green-400">PASSED</span></div>
-      <div>🔄 Type Validation... <span className="text-green-400">PASSED</span></div>
-    </div>
-    <br/>
-    <span className="text-green-400">✅ All checks passed!</span>
-    Deploying to Vercel...
-  </TerminalBlock>
-
-  <TerminalBlock highlight>
-    <TerminalLine type="agent">**🚀 Deployment Complete!**</TerminalLine>
-    <div className="space-y-1 mt-2">
-      <div>🌐 URL: <span className="text-blue-400">https://my-app.vercel.app</span></div>
-      <div>💚 Health Check: <span className="text-green-400">OK</span></div>
-    </div>
-  </TerminalBlock>
-</Terminal>
-
-## Pro Tips
-
-<ProTips>
-  <Tip title="Check First">
-    Run `/deploy check` to dry-run validations without deploying.
-  </Tip>
-  <Tip title="Rollback Safety">
-    Use `/deploy rollback` to instantly revert to the last stable version.
-  </Tip>
-</ProTips>
-
-## Next Steps
-
-- Try `/deploy check` to run pre-flight checks
-- Learn about [Multi-Agent Orchestration](/docs/guide/examples/orchestration)

package/web/src/app/docs/guide/examples/new-feature/page.mdx

@@ -1,102 +0,0 @@
-export const metadata = {
-  title: "Example: Add a New Feature | Antigravity Kit",
-  description: "Step-by-step guide on adding new features to an existing application using Antigravity Kit workflows.",
-};
-
-import { Callout, StepList, Step, Terminal, TerminalLine, TerminalBlock, ProTips, Tip } from '@/components/mdx'
-
-# Add a New Feature
-
-Learn how to safely add complex features to an existing codebase using the `/enhance` workflow.
-
-## Overview
-
-The `/enhance` workflow is your day-to-day tool for iterative development.
-Unlike `/create` which builds from scratch, `/enhance` focuses on surgically adding functionality without breaking existing code.
-
-<Callout type="info">
-  **Scenario:** Adding a "Dashboard Analytics" feature to an existing SaaS application.
-</Callout>
-
-## The Process
-
-<StepList>
-  <Step number={1} title="Feature Planning">
-    Describe your feature requirements clearly.
-
-    ```bash
-    /enhance Add an analytics dashboard for user activity
-    Requirements:
-    - Track daily active users and page views
-    - Visual charts using Recharts
-    - API endpoint to aggregate data
-    ```
-  </Step>
-  <Step number={2} title="Component Implementation">
-    Specialists implement the full vertical slice.
-
-    <div className="grid grid-cols-2 md:grid-cols-4 gap-3 mt-4">
-      <div className="bg-zinc-50 dark:bg-zinc-900 border border-zinc-200 dark:border-zinc-800 rounded-lg p-3 text-center">
-        <div className="text-xs font-semibold">Database</div>
-      </div>
-      <div className="bg-zinc-50 dark:bg-zinc-900 border border-zinc-200 dark:border-zinc-800 rounded-lg p-3 text-center">
-        <div className="text-xs font-semibold">Backend</div>
-      </div>
-      <div className="bg-zinc-50 dark:bg-zinc-900 border border-zinc-200 dark:border-zinc-800 rounded-lg p-3 text-center">
-        <div className="text-xs font-semibold">Frontend</div>
-      </div>
-      <div className="bg-zinc-50 dark:bg-zinc-900 border border-zinc-200 dark:border-zinc-800 rounded-lg p-3 text-center">
-        <div className="text-xs font-semibold">Testing</div>
-      </div>
-    </div>
-  </Step>
-  <Step number={3} title="Verify Integration">
-    Run `final checks` to validate bundle size, accessibility, and tests.
-  </Step>
-</StepList>
-
-## Example Session
-
-<Terminal>
-  <TerminalLine type="user">/enhance add dark mode toggle</TerminalLine>
-
-  <TerminalBlock>
-    <TerminalLine type="agent">**Analyzing codebase...**</TerminalLine>
-    <div className="text-xs mt-2">
-      Found: Tailwind CSS with no dark mode config<br/>
-      Plan: Update tailwind.config, add ThemeProvider, create toggle component
-    </div>
-  </TerminalBlock>
-
-  <div className="space-y-2 pl-8 mb-4">
-    <div className="flex items-center gap-2">
-      <span className="w-2 h-2 rounded-full bg-purple-500 animate-pulse"></span>
-      <span><strong>Frontend:</strong> Creating ThemeToggle...</span>
-    </div>
-    <div className="flex items-center gap-2">
-      <span className="w-2 h-2 rounded-full bg-green-500 animate-pulse"></span>
-      <span><strong>Testing:</strong> Adding theme tests...</span>
-    </div>
-  </div>
-
-  <TerminalBlock highlight>
-    <TerminalLine type="agent">**✅ Feature Added!**</TerminalLine>
-    <span className="text-zinc-400">Run `/preview start` to test.</span>
-  </TerminalBlock>
-</Terminal>
-
-## Pro Tips
-
-<ProTips>
-  <Tip title="Check Dependencies">
-    Use `checklist.py` to prevent bundle bloat from new libraries.
-  </Tip>
-  <Tip title="Keep It Modular">
-    Isolate new components to minimize side effects on existing code.
-  </Tip>
-</ProTips>
-
-## Next Steps
-
-- Try `/enhance` in your project
-- See [Test Generation](/docs/guide/examples/test) for coverage

package/web/src/app/docs/guide/examples/orchestration/page.mdx

@@ -1,99 +0,0 @@
-export const metadata = {
-  title: "Example: Multi-Agent Orchestration | Antigravity Kit",
-  description: "Learn how to coordinate multiple specialist agents for complex projects using the /orchestrate workflow.",
-};
-
-import { Callout, StepList, Step, Terminal, TerminalLine, TerminalBlock, ProTips, Tip, FeatureGrid, Feature } from '@/components/mdx'
-
-# Multi-Agent Orchestration
-
-Build entire SaaS platforms by coordinating specialist agents with the `/orchestrate` workflow.
-
-## Overview
-
-Most AI interactions are 1-on-1. The `orchestrator` agent changes this by acting as a **Project Manager**.
-It breaks down a large request (e.g., "Build a SaaS MVP") into tasks and assigns them to the best specialist for the job.
-
-<FeatureGrid>
-  <Feature title="Backend" description="API & DB Architect" />
-  <Feature title="Frontend" description="UI/UX Specialist" />
-  <Feature title="Security" description="Safety Auditor" />
-  <Feature title="QA" description="Test Engineer" />
-</FeatureGrid>
-
-## The Process
-
-<StepList>
-  <Step number={1} title="Project Brief">
-    Describe the high-level goal. The orchestrator will interview you to clarify requirements.
-
-    ```bash
-    /orchestrate Build a "Course Platform" MVP with:
-    - User Authentication (NextAuth)
-    - Stripe Payments
-    - Video Hosting (Mux)
-    - Dashboard for Instructors
-    ```
-  </Step>
-  <Step number={2} title="Phase 1: Planning">
-    The `project-planner` agent creates a detailed roadmap (`PLAN.md`).
-
-    <div className="bg-zinc-50 dark:bg-zinc-900 p-3 rounded-lg text-xs font-mono border-l-2 border-blue-500 mt-2">
-      ...<br/>
-      ### 2.1 Database Schema<br/>
-      - Users (id, email, role)<br/>
-      - Courses (id, title, price)<br/>
-      ...
-    </div>
-  </Step>
-  <Step number={3} title="Phase 2: Execution">
-    Agents work in parallel. The Orchestrator monitors progress and unblocks dependencies.
-  </Step>
-</StepList>
-
-## Example Session
-
-<Terminal>
-  <TerminalLine type="user">/orchestrate Build E-commerce MVP</TerminalLine>
-
-  <TerminalBlock>
-    <TerminalLine type="agent">**Activating Squad...**</TerminalLine>
-    Assigning tasks based on `PLAN.md`:
-  </TerminalBlock>
-
-  <div className="space-y-3 pl-8">
-    <div className="flex items-center gap-2">
-      <span className="w-2 h-2 rounded-full bg-yellow-500 animate-pulse"></span>
-      <span><strong>Backend-Specialist:</strong> Configuring Prisma Schema...</span>
-    </div>
-    <div className="flex items-center gap-2">
-      <span className="w-2 h-2 rounded-full bg-blue-500 animate-pulse"></span>
-      <span><strong>Frontend-Specialist:</strong> Building ProductCard component...</span>
-    </div>
-    <div className="flex items-center gap-2">
-      <span className="w-2 h-2 rounded-full bg-purple-500 animate-pulse"></span>
-      <span><strong>Security-Auditor:</strong> Reviewing auth flow...</span>
-    </div>
-  </div>
-
-  <TerminalBlock highlight>
-    <TerminalLine type="agent">**✅ Project Complete!**</TerminalLine>
-    All tasks finished. Run `npm run dev` to start.
-  </TerminalBlock>
-</Terminal>
-
-## Pro Tips
-
-<ProTips>
-  <Tip title="Start Small">
-    Don't try to build Facebook in one go. Orchestrate an MVP first, then use `/enhance` to iterate.
-  </Tip>
-  <Tip title="Define Auth">
-    Always specify how users log in (e.g., "Use NextAuth with Google"). It's a key architectural decision.
-  </Tip>
-</ProTips>
-
-## Next Steps
-
-- Learn about [Systematic Debugging](/docs/guide/examples/debugging) to maintain your complex app
-- See [Deployment](/docs/guide/examples/deployment) to ship your MVP

package/web/src/app/docs/guide/examples/plan/page.mdx

@@ -1,76 +0,0 @@
-export const metadata = {
-  title: "Example: Project Planning | Antigravity Kit",
-  description: "Learn how to use the /plan workflow to create detailed project plans before implementation.",
-};
-
-import { Callout, StepList, Step, Terminal, TerminalLine, TerminalBlock, ProTips, Tip } from '@/components/mdx'
-
-# Project Planning
-
-Create detailed implementation plans before writing code with the `/plan` workflow.
-
-## Overview
-
-The `/plan` command activates **planning-only mode**.
-It uses the `project-planner` agent to create a detailed plan file without writing any code.
-
-<Callout type="info">
-  **Critical Rule:** NO CODE is written during planning. Only `PLAN.md` is created.
-</Callout>
-
-## The Process
-
-<StepList>
-  <Step number={1} title="Describe Your Project">
-    Tell the planner what you want to build.
-
-    ```bash
-    /plan e-commerce site with cart and checkout
-    ```
-  </Step>
-  <Step number={2} title="Socratic Questions">
-    The planner asks clarifying questions before creating the plan.
-  </Step>
-  <Step number={3} title="Plan Generated">
-    Creates `docs/PLAN-{slug}.md` with tasks and agent assignments.
-  </Step>
-</StepList>
-
-## Example Session
-
-<Terminal>
-  <TerminalLine type="user">/plan SaaS dashboard with analytics</TerminalLine>
-
-  <TerminalBlock>
-    <TerminalLine type="agent">**Clarifying Questions:**</TerminalLine>
-    <div className="text-yellow-300 text-xs mt-2">
-      1. What metrics? (users, revenue?)<br/>
-      2. Real-time or daily?<br/>
-      3. Charting library?
-    </div>
-  </TerminalBlock>
-
-  <TerminalLine type="user">Users + revenue, real-time, Recharts</TerminalLine>
-
-  <TerminalBlock highlight>
-    <TerminalLine type="agent">**✅ Plan Created!**</TerminalLine>
-    `docs/PLAN-saas-dashboard.md`<br/>
-    <span className="text-zinc-400">Run `/create` to implement.</span>
-  </TerminalBlock>
-</Terminal>
-
-## Pro Tips
-
-<ProTips>
-  <Tip title="Answer Thoroughly">
-    The more context you provide, the better the plan.
-  </Tip>
-  <Tip title="Edit the Plan">
-    Modify the generated plan before implementation.
-  </Tip>
-</ProTips>
-
-## Next Steps
-
-- Run `/plan` for your next major feature
-- After planning, use [Create Application](/docs/guide/examples/create) to implement