The Antigravity Pro Developer Playbook#

Using an agentic IDE like Antigravity in 2026 requires a shift from “typing code” to “orchestrating intelligence.” This guide covers the mental models and technical strategies to build complex apps like GenDash while maximizing credit efficiency.

1. The Model Garage: Choosing the Right Engine#

In Antigravity, you have a team of experts. Don’t use a supercar for a grocery run.

Model Role Best For Credit Cost
Gemini 3.1 Pro (High) The Architect Designing the data model (SwiftData), complex math, and initial project scaffolding. High (Weekly Cap)
Gemini 3.1 Pro (Low) The Lead Dev Implementing business logic, writing multi-file features, and standard debugging. Medium (5hr Quota)
Gemini 3 Flash The Junior Dev UI styling, padding/color tweaks, fixing typos, and writing boilerplate. Lowest (Near Free)
Claude Sonnet 4.6 The Designer Refactoring messy SwiftUI into elegant, human-readable layouts. High (Credits)
Claude Opus 4.6 The Specialist Solving “impossible” bugs or deep architectural audits. Use as a last resort. Highest (Credits)

2. Mode Mastery: Planning vs. Fast#

The Mode selector determines how much “thinking” the agent does before it touches your files.

Planning Mode#

  • When to use: Adding new features (Live Activities), changing the app’s navigation structure, or modifying the database.
  • How it works: The agent creates a multi-step roadmap. It performs a discovery phase using the Xcode bridge to ensure it doesn’t break the project.
  • Pro Tip: Always review the “Plan” before clicking Run. This is where you catch logic errors before they are committed.

Fast Mode#

  • When to use: Changing button colors, updating text labels, or simple one-line logic fixes.
  • How it works: The agent executes the task immediately without a roadmap.
  • Benefit: Massive credit savings and near-instant execution.

3. Mission-Driven Development (MDD)#

In a 2026 agentic workflow, your MISSION.md is the “Long-Term Memory” of the project.

  1. The Ground Truth: Keep a MISSION.md in your root folder containing the math (interpolation formulas), security rules (redaction of UP_UNIFI_PASS), and core requirements.
  2. The Handover: When starting a fresh chat, point the agent to this file first. This prevents “AI Drift” and keeps the agent from suggesting old or irrelevant logic.
  3. The Sync: Periodically ask the agent: “Update MISSION.md to reflect our current progress and new architectural decisions.”

4. Quota & Credit Management#

Antigravity operates on a tiered usage system. Avoid hitting the “6-day Wall” by managing your history.

The History Tax#

Every time you send a message, the model re-reads the entire chat history.

  • Images/Screenshots: Highly effective for UI debugging, but very heavy (500+ tokens per image).
  • Resetting Context: Once a feature (like the Dynamic Island) is working and committed to Git, start a new conversation. This wipes the heavy images and old context, making the agent faster and cheaper.

The Emergency Tank#

  • AI Credits: Your 1,000 credits are a safety net.
  • Overages: Toggle “Enable AI Credit Overages” only when your weekly Pro quota is exhausted and you have critical work to finish.

5. The Xcode Bridge & Sideloading#

Antigravity interacts with Xcode targets, but some tasks still require the “Human in the Loop.”

  • Target Creation: Never let an AI try to create a New Target (like a Widget Extension) via the raw .pbxproj file. It will likely corrupt the project. Create targets manually in the Xcode GUI, then let the agent fill them with code.
  • Developer Override: When sideloading to a physical iPhone, remember the “Trust” sequence: Settings > General > VPN & Device Management and Settings > Privacy & Security > Developer Mode.
  • Orientation & Info.plist: For apps like GenDash, always lock the orientation to Portrait in the Target settings to prevent UI breakage during generator sessions.

6. The “Pro” Routine#

  1. Plan with Gemini 3.1 Pro (High).
  2. Build with Gemini 3.1 Pro (Low).
  3. Refine UI with Gemini 3 Flash.
  4. Clean up by starting a New Chat every 2-3 hours of work.
  5. Document progress back into MISSION.md.