To make Google Antigravity useful for recurring coding chores, first give the agent the right project context, then write a bounded task with clear success criteria. Add persistent guidance for conventions and reusable instructions for repeatable processes. The setup depends on which Antigravity surface you use: the IDE has Rules and Workflows, while Antigravity 2.0 uses Agent Skills for durable task instructions.
Choose the Antigravity surface that fits your work
Google presents Antigravity 2.0 as a desktop agent command center, Antigravity CLI as a terminal interface, and Antigravity IDE as an AI-powered development environment. The current Google getting-started guide covers all three. The setup steps below are deliberately surface-specific: the IDE’s Customizations panel is where its Rules and Workflows are configured, and its exact menus should not be assumed to apply to the desktop app or CLI.
As an Amazon Associate I earn from qualifying purchases.
For Antigravity 2.0, Google lists macOS 12 or later on Apple Silicon (Intel is unsupported), Windows 10 64-bit, Linux with glibc 2.28 or later and glibcxx 3.4.25 or later, and Googlebook OS in its current getting-started requirements. Check the live guide for the latest installation details rather than relying on a saved installer or older requirements.
Give the agent the right project context
Create a project in Antigravity 2.0
- Use the folder-plus control and choose New Project.
- Add one or more local folders or Git repositories, then select Create. Google says that adding multiple folders gives the agent cross-repository context; each project maintains isolated settings and security policies.
- Enter the task in the project’s chat input and choose an agent mode. Local lets the agent operate in active folders; New worktree isolates its work in a Git worktree.
Pick the smallest useful set of folders. A task that spans repositories needs that context; a task limited to one project does not benefit from unrelated files.
#1 Best Overall
Write a bounded task
A useful request names the outcome, the files or boundaries that matter, and how you will verify success. For example: “Add unit tests for the date parsing helpers in src/date. Keep the public API unchanged, follow the existing test style, and run the project’s relevant test command. Show me the plan before editing.” This is a prompt-writing pattern, not a required Google format.
On surfaces that support these documented commands, use /grill-me to clarify details and align on a plan before implementation, or /goal when you want the agent to continue until the task is complete. Antigravity 2.0 also documents /schedule for a one-time or recurring instruction and /browser for controlling browser debugging behavior in Chrome. Confirm command availability in the surface you are using.
Choose the right reusable guidance
The mechanisms are related but not interchangeable: Rules supply standing context, while Workflows and Skills are invoked or selected for task-specific instructions. Use the one that matches when the guidance should apply.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchRank #2
| Mechanism | When it applies | Good fit | Scope | Migration status |
|---|---|---|---|---|
| IDE Rules | Persistent, reusable prompt-level context | Project conventions and standing expectations | Global or workspace | No shutdown date identified in the reviewed Google documentation |
| IDE Workflows | On demand, when explicitly invoked | Ordered steps for a repeated process | Global or workspace | Current system stops working October 19, 2026 |
| Antigravity 2.0 Skills | Selected when relevant or invoked with a slash command | Task-specific knowledge and optional resources or scripts | Global or workspace | Presented by Google as a migration destination for Workflows |
These distinctions and the migration date come from Google Antigravity’s Workflows documentation, Skills documentation, and Google’s Antigravity IDE codelab.
Set up Rules and Workflows in the IDE
Add a Rule for conventions that should always apply
- Open the ellipsis menu in the Agent panel.
- Choose Customizations, then open Rules.
- Create the Rule at global scope for conventions you want across workspaces, or workspace scope for project-specific expectations.
Keep Rules focused on durable expectations, such as the project’s code style or preference for modular changes. Google’s codelab describes Rules as guidance for agent behavior; a Rule is not the right place for a long, task-by-task procedure that should run only when requested.
Create an on-demand Workflow
- In the Agent panel, open the ellipsis menu and choose Customizations, then Workflows.
- Create a Workflow at global scope for a repeatable process across workspaces, or at workspace scope for a project-specific process.
- Write a title, description, and ordered task steps in the Workflow’s Markdown file.
- Invoke it in the IDE using its slash command, such as
/generate-unit-tests.
Workflows can call other Workflows, and each file is limited to 12,000 characters, according to Google’s Workflows documentation. A practical Workflow might ask the agent to inspect changed files, prepare a pull-request review, or run checks already established by the project. Keep each sequence centered on one recurring job rather than trying to encode every possible task in one file.
Use Agent Skills for Antigravity 2.0
Google documents an Agent Skill as a folder containing a required SKILL.md with task instructions, plus optional scripts, examples, and resources. For Antigravity 2.0, place a workspace Skill under <workspace-root>/.agents/skills/<skill-folder>/, or a global Skill under ~/.gemini/config/skills/<skill-folder>/. The agent may select a relevant Skill based on its description, or you can invoke one with /<skill-name>. See Google’s Skills documentation for the current format and details.
The transition is time-sensitive. Google’s IDE Workflows page says the current Workflows stop working on October 19, 2026, and points users to a Workflows-to-Skills migration guide or /migrate-workflows. That date is still in the future as of October 8, 2026. If you rely on an existing IDE Workflow, check the live documentation and migrate it before the cutoff rather than assuming it will keep running.
Review the work instead of trusting a completion message
Google’s Antigravity IDE codelab describes reviewing an implementation plan and task list, accepting or rejecting code changes, commenting on artifacts to redirect work, and using Undo changes when needed. Google’s overview also describes structured deliverables such as plans, diffs, diagrams, screenshots, and browser recordings. These artifacts make the agent’s work inspectable; they do not establish that the result is correct.
Rank #4
- Stay present in every scenario: Every conversation is covered, in person, on calls, and online. 4 MEMS + 1 VPU microphones with AI beamforming capture every voice across the room. Smart Dual-Mode Recording switches automatically between phone calls and in-person. The free Plaud Desktop captures online meetings without a bot
- Walk out of every meeting with notes ready to act on: Plaud Intelligence transcribes in 112 languages with speaker labels and turns each recording into action items, decisions, and follow-ups, structured and ready to use. Choose from 10,000+ customizable templates tailored to your role and industry
- AI summary ready before you reach your desk: Auto Transfer moves each recording to the Plaud app automatically, and AutoFlow transcribes and summarizes so your notes are ready before you are back at your desk. Upgrade anytime to Pro (1,200 min/mo) or Unlimited
- Access your AI workspace anywhere: One connected workspace across Plaud Desktop, Plaud Web, and the Plaud mobile app, so your conversations and finished work follow you everywhere
- Your conversations stay private and yours: Compliant with ISO 27001, ISO 27701, SOC 2, HIPAA, GDPR, and EN 18031, with zero data used to train AI models. Trusted by 2.5M+ professionals, including legal, medical, and business professionals handling sensitive information
- State the request and what would count as success.
- Inspect the proposed plan and correct misunderstandings before implementation.
- Review the code diff for unintended files or changes outside the task’s boundaries.
- Run the project’s relevant checks yourself and examine their results.
- Inspect any walkthrough or browser evidence that bears on the requested behavior, then accept or revise the result.
This review sequence applies Google’s documented review controls as a practical routine; it is not a guarantee that every task or surface produces the same artifacts.
Know the IDE’s support boundary
Google’s Antigravity IDE overview states: “Antigravity IDE is not supported for enterprise customers.” Organizations evaluating the IDE should verify current support and deployment options with Google before adopting it.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.




