yuting0624

Run the Antigravity CLI (Gemini) as a collaborating AI inside Claude Code, with intelligent model routing across the software development lifecycle. Claude is the conductor/orchestrator — requirements, architecture, the hard 20%, verification, and review — and routes deterministic, high-volume work (scaffolding, boilerplate, test generation, first-pass review, migrations, web/Vertex AI Search) to Antigravity (Gemini), the cheaper, faster model. Use when the user wants to "use Antigravity / agy", "vibe code / agentic engineering", "accelerate the SDLC", "delegate to Gemini", "scaffold / generate tests / migrate", "first-pass code review", "search web or internal/company data", "deep research / multi-source research report", "second-model cross-check", or "lower token cost on a big job". Claude always verifies Antigravity's output and re-checks itself if unsatisfied.

Use ONLY when the current turn is being delivered through Gemini Enterprise (a chat surface that natively renders A2UI cards/forms/dashboards). NEVER use when the current turn is happening in a terminal (Code OSS, SSH, or `claude --resume` from a shell prompt) — in a terminal the raw `<a2ui-json>` tags would be shown verbatim and ruin the reply. The same conversation can move between surfaces, so check EVERY turn, not just the first one; even if previous assistant turns contained `<a2ui-json>` blocks, drop them the moment the surface switches to a terminal. Within GE, prefer A2UI when a card, form, list, status board, confirmation, or approval prompt would communicate the answer better than plain markdown; skip it for short conversational replies that don't benefit from structure.