Supabase Multi Env Setup

What it does

When your agent uses it

• Setting up multi-environment deployments
• Isolating dev from prod data
• Configuring per-environment Supabase projects
• Promoting migrations through environments

Example prompts

• “supabase environments”
• “supabase staging”
• “supabase dev prod”
• “/supabase-multi-env-setup”

Requirements

• Node.js
• Compatibility (from SKILL.md): Designed for Claude Code
• Pre-approved tools (allowed-tools): Read, Write, Edit, Bash(npx supabase:*), Bash(supabase:*), Bash(vercel:*)

Workflow steps

3 steps, taken from the step headings in SKILL.md.

1. 1Environment Files and Project Layout
2. 2Environment-Aware Client and Safeguards
3. 3Migration Promotion and Database Branching

What it can do on your machine

Read from SKILL.md and the folder at commit 80f86df. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves these tools, so the agent can use them without asking each time:

  • Read
  • Write
  • Edit
  • Bash(npx supabase:*)
  • Bash(supabase:*)
  • Bash(vercel:*)

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  Shell commands in SKILL.md call:

  • npx
  • supabase
  • npm

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  Links to these hosts (documentation or services it may open):

  • supabase.com
  • 12factor.net

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names these keys or tokens, usually read from environment variables:

  • SUPABASE_DB_PASSWORD

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

• Compatibility

  Designed for Claude Code

  From compatibility in the SKILL.md frontmatter.

Context cost

Supabase Multi Env Setup loads about 2.2k tokens when it runs, and up to ~5.8k if it reads all its reference files. Until then it costs about 124 tokens; SKILL.md has 756 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~124

When it runs · the whole SKILL.md, loaded when a task matches

~2.2k

With references · SKILL.md plus every file in references/, read only if the agent opens them

~5.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

• NoteMentions a .env fileSKILL.md:42

  e.js 18+ with a framework that supports `.env` files (Next.js, Nuxt, SvelteKit, etc.)

• NoteMentions a .env fileSKILL.md:54

  ject with **shared migrations** and one `.env.*` file per

• NoteMentions a .env fileSKILL.md:55

  s at a different Supabase project; only `.env.local` is safe to

• NoteMentions a .env fileSKILL.md:60

  .env.local             # supabase start defaults (safe to commit)

• NoteMentions a .env fileSKILL.md:61

  .env.staging           # staging project creds  (gitignored)

• NoteMentions a .env fileSKILL.md:62

  .env.production        # production project creds (gitignored — NEVER commit)

• NoteMentions a .env fileSKILL.md:73

  for full `.env.*` contents, the `.gitignore` block, and the local-port reference.

• NoteMentions a .env fileSKILL.md:115

  - **Environment-specific `.env` files** — `.env.local`, `.env.staging`, `.env.production` with correct credentials

• NoteMentions a .env fileSKILL.md:131

  | `Wrong environment keys in client` | `.env` file mismatch | Check `SUPABASE_ENV` var and verify URL matches expected p

• NoteMentions a .env fileSKILL.md:142

  abase start        # local, copy keys to .env.local

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit 80f86df, republished under its MIT licence (© jeremylongshore). 756 words, ~2,197 tokens.

name

supabase-multi-env-setup

description

Configure Supabase across development, staging, and production with separate projects, environment-specific secrets, and safe migration promotion. Use when setting up multi-environment deployments, isolating dev from prod data, configuring per-environment Supabase projects, or promoting migrations through environments. Trigger with "supabase environments", "supabase staging", "supabase dev prod", "supabase multi-project", "supabase env config", "database branching".

allowed-tools

Read, Write, Edit, Bash(npx supabase:*), Bash(supabase:*), Bash(vercel:*)

compatibility

Designed for Claude Code

version

1.54.0

license

MIT

author

Jeremy Longshore <jeremy@intentsolutions.io>

tags

saas, supabase, deployment, environments, multi-env, devops

supabase/migrations/   # shared schema — every env applies the same migrations
.env.local             # supabase start defaults (safe to commit)
.env.staging           # staging project creds  (gitignored)
.env.production        # production project creds (gitignored — NEVER commit)

npx supabase link --project-ref <target-ref>

export function requireNonProduction(operation: string): void {
  if (isProduction()) {
    throw new Error(`[BLOCKED] "${operation}" is not allowed in production.`);
  }
}

npx supabase db reset                              # local: all migrations + seed
npx supabase link --project-ref <staging-ref> && npx supabase db push   # then staging
npx supabase link --project-ref <prod-ref>    && npx supabase db push   # then production

npx supabase init && npx supabase start        # local, copy keys to .env.local
npx supabase migration new create_users        # author schema, then:
npx supabase db reset                           # verify locally
npx supabase link --project-ref "<staging-ref>" && npx supabase db push
npx supabase link --project-ref "<prod-ref>"    && npx supabase db push

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files (references) in skills/.curated/supabase-multi-env-setup of jeremylongshore/tons-of-skills-marketplace.

• SKILL.md
• references/configuration-structure.md
• references/errors.md
• references/examples.md
• references/implementation.md

Open the folder on GitHubat commit 80f86df