## What this does
Adds **Antigravity** to the Supabase AI agent plugin docs.
- **Plugin docs** (`AgentPluginsPanel`): Antigravity client between
Cursor and Gemini CLI. The install step is a copyable `agy plugin
install https://github.com/supabase-community/supabase-plugin` (checked
with `agy` 1.4.0: it installs v0.1.17 with both skills and the MCP
server). A note below points to the `/plugin` slash command and
[Antigravity's plugin
docs](https://antigravity.google/docs/plugins/#managing-plugins-by-surface).
- **Icon**: replaces the existing Antigravity icon (MCP client picker
and "Pick your agent" grid share it) with the official full-color icon
from the [Antigravity press assets](https://antigravity.google/press/).
- **"Pick your agent" grid**: Antigravity now shows the "Plugin + MCP"
badge and links to the plugin page.
Plugin support shipped in supabase-community/supabase-plugin
[v0.1.17](https://github.com/supabase-community/supabase-plugin/releases/tag/v0.1.17)
(#66), validated with `agy` 1.3.5 and 1.4.0.
## Testing
Ran the docs app locally at 41bf5af, opened
`/docs/guides/ai-tools/plugins` and selected Antigravity. The icon and
install step render in light and dark mode, both links point to
`https://antigravity.google/docs/plugins/#managing-plugins-by-surface`,
and Claude Code is still the default selection.
<img width="771" height="349" alt="pr51647-antigravity-dark"
src="https://github.com/user-attachments/assets/a4c682f1-a67e-4a89-8060-7bf94adb2388"
/>
<img width="771" height="349" alt="pr51647-antigravity-light"
src="https://github.com/user-attachments/assets/65611703-789c-456e-b03f-b444b1e3958e"
/>
<img width="243" height="284" alt="image"
src="https://github.com/user-attachments/assets/b5c87b73-21d3-4665-ae75-4915b75dfefd"
/>
Closes AI-1315
---------
Co-authored-by: Barry Roodt <barry@jumptag.co.za>
Co-authored-by: Barry Roodt <barry.roodt@supabase.io>
Reference Docs
Supabase Reference Docs
Maintainers
If you are a maintainer of any tools in the Supabase ecosystem, you can use this site to provide documentation for the tools & libraries that you maintain.
DocSpec
We use documentation specifications which can be used to generate human-readable docs.
- OpenAPI: for documenting API endpoints.
- SDKSpec (custom to Supabase): for SDKs and client libraries.
- ConfigSpec (custom to Supabase): for configuration options.
- CLISpec (custom to Supabase): for CLI commands and usage.
The benefit of using custom specifications is that we can generate many other types from a strict schema (eg, HTML and manpages). It also means that we can switch to any documentation system we want. On this site we use Next.js, but on Supabase's official website, we use a custom React site and expose only a subset of the available API for each tool.
Contributing
To contribute to docs, see the style guide for how to write a page, and the developers' guide and contributing guide for repo mechanics. If you write with an AI coding agent, use the /write-the-docs skill to draft and /edit-the-docs to revise an existing page.