johnnycrypto289/masonclawv4/antigravity

Antigravity IDE Skill

What It Is

Google Antigravity is an agentic IDE (Gemini 3 Pro) installed at /Applications/Antigravity.app. It builds websites, apps, and code autonomously. Mason orchestrates it for business projects.

Paths

• App: /Applications/Antigravity.app
• CLI: /Applications/Antigravity.app/Contents/Resources/app/bin/antigravity
• Config: ~/.antigravity/
• Gemini context: ~/.gemini/GEMINI.md (points to Mason workspace)
• MCP config: ~/.gemini/antigravity/mcp_config.json
• Scratch space: ~/.gemini/antigravity/scratch/ (where projects are built)
• Brain/tasks: ~/.gemini/antigravity/brain/ (task history + walkthroughs)
• Conversations: ~/.gemini/antigravity/conversations/

Commands

Open a project in Antigravity

/Applications/Antigravity.app/Contents/Resources/app/bin/antigravity <folder-path>

Open a specific file

/Applications/Antigravity.app/Contents/Resources/app/bin/antigravity --goto <file:line>

Check completed projects

ls ~/.gemini/antigravity/scratch/

Read task walkthroughs (what Antigravity built)

find ~/.gemini/antigravity/brain/ -name "walkthrough.md.resolved" -exec cat {} \;

Read task status

find ~/.gemini/antigravity/brain/ -name "task.md.resolved.*" | sort | tail -1 | xargs cat

Workflows

1. Check what Antigravity has built

1. List ~/.gemini/antigravity/scratch/ for completed projects
2. Read walkthrough files in brain/ for summaries
3. Report findings to Boss

2. Move completed project to business workspace

When Antigravity finishes a build:

1. Identify the business (CU, CE, WS, CD)
2. Copy from scratch to the right agent workspace:

• CU: ~/.openclaw/workspace-cu-midwest/projects/
• CE: ~/.openclaw/workspace-contractor-engage/projects/
• WS: ~/.openclaw/workspace-winkscope/projects/
• CD: ~/.openclaw/workspace-contractor-dispatch/projects/

1. Update the agent's memory with project details

3. Update GEMINI.md context

When Mason's system changes (new agents, new config, new tools), update ~/.openclaw/workspace/GEMINI.md and ~/.gemini/GEMINI.md so Antigravity stays in sync.

4. Wire MCP servers

Edit ~/.gemini/antigravity/mcp_config.json to connect Antigravity to external tools. See references/mcp-setup.md for details.

Key Rules

• Antigravity builds code. Mason deploys, monitors, and manages.
• Projects start in Antigravity's scratch space, then get moved to the right workspace.
• GEMINI.md is the bridge — keep it updated when Mason changes.
• MCP config connects Antigravity to Mason's data sources (Gmail, Trello, JobTread).