supabase-postgres-style-guide

A set of rules for writing PostgreSQL database queries and definitions, covering naming, formatting, dates, schemas, tables, columns, and comments.

In plain words
What is it for?
Creating or reviewing PostgreSQL tables and queries with consistent lowercase keywords, snake_case names, public schemas, identity IDs, and documented database objects.
Why use it?
It reduces inconsistent SQL and makes database structures and queries easier to read and maintain.

Cursor rule

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add rules/squirrelogic/cursor-rules/supabase-postgres-style-guide
Clone the repo
git clone --depth 1 https://github.com/squirrelogic/cursor-rules
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 826 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 91% copy Near-identical to another mod in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00826
Opus 5 $0.00000 $0.00413
Sonnet 5 $0.00000 $0.00165
Haiku 4.5 $0.00000 $0.00083

Measured 2d ago against content hash 3fe60c177d6d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

supabase-postgres-style-guide scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

91% identical to guidelines-for-writing-postgres-sql-by-supabase — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

supabase/supabase-postgres-style-guide.mdc · 149 lines

How it starts

The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Postgres SQL Style Guide

General

  • Use lowercase for SQL reserved words to maintain consistency and readability.
  • Employ consistent, descriptive identifiers for tables, columns, and other database objects.
  • Use white space and indentation to enhance the readability of your code.
  • Store dates in ISO 8601 format (yyyy-mm-ddThh:mm:ss.sssss).
  • Include comments for complex logic, using '/* ... */' for block comments and '--' for line comments.

Naming Conventions

  • Avoid SQL reserved words and ensure names are unique and under 63 characters.
  • Use snake_case for tables and columns.
  • Prefer plurals for table names
  • Prefer singular names for columns.

Tables

  • Avoid prefixes like 'tbl_' and ensure no table name matches any of its column names.
  • Always add an id column of type identity generated always unless otherwise specified.
  • Create all tables in the public schema unless otherwise specified.
  • Always add the schema to SQL queries for clarity.
  • Always add a comment to describe what the table does. The comment can be up to 1024 characters.

Columns

  • Use singular names and avoid generic names like 'id'.
  • For references to foreign tables, use the singular of the table name with the _id suffix. For example user_id to reference the users table
  • Always use lowercase except in cases involving acronyms or when readability would be enhanced by an exception.
Examples:
create table books (
  id bigint generated always as identity primary key,
  title text not null,
  author_id bigint references authors (id)
);
comment on table books is 'A list of all the books in the library.';

Queries

  • When the query is shorter keep it on just a few lines. As it gets larger start adding newlines for readability
  • Add spaces for readability.

Smaller queries:

select *
from employees
where end_date is null;

update employees
set end_date = '2023-12-31'
where employee_id = 1001;

Larger queries:

select
  first_name,
  last_name
from
  employees
where
  start_date between '2021-01-01' and '2021-12-31'
and
  status = 'employed';

Read the full file on GitHub · 149 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 149 lines · 826 tokens per session scan A 3fe60c177d6d

Subscribe to this mod's changes

supabase-postgres-style-guide is a cursor rule published in the GitHub repository squirrelogic/cursor-rules (20 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 826 tokens. A static security scan graded it A with 0 findings. It is 91% identical to guidelines-for-writing-postgres-sql-by-supabase, differing in 6 lines, and is treated as a copy.