mirror of
https://github.com/supabase/supabase.git
synced 2026-10-05 09:25:06 +03:00
Miranda Limonczenko
abbf667084
## I have read the [CONTRIBUTING.md](https://github.com/supabase/supabase/blob/master/CONTRIBUTING.md) file. YES ## Problem The Docs E2E link checker found broken links throughout docs, starting with `phone-login.mdx` pointing to `/docs/guides/cli/config` (404). Old links like `/docs/guides/cli/config` still work on the live site because `supabase.com` has redirects set up for them, but these links break on the docs preview site, which is what the E2E check tests against. These issues look clean on the live site, and I didn't catch them in my first pass because I was testing production instead of the preview. The E2E check only tests the ~20 pages a given PR happens to touch, so fixing the pages it flagged kept exposing more of the same problem one page at a time as each fix pulled in a new file. To stop chasing this incrementally, I cross-referenced every `/docs/guides/*` and `/docs/reference/*` redirect source in `apps/www/lib/redirects.js` against actual usage across all of `apps/docs`, and verified each candidate against the live preview. ## Solution Rather than updating the Docs E2E link checker, this PR resolves the links. **Why:** we own these docs, so keeping the links clean without redirects is keeping the house maintained. See [Broken Window Theory](https://blog.codinghorror.com/the-broken-window-theory/). Updated every link still using an old path to point straight at the current page instead of relying on a redirect. This covers old links like: - `/docs/guides/cli/config` → `/docs/guides/local-development/cli/config` - `/docs/guides/cli/getting-started` → `/docs/guides/local-development/cli/getting-started` - `/docs/guides/cli/local-development` → `/docs/guides/local-development/database-migrations` - `/docs/guides/cli/managing-environments` → `/docs/guides/deployment/managing-environments` - `/docs/guides/cli/seeding-your-database` → `/docs/guides/local-development/seeding-your-database` - bare `/docs/guides/cli` → `/docs/guides/local-development` - `/docs/guides/platform/compute-add-ons` → `/docs/guides/platform/compute-and-disk` - `/docs/guides/platform/shared-responsibility-model` → `/docs/guides/deployment/shared-responsibility-model` - `/docs/guides/database` → `/docs/guides/database/overview` - `/docs/reference/javascript`, `/docs/reference/dart`, `/docs/reference/kotlin`, `/docs/reference/python`, `/docs/reference/csharp` → their `/introduction` pages (the redirect's own destination, `/start`, turned out to be dead even on production — a separate bug in `redirects.js` I didn't touch here) - and about 35 more of the same pattern, listed in the commit messages Also fixed a handful of dead heading anchors found along the way (links that resolve to the right page but point at a `#section` that got renamed or moved), including the original `#bigquery` anchor and a few in `connecting-to-postgres.mdx` where content moved to its own dedicated page. Left alone on purpose: - `content/guides/cli.mdx` — this page has no route in the docs app at all (no `app/guides/cli/` directory), so it 404s even in production before the `www` redirect ever fires. Fixing its internal link wouldn't change that; it needs an actual routing/content decision, not a link fix. - A few candidates that already resolve fine as-is (`pg_partman`, bare `/docs/reference/api`, bare `/docs/reference/cli`) — confirmed via curl, left untouched. ## Manual testing 1. Confirmed every new link target actually exists by checking the destination file/page and matching heading anchors. 2. Cross-referenced every `/docs/guides/*` and `/docs/reference/*` redirect source in `apps/www/lib/redirects.js` against real usage in `apps/docs`, and curl-verified each old path (404) and new path (200) against the live PR preview before fixing it. 3. Ran the Docs E2E link checker locally against changed pages. 4. Spot-checked the original broken link from CI (`/docs/guides/cli/config`) to confirm it now points to a working page.
53 lines
2.9 KiB
Plaintext
53 lines
2.9 KiB
Plaintext
---
|
|
id: 'ai-tools-plugins'
|
|
title: 'Supabase Plugin for AI Coding Agents'
|
|
subtitle: 'One-click setup for Supabase in your AI coding agent'
|
|
description: 'The Supabase plugin for AI coding agents bundles the MCP server and agent skills into a single install for your AI coding agent.'
|
|
sidebar_label: 'Supabase Plugin for AI Coding Agents'
|
|
---
|
|
|
|
The Supabase Plugin for AI Coding Agents gives your AI coding agent everything it needs to work with Supabase. It bundles the [Supabase MCP server](/docs/guides/ai-tools/mcp) and [Supabase agent skills](/docs/guides/ai-tools/ai-skills) so your agent can query your database, manage migrations, deploy Edge Functions, and follow Supabase and Postgres best practices — without manual configuration.
|
|
|
|
## Quick installation
|
|
|
|
```bash
|
|
npx plugins add supabase-community/supabase-plugin
|
|
```
|
|
|
|
The [`plugins`](https://www.npmjs.com/package/plugins) package auto-detects your installed AI coding agents and installs the Supabase plugin to all of them with one command. Use `--yes` to skip the confirmation prompt.
|
|
|
|
Or, follow the [manual installation](#manual-installation) steps for your specific agent.
|
|
|
|
## Why use the plugin?
|
|
|
|
Plugins for AI coding agents are packages of AI agent extensions. A single plugin can bundle any combination of:
|
|
|
|
- **MCP servers** — external tool integrations that let your agent interact with services like Supabase
|
|
- **Skills** — procedural knowledge and context your agent loads on demand to work more accurately
|
|
- **Hooks** — event handlers that run at agent lifecycle points (e.g. before or after a tool call)
|
|
- **Agents** — specialized sub-agents with specific personas and tool configurations
|
|
- **Slash commands** — custom commands you can invoke directly in chat
|
|
|
|
Bundling the [MCP server](/docs/guides/ai-tools/mcp) and [agent skills](/docs/guides/ai-tools/ai-skills) into a single plugin means you can set up both in one step. You can also install them separately if you prefer. You can install the plugin globally to use it across all your projects, or per project to keep it isolated.
|
|
|
|
## What's included
|
|
|
|
### Supabase MCP server
|
|
|
|
The [Supabase MCP server](/docs/guides/ai-tools/mcp) connects your AI coding agent directly to your Supabase projects. Once authenticated, your agent can query your database, manage migrations, deploy Edge Functions, and more — see the [full list of available tools](/docs/guides/ai-tools/mcp#available-tools).
|
|
|
|
### Supabase agent skills
|
|
|
|
Skills provide your agent with Supabase-specific procedural knowledge:
|
|
|
|
- **`supabase`** — Core guidance for working with Supabase products (Database, Auth, Edge Functions, Storage, Realtime)
|
|
- **`supabase-postgres-best-practices`** — Postgres query optimization, schema design, connection management, and RLS patterns
|
|
|
|
For a full list of available skills and supported agents, see [Agent Skills](/docs/guides/ai-tools/ai-skills).
|
|
|
|
## Manual installation
|
|
|
|
Alternatively, choose your AI coding agent and follow the installation steps:
|
|
|
|
<AgentPluginsPanel />
|