supabase-ops
Skill0 starsChanged 2 months agoMITView on GitHub
Use when the user works on Supabase Auth, RLS, Postgres schema/migrations, Edge Functions, Storage, Realtime, supabase-js, or @supabase/ssr. Not for visual UI, not for MongoDB, not for Vercel deploy-only.
- Reads credentials
1 other project uses a version of this.
Adopted by
Most recently taken up by
- ImpactMojo/ImpactMojotheir own version, first seen Apr 12, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- ImpactMojo/ImpactMojo★ 3same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository47 other files it gives its agents.
- templates/AGENTS.mdAGENTS.md
- academicSkill
- adhdSkill
- agent-architecture-auditSkill
- api-designSkill
- automation-audit-opsSkill
- browser-actSkill
- chrome-devtools-axiSkill
- click-path-auditSkill
- codebase-designSkill
- code-tourSkill
- contract-firstSkill
- cost-aware-llm-pipelineSkill
- diagnosing-bugsSkill
- diagram-designSkill
- domain-modelingSkill
- emil-design-engSkill
- eval-harnessSkill
- found-this-designSkill
- full-audit-keamananSkill
- full-performance-auditSkill
- gh-axiSkill
- grill-with-docsSkill
- humanizerSkill
- hyperframesSkill
- id-demo-videoSkill
- img2threejsSkill
- impeccableSkill
- install-anti-slopSkill
- markitdownSkill
- matt-code-reviewSkill
- mongodb-opsSkill
- playwright-qaSkill
- prompt-optimizerSkill
- prototypeSkill
- researchSkill
- scroll-craftSkill
- scroll-worldSkill
- skill-stocktakeSkill
- smartbook-ingestSkill
- smartdocSkill
- tddSkill
- to-specSkill
- to-ticketsSkill
- vercel-opsSkill
- visual-studioSkill
- writing-for-agentsSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 2 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 25
NO UI generation: Do not generate or style user interfaces, login forms, or dashboards.
- Distinctive: line 26
NO Design Bank access: Do not search, crawl, or import Design Bank catalogs.
- Very specific: line 27
NO secret exposure: Never print service_role keys, database connection strings containing passwords, or JWTs.
- Very specific: line 33
Check package.json for installed Supabase packages (@supabase/supabase-js, @supabase/ssr).
- Distinctive: line 34
Never invent database tables or schemas out of thin air when migration files or existing models exist.
- Very specific: line 38
Ensure Row Level Security (ALTER TABLE ...
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Supabase Ops
First-party operational and contract specialist for Supabase. Handles database schemas, migrations, Row Level Security (RLS) policies, Auth contracts, Edge Functions, Storage, Realtime, and client SDK integration (@supabase/supabase-js, @supabase/ssr).
Boundaries & Handoffs
| Need | Route |
| Visual UI, login forms, styling, page layout | found-this-design → impeccable (Design Bank) |
| Defensive audit of Auth / RLS policies / public table exposure | full-audit-keamanan (risk XOR, do not load concurrently) |
| MongoDB schemas, indexing, aggregation | mongodb-ops |
| Vercel deployment and hosting configuration | vercel-ops |
| Official Supabase API and library syntax | Context7 (@supabase/supabase-js, @supabase/ssr) |
| Supabase schema, migrations, RLS, Auth contracts, Edge Functions | supabase-ops |
Explicit Non-Goals & Safety
- NO UI generation: Do not generate or style user interfaces, login forms, or dashboards. UI belongs strictly to
impeccable. Vendor stack ≠ UI. - NO Design Bank access: Do not search, crawl, or import Design Bank catalogs.
- NO secret exposure: Never print
service_rolekeys, database connection strings containing passwords, or JWTs. Reference secret names only (e.g. in.env.example).
Procedure
- Repo Evidence First:
- Inspect existing SQL schemas,
supabase/migrations/,supabase/config.toml, and.env.example(without secrets). - Check
package.jsonfor installed Supabase packages (@supabase/supabase-js,@supabase/ssr). - Never invent database tables or schemas out of thin air when migration files or existing models exist.
- Inspect existing SQL schemas,
- Official Documentation via Context7:
- Fetch verified API contracts from Context7 for
@supabase/supabase-jsor@supabase/ssr. Do not guess API methods.
- Fetch verified API contracts from Context7 for
- RLS & Security Enforcement:
- Ensure Row Level Security (
ALTER TABLE ... ENABLE ROW LEVEL SECURITY;) is enabled on all tables exposed to the client. - Specify explicit policies for
SELECT,INSERT,UPDATE, andDELETE. For sensitive public APIs or security audits, recommendfull-audit-keamananas risk specialist.
- Ensure Row Level Security (
- Auth & Backend Contracts:
- Configure SSR cookie exchange patterns and server client wrappers.
- Login and onboarding UI pages remain with
impeccable; this skill delivers backend route handlers, server actions, and schema policies.
Finish Gate
- State all modified files (e.g. migrations, client factories, route handlers).
- Execute project verification commands (
npm test,pytest) or reportNOT_CONFIGUREDif none exist.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.