Official agent skill

Studio Testing

Testing strategy for Supabase Studio. An agent skill from supabase/supabase.

OfficialApache-2.0Auto-check passedTesting & QA

Install Studio Testing

skills CLI

$ npx skills add supabase/supabase --skill studio-testing -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install supabase/supabase studio-testing --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/supabase/supabase.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/studio-testing .claude/skills/studio-testing && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "studio-testing" agent skill from https://github.com/supabase/supabase/tree/master/.agents/skills/studio-testing into .claude/skills/studio-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "studio-testing", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/supabase/supabase/tree/master/.agents/skills/studio-testing

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add supabase/supabase --skill studio-testing -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install supabase/supabase studio-testing --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/supabase/supabase.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/studio-testing .agents/skills/studio-testing && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "studio-testing" agent skill from https://github.com/supabase/supabase/tree/master/.agents/skills/studio-testing into .agents/skills/studio-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "studio-testing", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add supabase/supabase --skill studio-testing -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install supabase/supabase studio-testing --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/supabase/supabase.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/studio-testing .cursor/skills/studio-testing && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "studio-testing" agent skill from https://github.com/supabase/supabase/tree/master/.agents/skills/studio-testing into .cursor/skills/studio-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "studio-testing", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/supabase/supabase.git --path .agents/skills/studio-testing

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add supabase/supabase --skill studio-testing -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install supabase/supabase studio-testing --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/supabase/supabase.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/studio-testing .gemini/skills/studio-testing && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "studio-testing" agent skill from https://github.com/supabase/supabase/tree/master/.agents/skills/studio-testing into .gemini/skills/studio-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "studio-testing", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install supabase/supabase studio-testing

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add supabase/supabase --skill studio-testing -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/supabase/supabase.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/studio-testing .github/skills/studio-testing && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "studio-testing" agent skill from https://github.com/supabase/supabase/tree/master/.agents/skills/studio-testing into .github/skills/studio-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "studio-testing", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add supabase/supabase --skill studio-testing -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install supabase/supabase studio-testing --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/supabase/supabase.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/studio-testing .opencode/skills/studio-testing && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "studio-testing" agent skill from https://github.com/supabase/supabase/tree/master/.agents/skills/studio-testing into .opencode/skills/studio-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "studio-testing", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: studio-testing
GitHub stars: 111k
Token cost: ~2.2k tokens
SKILL.md length: 505 words
Files: 1
Skills in repo: 22
Repo updated: Oct 8, 2026
First seen: Oct 8, 2026
Licence: Apache-2.0

At a glance

Testing strategy for Supabase Studio. An agent skill from supabase/supabase.

Works in 4 steps: Logic Extraction (CRITICAL) → Test Coverage (CRITICAL) → Component Tests (HIGH) → …
Deciding whether a change needs tests and which type
SKILL.md covers When to Apply, Rule Categories by Priority, Quick Reference and Decision Tree: Which Test Type?, plus 5 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Studio Testing is an agent skill from supabase/supabase, published by the product's own GitHub organization. Testing strategy for Supabase Studio. Use when writing tests, deciding whether a change needs tests and which type, extracting logic from components into testable utility functions, or reviewing test coverage. Covers unit tests, component tests, and E2E test selection criteria.

Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Testing & QA, covering End-to-end testing, Test coverage and Test strategy. It works with Supabase. The repository describes itself as: The Postgres development platform. Supabase gives you a dedicated Postgres database to build your web, mobile, and AI applications. The licence is Apache-2.0.

When your agent uses it

Deciding whether a change needs tests and which type
Extracting logic from components into testable utility functions
Reviewing test coverage

Example prompts

“/studio-testing”

Workflow steps

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

Logic Extraction (CRITICAL)
Test Coverage (CRITICAL)
Component Tests (HIGH)
E2E Tests (HIGH)

What it can do on your machine

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

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Studio Testing loads about 2.2k tokens when it runs. Until then it costs about 73 tokens; SKILL.md has 505 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~73
When it runs · the whole SKILL.md, loaded when a task matches: ~2.2k

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

Auto-check passed

The automated check found no risky patterns in SKILL.md.

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 supabase/supabase at commit 26c838a, republished under its Apache-2.0 licence (© supabase). 505 words, ~2,230 tokens.

Download SKILL.mdSave it as .claude/skills/studio-testing/SKILL.md (or your agent's skills folder).

name: studio-testing
description: Testing strategy for Supabase Studio. Use when writing tests, deciding whether a change needs tests and which type, extracting logic from components into testable utility functions, or reviewing test coverage. Covers unit tests, component tests, and E2E test selection criteria.

Studio Testing Strategy

How to write and structure tests for apps/studio/. The core principle: push logic out of React components into pure utility functions, then test those functions exhaustively. Only use component tests for complex UI interactions. Use E2E tests for features shared between self-hosted and platform.

When to Apply

Reference these guidelines when:

Writing new tests for Studio code
Deciding which type of test to write (unit, component, E2E)
Extracting logic from a component to make it testable
Reviewing whether test coverage is sufficient
Adding a new feature that needs tests

Rule Categories by Priority

Priority	Category	Impact	Prefix
1	Logic Extraction	CRITICAL	`testing-`
2	Test Coverage	CRITICAL	`testing-`
3	Component Tests	HIGH	`testing-`
4	E2E Tests	HIGH	`testing-`

Quick Reference

1. Logic Extraction (CRITICAL)

testing-extract-logic - Remove logic from components into .utils.ts files as pure functions: args in, return out

2. Test Coverage (CRITICAL)

testing-exhaustive-permutations - Test every permutation of utility functions: happy path, malformed input, empty values, edge cases

3. Component Tests (HIGH)

testing-component-tests-ui-only - Only write component tests for complex UI interaction logic, not business logic

4. E2E Tests (HIGH)

testing-e2e-shared-features - Write E2E tests for features used in both self-hosted and platform; cover clicks AND keyboard shortcuts

Decision Tree: Which Test Type?

Is the logic a pure transformation (parse, format, validate, compute)?
  YES -> Extract to .utils.ts, write unit test with vitest
  NO  -> Does the feature involve complex UI interactions?
           YES -> Is it used in both self-hosted and platform?
                    YES -> Write E2E test in e2e/studio/features/
                    NO  -> Write component test with customRender
           NO  -> Can you extract the logic to make it pure?
                    YES -> Do that, then unit test it
                    NO  -> Write a component test

1. Extract Logic Into Utility Files (CRITICAL)

Remove as much logic from components as possible. Put it in co-located .utils.ts files as pure functions: arguments in, return value out.

File naming:

Utility: ComponentName.utils.ts next to the component
Test: tests/components/.../ComponentName.utils.test.ts mirroring the source path

tsx

// ❌ Logic buried in component — hard to test without rendering
function TaxIdForm({ taxIdValue, taxIdName }: Props) {
  const handleSubmit = () => {
    const taxId = TAX_IDS.find((t) => t.name === taxIdName)
    let sanitized = taxIdValue
    if (taxId?.vatPrefix && !taxIdValue.startsWith(taxId.vatPrefix)) {
      sanitized = taxId.vatPrefix + taxIdValue
    }
    submitToApi(sanitized)
  }
  return <form onSubmit={handleSubmit}>...</form>
}

// ✅ Logic extracted to .utils.ts — trivially testable
// TaxID.utils.ts
export function sanitizeTaxIdValue({ value, name }: { value: string; name: string }): string {
  const taxId = TAX_IDS.find((t) => t.name === name)
  if (taxId?.vatPrefix && !value.startsWith(taxId.vatPrefix)) {
    return taxId.vatPrefix + value
  }
  return value
}

// TaxIdForm.tsx — thin shell
const handleSubmit = () => {
  const sanitized = sanitizeTaxIdValue({ value: taxIdValue, name: taxIdName })
  submitToApi(sanitized)
}

2. Test Every Permutation (CRITICAL)

Once logic is extracted, test exhaustively. Every code path needs a test:

Valid inputs (happy path for each branch)
Invalid / malformed inputs
Empty values, null values, missing fields
Edge cases (timestamps with colons, special characters, boundary values)

// ❌ Only happy path
test('parses a filter', () => {
  expect(formatFilterURLParams('id:gte:20')).toStrictEqual({ column: 'id', operator: 'gte', value: '20' })
})

// ✅ Every permutation
test('parses valid filter', () => { ... })
test('handles timestamp with colons in value', () => { ... })
test('rejects malformed filter with missing parts', () => { ... })
test('rejects unrecognized operator', () => { ... })
test('allows empty filter value', () => { ... })

Show full SKILL.md (217 more words)Show less

3. Component Tests for Complex UI Only (HIGH)

Only write component tests when there is complex UI interaction logic that cannot be captured by testing utility functions alone.

Valid reasons: conditional rendering from user interaction sequences, popover open/close with keyboard/mouse, multi-step form transitions.

Not valid: testing a calculation or transformation that happens to live in a component — extract to .utils.ts and unit test instead.

Studio component test conventions:

tsx

import { screen } from '@testing-library/react'
import { platformComponents as components } from 'api-types'
import { HttpResponse } from 'msw'

import { customRender } from '@/tests/lib/custom-render'
import { addAPIMock } from '@/tests/lib/msw'

type OrganizationResponse = components['schemas']['OrganizationResponse']

addAPIMock({
  method: 'get',
  path: '/platform/organizations',
  response: () => HttpResponse.json<OrganizationResponse[]>([]),
})
customRender(<MyComponent />)
expect(await screen.findByText('No organizations')).toBeInTheDocument()

Mock API requests at the network layer with addAPIMock (MSW) — unhandled requests fail the test. Don't vi.mock('@/data/...'). Always pass the OpenAPI body type to HttpResponse.json<…>.
customRender wraps the component in the providers Studio needs (React Query, router, etc.).
The full template, path-param syntax, and the jsdom/MSW gotchas are in the studio-mock-api-tests skill.

4. E2E Tests for Shared Features (HIGH)

If a feature exists in both self-hosted and platform, create an E2E test. Cover mouse clicks AND keyboard shortcuts (Tab, Enter, Escape, Arrow keys).

Extract reusable interactions into e2e/studio/utils/*-helpers.ts. Use try/finally for resource cleanup. For E2E execution details, see the studio-e2e-tests skill.

Codebase References

What	Where
Util test examples	`apps/studio/tests/components/Grid/Grid.utils.test.ts`, `apps/studio/tests/components/Billing/TaxID.utils.test.ts`, `apps/studio/tests/components/Editor/SpreadsheetImport.utils.test.ts`
Component test examples	`apps/studio/tests/features/logs/LogsFilterPopover.test.tsx`, `apps/studio/tests/components/CopyButton.test.tsx`
E2E test example	`e2e/studio/features/filter-bar.spec.ts`
E2E helpers pattern	`e2e/studio/utils/filter-bar-helpers.ts`
Custom render	`apps/studio/tests/lib/custom-render.tsx`
MSW mock setup	`apps/studio/tests/lib/msw.ts` (`addAPIMock`)
Test README	`apps/studio/tests/README.md`
Vitest config	`apps/studio/vitest.config.ts`
Related skills	`studio-e2e-tests` (running E2E), `vitest` (API reference), `vercel-composition-patterns` (component architecture)

Files

Just SKILL.md in .agents/skills/studio-testing of supabase/supabase.

Open the folder on GitHubat commit 26c838a

Compare with similar skills

Studio Testing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Studio Testing compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Studio Testing this skillsupabase/supabase	111k	—	~2.2k	Automated safety check: Pass	Apache-2.0	today
Dotnet Testingnovotnyllc/dotnet-artisan	233	—	~972	Automated safety check: Pass	MIT	today
Senior QAalirezarezvani/claude-skills	28k	1 repos	~2.1k	Automated safety check: Pass	MIT	1 mo ago
Senior QAnicepkg/auto-company	192	3 repos	~1.1k	Automated safety check: Notes	None	7 mo ago
Designing TestsCloudAI-X/claude-workflow-v2	1.4k	1 repos	~1.5k	Automated safety check: Pass	MIT	yesterday
Test Pyramidkubernetes-sigs/agent-sandbox	4.2k	—	~1.6k	Automated safety check: Pass	Apache-2.0	today

Similar skills

Dotnet Testing
novotnyllc/dotnet-artisan
Defines .NET test strategy and implementation patterns across xUnit v3 (Facts, Theories, fixtures, IAsyncLifetime), integration testing (WebApplicationFactory, Testcontainers), Aspire testing…
233 GitHub stars~972 tokensUpdated today
Testing & QAAuto-check passed
Senior QA
alirezarezvani/claude-skills
Generates unit tests, integration tests, and E2E tests for React/Next.js applications.
28k GitHub starsUsed in 1 repo~2.1k tokens
Testing & QAAuto-check passed
Senior QA
nicepkg/auto-company
Comprehensive QA and testing skill for quality assurance, test automation, and testing strategies for ReactJS, NextJS, NodeJS applications.
192 GitHub starsUsed in 3 repos~1.1k tokens
Testing & QAAuto-check: notes
Designing Tests
CloudAI-X/claude-workflow-v2
Designs and implements testing strategies for any codebase. An agent skill from CloudAI-X/claude-workflow-v2.
1.4k GitHub starsUsed in 1 repo~1.5k tokens
Testing & QAAuto-check passed
Test Pyramid
kubernetes-sigs/agent-sandbox
Official
Analyze the repo's unit and E2E tests and propose rebalancing toward a test pyramid — which E2E tests (or assertions inside them) can be covered by unit tests, which unit-level gaps genuinely need…
4.2k GitHub stars~1.6k tokensUpdated today
Testing & QAAuto-check passed
Atdd Mutate
swingerman/engineer
A skill your agent uses to add a third validation layer to the ATDD workflow — after acceptance tests verify WHAT and unit tests verify HOW, mutation testing verifies the tests actually catch bugs.
154 GitHub stars~2.7k tokensUpdated 15 days ago
Testing & QAAuto-check passed

More from supabase/supabase

All 22 skills in this repo

Vercel Composition Patterns
supabase/supabase
Official
React composition patterns that scale. An agent skill from supabase/supabase.
111k GitHub starsUsed in 59 repos~726 tokens
Auto-check passed
Clickhouse Logs Queries
supabase/supabase
Official
Write, review, and migrate Supabase logs queries against the ClickHouse-backed logs table (the logs.all.otel analytics endpoint).
111k GitHub stars~2.4k tokensUpdated today
Auto-check passed
Review The Docs
supabase/supabase
Official
Review Supabase docs changes locally in your supabase/supabase checkout — either an open PR (triage, classify, verify) or your own branch before opening a PR (local self-review).
111k GitHub stars~4.6k tokensUpdated today
Auto-check passed
Vitest
supabase/supabase
Official
Vitest API and config reference (Jest-compatible) — mocking with vi., spies, fake timers, coverage configuration, fixtures, snapshots, and test filtering.
111k GitHub starsUsed in 12 repos~1.1k tokens
Auto-check passed
Safe SQL Execution
supabase/supabase
Official
A skill your agent uses whenever code will build, return, fetch, or execute SQL that runs against a user's real Postgres database — even when the request reads like an ordinary feature or bug fix…
111k GitHub stars~4.2k tokensUpdated today
Auto-check passed
Studio E2E Tests
supabase/supabase
Official
Write and run Playwright E2E tests for Supabase Studio (e2e/studio).
111k GitHub stars~2.8k tokensUpdated today
Auto-check passed

Works with

Supabase

Questions about Studio Testing

What does Studio Testing do?

Testing strategy for Supabase Studio. An agent skill from supabase/supabase. Studio Testing is an agent skill from supabase/supabase, published by the product's own GitHub organization. Testing strategy for Supabase Studio.

When should I use Studio Testing?

Studio Testing fits situations like: deciding whether a change needs tests and which type; extracting logic from components into testable utility functions; reviewing test coverage.

How do I install Studio Testing in Claude Code?

Run `npx skills add supabase/supabase --skill studio-testing -a claude-code`. Or copy the skill folder (.agents/skills/studio-testing in supabase/supabase) into .claude/skills/studio-testing in your project. Claude Code loads it when a task matches its description.

How do I install Studio Testing in Codex?

Run `npx skills add supabase/supabase --skill studio-testing -a codex`. Or copy the skill folder (.agents/skills/studio-testing in supabase/supabase) into .agents/skills/studio-testing in your project. Codex loads it when a task matches its description.

Can I use Studio Testing in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add supabase/supabase --skill studio-testing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/studio-testing, .gemini/skills/studio-testing, .github/skills/studio-testing and .opencode/skills/studio-testing in your project.

What does Studio Testing need to run?

SKILL.md names no scripts, command-line tools or credentials: Studio Testing is instructions for the agent only.

Does Studio Testing access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Studio Testing safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Studio Testing use?

Studio Testing is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Studio Testing use?

About 2.2k tokens (SKILL.md is roughly 8.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Studio Testing?

Skills that share tags, products or a category with Studio Testing: Dotnet Testing (novotnyllc/dotnet-artisan, 233 stars), Senior QA (alirezarezvani/claude-skills, 28k stars), Senior QA (nicepkg/auto-company, 192 stars) and Designing Tests (CloudAI-X/claude-workflow-v2, 1.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Studio Testing?

supabase (a GitHub organization, an official publisher) maintains it in supabase/supabase, which has 111,222 GitHub stars. The repository holds 22 skills in this directory. The repository was last updated on October 8, 2026.

Source: supabase/supabase on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Studio Testing

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Studio Testing Strategy

When to Apply

Rule Categories by Priority

Quick Reference

1. Logic Extraction (CRITICAL)

2. Test Coverage (CRITICAL)

3. Component Tests (HIGH)

4. E2E Tests (HIGH)

Decision Tree: Which Test Type?

1. Extract Logic Into Utility Files (CRITICAL)

2. Test Every Permutation (CRITICAL)

3. Component Tests for Complex UI Only (HIGH)

4. E2E Tests for Shared Features (HIGH)

Codebase References

Files

Compare with similar skills

Similar skills

More from supabase/supabase

Related

Questions about Studio Testing