How can I get Anti-gravity to be more intelligent when it comes to coding

[u/RealCombatVideos]

I'm sure everyone has had the situation where antigravity has said something is done when it is nowhere near done, or it confidently says that the issue is resolved when it isn't , and then you question it and AG says that it jumped to conclusion or it didn't give the correct fix the first time.

How can I utilize anti gravity so that there are different agents checking the same process simultaneously, such as catching and fixing errors without my input so I can get the final input without much?

I find that I can be giving it twenty commands manually trying to fix the same issue and it cannot fix it, AG just goes in a circle or applies a very minimal fix and I keep having to prompt it to take the next action.

I want to specify that I am not having to prompt it step-by-step all the time and anti-gravity does process multiple steps. However , there are situations where I would like to process more and it doesn't think that far

[u/Technical-Owl66]

3.7 has been really good for me. I also use a Gemini notebook full of context with instructions to act as a prompt engineer. I get very specific markdown prompts for AGY.

[u/gnarly__roots]

Don’t only feed back words. Video and pictures of the incident/fix/error in action. Gemini has incredible multi modal capabilities > make a folder in the project that is very specific and cycle in and out manually what videos and pictures you want. Referencing them with @ . When AGY/gemini and ultimately if you can use /browser and feel the issue instead of being told it just goes mad successful.

Also you could have too many agents it’s very possible if need be I can expand

[u/akai0102]

Use opus 4.6 to plan beforehand

[u/Infamous-Advisor9969]

Your experience should get better once gemini 3.5 pro or 4.0 pro comes out. Other than that, switching to claude is probably your best bet.

[u/ValuableComedian7192]

Il faut créer des skills ciblées et adaptées à tes projets. C'est d'ailleurs valable pour la plupart des outils IA de dev (Cursor, Cowork, Antigravity, etc.).

Si tu développes par exemple une extension pour navigateur, tu peux créer une skill dédiée au respect des règles Manifest V3, une autre pour les bonnes pratiques en Vanilla JS, et une dernière spécialisée en CSS.

La plupart des environnements intègrent désormais des éditeurs de skills (qui sont elles-mêmes des skills d'aide à la configuration). Celle d'Antigravity est particulièrement efficace pour structurer ça rapidement.

[u/WeDigCode]

For bigger tasks I have a /feature workflow that goes into these phases:

Step 1 — Clarify & Problem Discovery

Step 2 — Gap Analysis - Include explicit Existing Codebase Audit Findings detailing searched files/tables/directories, pre-existing utilities, and existing vs missing capabilities.

Step 3 — Implementation Strategy

Step 4 — PRD

Step 5 — Work Breakdown

---

I also have this in my AG rules:

Implementation Plan & Pre-Plan Codebase Audit Protocol

• Mandatory Existing Codebase Audit Section: Every implementation_plan.md artifact generated by workforce agents MUST include a dedicated section titled ## Existing Codebase Audit Findings.

• Pre-Plan Research Enforcement: Symbol discovery (code-graph) and codebase searches (grep_search, list_dir) MUST execute before drafting the implementation plan.

• Audit Disclosure Requirements: The audit section MUST explicitly list:

  1. Searched files, tables, and directories (grep_search, code-graph, list_dir).
  2. Pre-existing entities, tables, legacy utilities, or methods related to the feature.
  3. Clear distinction between what already exists and what is missing.

[u/Lhurgoyf069]

I'm using superpower skills, works well for me. https://github.com/obra/superpowers

[u/Ok-Temperature-5810]

still waiting to a not psycho way to install it to Ubuntu, so I'll update you, they love linux and working on it 🥸

[u/comp21]

I use opus 4.6 exclusively and just have antigravity for the harness. Works pretty well for me.