@oriro/orirocli 0.1.9 → 0.1.11

package/skills/craft/supabase-postgres-best-practices/references/schema-foreign-key-indexes.md

@@ -1,59 +1,59 @@
----
-title: Index Foreign Key Columns
-impact: HIGH
-impactDescription: 10-100x faster JOINs and CASCADE operations
-tags: foreign-key, indexes, joins, schema
----
-
-## Index Foreign Key Columns
-
-Postgres does not automatically index foreign key columns. Missing indexes cause slow JOINs and CASCADE operations.
-
-**Incorrect (unindexed foreign key):**
-
-```sql
-create table orders (
-  id bigint generated always as identity primary key,
-  customer_id bigint references customers(id) on delete cascade,
-  total numeric(10,2)
-);
-
--- No index on customer_id!
--- JOINs and ON DELETE CASCADE both require full table scan
-select * from orders where customer_id = 123;  -- Seq Scan
-delete from customers where id = 123;          -- Locks table, scans all orders
-```
-
-**Correct (indexed foreign key):**
-
-```sql
-create table orders (
-  id bigint generated always as identity primary key,
-  customer_id bigint references customers(id) on delete cascade,
-  total numeric(10,2)
-);
-
--- Always index the FK column
-create index orders_customer_id_idx on orders (customer_id);
-
--- Now JOINs and cascades are fast
-select * from orders where customer_id = 123;  -- Index Scan
-delete from customers where id = 123;          -- Uses index, fast cascade
-```
-
-Find missing FK indexes:
-
-```sql
-select
-  conrelid::regclass as table_name,
-  a.attname as fk_column
-from pg_constraint c
-join pg_attribute a on a.attrelid = c.conrelid and a.attnum = any(c.conkey)
-where c.contype = 'f'
-  and not exists (
-    select 1 from pg_index i
-    where i.indrelid = c.conrelid and a.attnum = any(i.indkey)
-  );
-```
-
-Reference: [Foreign Keys](https://www.postgresql.org/docs/current/ddl-constraints.html#DDL-CONSTRAINTS-FK)
+---
+title: Index Foreign Key Columns
+impact: HIGH
+impactDescription: 10-100x faster JOINs and CASCADE operations
+tags: foreign-key, indexes, joins, schema
+---
+
+## Index Foreign Key Columns
+
+Postgres does not automatically index foreign key columns. Missing indexes cause slow JOINs and CASCADE operations.
+
+**Incorrect (unindexed foreign key):**
+
+```sql
+create table orders (
+  id bigint generated always as identity primary key,
+  customer_id bigint references customers(id) on delete cascade,
+  total numeric(10,2)
+);
+
+-- No index on customer_id!
+-- JOINs and ON DELETE CASCADE both require full table scan
+select * from orders where customer_id = 123;  -- Seq Scan
+delete from customers where id = 123;          -- Locks table, scans all orders
+```
+
+**Correct (indexed foreign key):**
+
+```sql
+create table orders (
+  id bigint generated always as identity primary key,
+  customer_id bigint references customers(id) on delete cascade,
+  total numeric(10,2)
+);
+
+-- Always index the FK column
+create index orders_customer_id_idx on orders (customer_id);
+
+-- Now JOINs and cascades are fast
+select * from orders where customer_id = 123;  -- Index Scan
+delete from customers where id = 123;          -- Uses index, fast cascade
+```
+
+Find missing FK indexes:
+
+```sql
+select
+  conrelid::regclass as table_name,
+  a.attname as fk_column
+from pg_constraint c
+join pg_attribute a on a.attrelid = c.conrelid and a.attnum = any(c.conkey)
+where c.contype = 'f'
+  and not exists (
+    select 1 from pg_index i
+    where i.indrelid = c.conrelid and a.attnum = any(i.indkey)
+  );
+```
+
+Reference: [Foreign Keys](https://www.postgresql.org/docs/current/ddl-constraints.html#DDL-CONSTRAINTS-FK)

package/skills/craft/supabase-postgres-best-practices/references/schema-lowercase-identifiers.md

@@ -1,55 +1,55 @@
----
-title: Use Lowercase Identifiers for Compatibility
-impact: MEDIUM
-impactDescription: Avoid case-sensitivity bugs with tools, ORMs, and AI assistants
-tags: naming, identifiers, case-sensitivity, schema, conventions
----
-
-## Use Lowercase Identifiers for Compatibility
-
-PostgreSQL folds unquoted identifiers to lowercase. Quoted mixed-case identifiers require quotes forever and cause issues with tools, ORMs, and AI assistants that may not recognize them.
-
-**Incorrect (mixed-case identifiers):**
-
-```sql
--- Quoted identifiers preserve case but require quotes everywhere
-CREATE TABLE "Users" (
-  "userId" bigint PRIMARY KEY,
-  "firstName" text,
-  "lastName" text
-);
-
--- Must always quote or queries fail
-SELECT "firstName" FROM "Users" WHERE "userId" = 1;
-
--- This fails - Users becomes users without quotes
-SELECT firstName FROM Users;
--- ERROR: relation "users" does not exist
-```
-
-**Correct (lowercase snake_case):**
-
-```sql
--- Unquoted lowercase identifiers are portable and tool-friendly
-CREATE TABLE users (
-  user_id bigint PRIMARY KEY,
-  first_name text,
-  last_name text
-);
-
--- Works without quotes, recognized by all tools
-SELECT first_name FROM users WHERE user_id = 1;
-```
-
-Common sources of mixed-case identifiers:
-
-```sql
--- ORMs often generate quoted camelCase - configure them to use snake_case
--- Migrations from other databases may preserve original casing
--- Some GUI tools quote identifiers by default - disable this
-
--- If stuck with mixed-case, create views as a compatibility layer
-CREATE VIEW users AS SELECT "userId" AS user_id, "firstName" AS first_name FROM "Users";
-```
-
-Reference: [Identifiers and Key Words](https://www.postgresql.org/docs/current/sql-syntax-lexical.html#SQL-SYNTAX-IDENTIFIERS)
+---
+title: Use Lowercase Identifiers for Compatibility
+impact: MEDIUM
+impactDescription: Avoid case-sensitivity bugs with tools, ORMs, and AI assistants
+tags: naming, identifiers, case-sensitivity, schema, conventions
+---
+
+## Use Lowercase Identifiers for Compatibility
+
+PostgreSQL folds unquoted identifiers to lowercase. Quoted mixed-case identifiers require quotes forever and cause issues with tools, ORMs, and AI assistants that may not recognize them.
+
+**Incorrect (mixed-case identifiers):**
+
+```sql
+-- Quoted identifiers preserve case but require quotes everywhere
+CREATE TABLE "Users" (
+  "userId" bigint PRIMARY KEY,
+  "firstName" text,
+  "lastName" text
+);
+
+-- Must always quote or queries fail
+SELECT "firstName" FROM "Users" WHERE "userId" = 1;
+
+-- This fails - Users becomes users without quotes
+SELECT firstName FROM Users;
+-- ERROR: relation "users" does not exist
+```
+
+**Correct (lowercase snake_case):**
+
+```sql
+-- Unquoted lowercase identifiers are portable and tool-friendly
+CREATE TABLE users (
+  user_id bigint PRIMARY KEY,
+  first_name text,
+  last_name text
+);
+
+-- Works without quotes, recognized by all tools
+SELECT first_name FROM users WHERE user_id = 1;
+```
+
+Common sources of mixed-case identifiers:
+
+```sql
+-- ORMs often generate quoted camelCase - configure them to use snake_case
+-- Migrations from other databases may preserve original casing
+-- Some GUI tools quote identifiers by default - disable this
+
+-- If stuck with mixed-case, create views as a compatibility layer
+CREATE VIEW users AS SELECT "userId" AS user_id, "firstName" AS first_name FROM "Users";
+```
+
+Reference: [Identifiers and Key Words](https://www.postgresql.org/docs/current/sql-syntax-lexical.html#SQL-SYNTAX-IDENTIFIERS)

package/skills/craft/supabase-postgres-best-practices/references/schema-partitioning.md

@@ -1,55 +1,55 @@
----
-title: Partition Large Tables for Better Performance
-impact: MEDIUM-HIGH
-impactDescription: 5-20x faster queries and maintenance on large tables
-tags: partitioning, large-tables, time-series, performance
----
-
-## Partition Large Tables for Better Performance
-
-Partitioning splits a large table into smaller pieces, improving query performance and maintenance operations.
-
-**Incorrect (single large table):**
-
-```sql
-create table events (
-  id bigint generated always as identity,
-  created_at timestamptz,
-  data jsonb
-);
-
--- 500M rows, queries scan everything
-select * from events where created_at > '2024-01-01';  -- Slow
-vacuum events;  -- Takes hours, locks table
-```
-
-**Correct (partitioned by time range):**
-
-```sql
-create table events (
-  id bigint generated always as identity,
-  created_at timestamptz not null,
-  data jsonb
-) partition by range (created_at);
-
--- Create partitions for each month
-create table events_2024_01 partition of events
-  for values from ('2024-01-01') to ('2024-02-01');
-
-create table events_2024_02 partition of events
-  for values from ('2024-02-01') to ('2024-03-01');
-
--- Queries only scan relevant partitions
-select * from events where created_at > '2024-01-15';  -- Only scans events_2024_01+
-
--- Drop old data instantly
-drop table events_2023_01;  -- Instant vs DELETE taking hours
-```
-
-When to partition:
-
-- Tables > 100M rows
-- Time-series data with date-based queries
-- Need to efficiently drop old data
-
-Reference: [Table Partitioning](https://www.postgresql.org/docs/current/ddl-partitioning.html)
+---
+title: Partition Large Tables for Better Performance
+impact: MEDIUM-HIGH
+impactDescription: 5-20x faster queries and maintenance on large tables
+tags: partitioning, large-tables, time-series, performance
+---
+
+## Partition Large Tables for Better Performance
+
+Partitioning splits a large table into smaller pieces, improving query performance and maintenance operations.
+
+**Incorrect (single large table):**
+
+```sql
+create table events (
+  id bigint generated always as identity,
+  created_at timestamptz,
+  data jsonb
+);
+
+-- 500M rows, queries scan everything
+select * from events where created_at > '2024-01-01';  -- Slow
+vacuum events;  -- Takes hours, locks table
+```
+
+**Correct (partitioned by time range):**
+
+```sql
+create table events (
+  id bigint generated always as identity,
+  created_at timestamptz not null,
+  data jsonb
+) partition by range (created_at);
+
+-- Create partitions for each month
+create table events_2024_01 partition of events
+  for values from ('2024-01-01') to ('2024-02-01');
+
+create table events_2024_02 partition of events
+  for values from ('2024-02-01') to ('2024-03-01');
+
+-- Queries only scan relevant partitions
+select * from events where created_at > '2024-01-15';  -- Only scans events_2024_01+
+
+-- Drop old data instantly
+drop table events_2023_01;  -- Instant vs DELETE taking hours
+```
+
+When to partition:
+
+- Tables > 100M rows
+- Time-series data with date-based queries
+- Need to efficiently drop old data
+
+Reference: [Table Partitioning](https://www.postgresql.org/docs/current/ddl-partitioning.html)

package/skills/craft/supabase-postgres-best-practices/references/schema-primary-keys.md

@@ -1,61 +1,61 @@
----
-title: Select Optimal Primary Key Strategy
-impact: HIGH
-impactDescription: Better index locality, reduced fragmentation
-tags: primary-key, identity, uuid, serial, schema
----
-
-## Select Optimal Primary Key Strategy
-
-Primary key choice affects insert performance, index size, and replication
-efficiency.
-
-**Incorrect (problematic PK choices):**
-
-```sql
--- identity is the SQL-standard approach
-create table users (
-  id serial primary key  -- Works, but IDENTITY is recommended
-);
-
--- Random UUIDs (v4) cause index fragmentation
-create table orders (
-  id uuid default gen_random_uuid() primary key  -- UUIDv4 = random = scattered inserts
-);
-```
-
-**Correct (optimal PK strategies):**
-
-```sql
--- Use IDENTITY for sequential IDs (SQL-standard, best for most cases)
-create table users (
-  id bigint generated always as identity primary key
-);
-
--- For distributed systems needing UUIDs, use UUIDv7 (time-ordered)
--- Requires pg_uuidv7 extension: create extension pg_uuidv7;
-create table orders (
-  id uuid default uuid_generate_v7() primary key  -- Time-ordered, no fragmentation
-);
-
--- Alternative: time-prefixed IDs for sortable, distributed IDs (no extension needed)
-create table events (
-  id text default concat(
-    to_char(now() at time zone 'utc', 'YYYYMMDDHH24MISSMS'),
-    gen_random_uuid()::text
-  ) primary key
-);
-```
-
-Guidelines:
-
-- Single database: `bigint identity` (sequential, 8 bytes, SQL-standard)
-- Distributed/exposed IDs: UUIDv7 (requires pg_uuidv7) or ULID (time-ordered, no
-  fragmentation)
-- `serial` works but `identity` is SQL-standard and preferred for new
-  applications
-- Avoid random UUIDs (v4) as primary keys on large tables (causes index
-  fragmentation)
-
-Reference:
-[Identity Columns](https://www.postgresql.org/docs/current/sql-createtable.html#SQL-CREATETABLE-PARMS-GENERATED-IDENTITY)
+---
+title: Select Optimal Primary Key Strategy
+impact: HIGH
+impactDescription: Better index locality, reduced fragmentation
+tags: primary-key, identity, uuid, serial, schema
+---
+
+## Select Optimal Primary Key Strategy
+
+Primary key choice affects insert performance, index size, and replication
+efficiency.
+
+**Incorrect (problematic PK choices):**
+
+```sql
+-- identity is the SQL-standard approach
+create table users (
+  id serial primary key  -- Works, but IDENTITY is recommended
+);
+
+-- Random UUIDs (v4) cause index fragmentation
+create table orders (
+  id uuid default gen_random_uuid() primary key  -- UUIDv4 = random = scattered inserts
+);
+```
+
+**Correct (optimal PK strategies):**
+
+```sql
+-- Use IDENTITY for sequential IDs (SQL-standard, best for most cases)
+create table users (
+  id bigint generated always as identity primary key
+);
+
+-- For distributed systems needing UUIDs, use UUIDv7 (time-ordered)
+-- Requires pg_uuidv7 extension: create extension pg_uuidv7;
+create table orders (
+  id uuid default uuid_generate_v7() primary key  -- Time-ordered, no fragmentation
+);
+
+-- Alternative: time-prefixed IDs for sortable, distributed IDs (no extension needed)
+create table events (
+  id text default concat(
+    to_char(now() at time zone 'utc', 'YYYYMMDDHH24MISSMS'),
+    gen_random_uuid()::text
+  ) primary key
+);
+```
+
+Guidelines:
+
+- Single database: `bigint identity` (sequential, 8 bytes, SQL-standard)
+- Distributed/exposed IDs: UUIDv7 (requires pg_uuidv7) or ULID (time-ordered, no
+  fragmentation)
+- `serial` works but `identity` is SQL-standard and preferred for new
+  applications
+- Avoid random UUIDs (v4) as primary keys on large tables (causes index
+  fragmentation)
+
+Reference:
+[Identity Columns](https://www.postgresql.org/docs/current/sql-createtable.html#SQL-CREATETABLE-PARMS-GENERATED-IDENTITY)

package/skills/craft/supabase-postgres-best-practices/references/security-privileges.md

@@ -1,54 +1,54 @@
----
-title: Apply Principle of Least Privilege
-impact: MEDIUM
-impactDescription: Reduced attack surface, better audit trail
-tags: privileges, security, roles, permissions
----
-
-## Apply Principle of Least Privilege
-
-Grant only the minimum permissions required. Never use superuser for application queries.
-
-**Incorrect (overly broad permissions):**
-
-```sql
--- Application uses superuser connection
--- Or grants ALL to application role
-grant all privileges on all tables in schema public to app_user;
-grant all privileges on all sequences in schema public to app_user;
-
--- Any SQL injection becomes catastrophic
--- drop table users; cascades to everything
-```
-
-**Correct (minimal, specific grants):**
-
-```sql
--- Create role with no default privileges
-create role app_readonly nologin;
-
--- Grant only SELECT on specific tables
-grant usage on schema public to app_readonly;
-grant select on public.products, public.categories to app_readonly;
-
--- Create role for writes with limited scope
-create role app_writer nologin;
-grant usage on schema public to app_writer;
-grant select, insert, update on public.orders to app_writer;
-grant usage on sequence orders_id_seq to app_writer;
--- No DELETE permission
-
--- Login role inherits from these
-create role app_user login password 'xxx';
-grant app_writer to app_user;
-```
-
-Revoke public defaults:
-
-```sql
--- Revoke default public access
-revoke all on schema public from public;
-revoke all on all tables in schema public from public;
-```
-
-Reference: [Roles and Privileges](https://supabase.com/blog/postgres-roles-and-privileges)
+---
+title: Apply Principle of Least Privilege
+impact: MEDIUM
+impactDescription: Reduced attack surface, better audit trail
+tags: privileges, security, roles, permissions
+---
+
+## Apply Principle of Least Privilege
+
+Grant only the minimum permissions required. Never use superuser for application queries.
+
+**Incorrect (overly broad permissions):**
+
+```sql
+-- Application uses superuser connection
+-- Or grants ALL to application role
+grant all privileges on all tables in schema public to app_user;
+grant all privileges on all sequences in schema public to app_user;
+
+-- Any SQL injection becomes catastrophic
+-- drop table users; cascades to everything
+```
+
+**Correct (minimal, specific grants):**
+
+```sql
+-- Create role with no default privileges
+create role app_readonly nologin;
+
+-- Grant only SELECT on specific tables
+grant usage on schema public to app_readonly;
+grant select on public.products, public.categories to app_readonly;
+
+-- Create role for writes with limited scope
+create role app_writer nologin;
+grant usage on schema public to app_writer;
+grant select, insert, update on public.orders to app_writer;
+grant usage on sequence orders_id_seq to app_writer;
+-- No DELETE permission
+
+-- Login role inherits from these
+create role app_user login password 'xxx';
+grant app_writer to app_user;
+```
+
+Revoke public defaults:
+
+```sql
+-- Revoke default public access
+revoke all on schema public from public;
+revoke all on all tables in schema public from public;
+```
+
+Reference: [Roles and Privileges](https://supabase.com/blog/postgres-roles-and-privileges)

package/skills/craft/supabase-postgres-best-practices/references/security-rls-basics.md

@@ -1,50 +1,50 @@
----
-title: Enable Row Level Security for Multi-Tenant Data
-impact: CRITICAL
-impactDescription: Database-enforced tenant isolation, prevent data leaks
-tags: rls, row-level-security, multi-tenant, security
----
-
-## Enable Row Level Security for Multi-Tenant Data
-
-Row Level Security (RLS) enforces data access at the database level, ensuring users only see their own data.
-
-**Incorrect (application-level filtering only):**
-
-```sql
--- Relying only on application to filter
-select * from orders where user_id = $current_user_id;
-
--- Bug or bypass means all data is exposed!
-select * from orders;  -- Returns ALL orders
-```
-
-**Correct (database-enforced RLS):**
-
-```sql
--- Enable RLS on the table
-alter table orders enable row level security;
-
--- Create policy for users to see only their orders
-create policy orders_user_policy on orders
-  for all
-  using (user_id = current_setting('app.current_user_id')::bigint);
-
--- Force RLS even for table owners
-alter table orders force row level security;
-
--- Set user context and query
-set app.current_user_id = '123';
-select * from orders;  -- Only returns orders for user 123
-```
-
-Policy for authenticated role:
-
-```sql
-create policy orders_user_policy on orders
-  for all
-  to authenticated
-  using (user_id = auth.uid());
-```
-
-Reference: [Row Level Security](https://supabase.com/docs/guides/database/postgres/row-level-security)
+---
+title: Enable Row Level Security for Multi-Tenant Data
+impact: CRITICAL
+impactDescription: Database-enforced tenant isolation, prevent data leaks
+tags: rls, row-level-security, multi-tenant, security
+---
+
+## Enable Row Level Security for Multi-Tenant Data
+
+Row Level Security (RLS) enforces data access at the database level, ensuring users only see their own data.
+
+**Incorrect (application-level filtering only):**
+
+```sql
+-- Relying only on application to filter
+select * from orders where user_id = $current_user_id;
+
+-- Bug or bypass means all data is exposed!
+select * from orders;  -- Returns ALL orders
+```
+
+**Correct (database-enforced RLS):**
+
+```sql
+-- Enable RLS on the table
+alter table orders enable row level security;
+
+-- Create policy for users to see only their orders
+create policy orders_user_policy on orders
+  for all
+  using (user_id = current_setting('app.current_user_id')::bigint);
+
+-- Force RLS even for table owners
+alter table orders force row level security;
+
+-- Set user context and query
+set app.current_user_id = '123';
+select * from orders;  -- Only returns orders for user 123
+```
+
+Policy for authenticated role:
+
+```sql
+create policy orders_user_policy on orders
+  for all
+  to authenticated
+  using (user_id = auth.uid());
+```
+
+Reference: [Row Level Security](https://supabase.com/docs/guides/database/postgres/row-level-security)