Hello, y’all​

! This specifically about:
Google Antigravity’s official documentation(Google Antigravity Docs - Home)
A centralized thread for the docs: a community effort
It’s no secret that the official Antigravity documentation is in bad shape right now… Wrong/outdated info/dead links/material that is incorrect, etc. & it has been like this for a while, it’s a shame. Let’s do something about it, together​
!
-
What:
Reporting issues with the Antigravity documentation in one thread, in a standardized format to make it easy, organized & comprehensible. -
Why:
Sadly the Antigravity documentation is currently in a bad shape. I believe that Antigravity deserves proper documentation! For new users, as well as experienced users who wish to deep dive into all that Antigravity has to offer. -
How:
Instead of having multiple threads with single reports regarding the documentation, this can serve as a centralized thread. Hopefully this makes it easier for the officials to collect and act on it
.
Report format explained:
Problem: JSON plugin schema link invalid.
Date: 01-08-26
Short summary: (optionally with screenshot) describe the issue, briefly. Date in “dd-mm-yy” format.
Example:
Antigravity CLI>Plugins & Skillscontains a JSON schema link which is invalid.
Problem: detailed description, preferably with a copy of the problem in the documentation and/or screenshot.
Example:
The link “plugin JSON manifest schema” mentioned is not found: “https://antigravity.google/schemas/v1/plugin.json”, results in: “Error: Not Found. The requested URL /schemas/v1/plugin.json was not found on this server.” .
Link to the documentation: link to the page(s) where this occurs, if applicable use the direct link to the section (see screenshot).
Example:
https://antigravity.google/docs/cli/plugins#the-plugin-manifest-pluginjson
Proposed fix or solution: clarify what you propose or if you know the fix or solution, mention it. This can be left blank, of course!
Example:
Update the plugin manifest JSON schema URL to the latest valid one, or exclude from the documentation if it’s redundant.
General advice
-
Report multiple things? Don’t bundle them, re-use the format:
Multiple reports all into one cramped post defeat the purpose. -
Proposal, request, etc.? Change the “Problem” prefix:
for a quick indication, makes it easier.
Report format with styling to copy:
# [Problem: Title]
*`Date: [dd-mm-yy]`*
ℹ️ ***Short summary:*** `[Section]>[Page Name(s)]`
❌ ***Problem:***
đź”— ***Link to the documentation:***
âś… ***Proposed fix or solution***:
Friendly tip: screenshots can be pasted in your post using: ctrl + v or cmd + v


