supabase-schema-from-requirements

Design Supabase Postgres schema from business requirements with migrations, RLS, and types. Use when translating specifications into database tables, creating migration files, adding Row Level Security policies, or generating TypeScript types from schema. Trigger with phrases like "supabase schema", "design database supabase", "schema from requirements", "supabase migration", "supabase tables from spec".

Ir para a instalação

Repositório: jeremylongshore/tons-of-skills-marketplace
Última atividade na origem: 19 de agosto de 2026 às 12:13
Idioma detectado do SKILL.md: inglês
Estrelas: 2.677
Forks: 392

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.

npx skills add https://github.com/jeremylongshore/tons-of-skills-marketplace --skill supabase-schema-from-requirements

O comando permanece em uma só linha. Role horizontalmente para revisá-lo antes de copiar.

Prefere uma cópia local? Baixe os arquivos disponíveis atualmente no SkillsMP.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

Explorador de arquivos

4 arquivos

SKILL.md

Instruções da origem · Visualização somente leitura

Voltar à pesquisa Voltar à instalação

langchain-deploy-integration

Deploy a LangChain 1.0 / LangGraph 1.0 app to Cloud Run, Vercel, or LangServe correctly — with timeouts sized for chain length, cold-start mitigation, SSE anti-buffering headers, and Secret Manager over .env. Use when prepping a first production deploy, debugging a stream that hangs behind a proxy, or diagnosing p99 latency spikes. Trigger with "langchain deploy", "langchain cloud run", "langchain vercel python", "langchain langserve", or "langchain docker".

2026-08-26

langchain-langgraph-agents

Build a correct LangGraph 1.0 ReAct agent with create_react_agent — typed tools, error propagation, recursion caps, and stop conditions that actually stop. Use when writing a first tool-calling agent, migrating from AgentExecutor or initialize_agent, or diagnosing an agent that loops on vague prompts. Trigger with "langgraph agent", "create_react_agent", "langgraph tool calling", "AgentExecutor migration", or "agent loop cost".

2026-08-26

langchain-langgraph-human-in-loop

Build LangGraph 1.0 human-in-the-loop approval flows with interrupt_before / interrupt_after and Command(resume=...) — JSON-serializable state, clean resume semantics, and UI wiring for approval decisions. Use when adding an approval gate before an expensive tool call, wiring a Slack/web UI for agent approvals, or debugging a graph that crashes on interrupt. Trigger with "langgraph human in loop", "langgraph interrupt_before", "langgraph approval flow", "Command resume", "langgraph HITL".

2026-08-26

Ver todas deste repositório

name	supabase-schema-from-requirements
description	Design Supabase Postgres schema from business requirements with migrations, RLS, and types. Use when translating specifications into database tables, creating migration files, adding Row Level Security policies, or generating TypeScript types from schema. Trigger with phrases like "supabase schema", "design database supabase", "schema from requirements", "supabase migration", "supabase tables from spec".
allowed-tools	Read, Write, Bash(supabase:), Bash(npx:)
version	1.53.0
license	MIT
author	Jeremy Longshore <jeremy@intentsolutions.io>
tags	["saas","supabase","database","migration","schema-design","postgres","rls"]
compatibility	Designed for Claude Code

Supabase Schema from Requirements

Overview

Translate business requirements into a production-ready Postgres schema inside Supabase, covering the full path from specification to applied migration: entity extraction, tables with proper types and constraints, Row Level Security policies, performance indexes, timestamp triggers, and TypeScript type generation. Getting this right early matters because every downstream feature — auth, storage, realtime, edge functions — depends on well-designed tables.

Prerequisites

Supabase CLI installed (npm install -g supabase) and project linked (supabase link)
@supabase/supabase-js v2+ installed in the project
Business requirements, PRD, or specification document identifying entities and access rules
Local Supabase running (supabase start) or a linked remote project

Instructions

Step 1: Parse Requirements and Create Migration

Read the requirements document and extract entities, attributes, relationships, and access control rules. Map each entity to a Postgres table.

Entity extraction example (project management app):

Entity	Key Columns	Relationships
Organization	name, slug, plan	has many Projects, has many Members
Project	name, description, status	belongs to Organization, has many Tasks
Task	title, priority, status, due_date	belongs to Project, assigned to User
Member	role (owner/admin/member)	junction linking User to Organization

Create the migration file:

npx supabase migration new create_tables
# Creates: supabase/migrations/TIMESTAMP_create_tables.sql

Write the migration SQL using standard Postgres data types (uuid, text, integer, boolean, timestamptz, jsonb): Full worked migration (project-management app — tables, FKs, indexes, moddatetime triggers): references/worked-schema-examples.md.

Use case	Type	Notes
Primary keys	`uuid`	Always with `uuid_generate_v4()` default
Names, titles	`text`	Prefer over `varchar` in Postgres
Counts, ranks	`integer`	Use `bigint` for sequences
Flags	`boolean`	Default explicitly to `true` or `false`
Timestamps	`timestamptz`	Never use `timestamp` without timezone
Flexible data	`jsonb`	Queryable JSON; use for settings, metadata
Lists	`text[]`	Postgres arrays for simple tags or labels

Error	Cause	Solution
`42P07: relation already exists`	Table name collision in migration	Use `create table if not exists` or rename the table
`23503: foreign key violation`	Insert references a nonexistent parent row	Insert parent rows first, or check the UUID
`42501: insufficient privilege`	RLS helper function permissions	Add `security definer` to the function definition
`42883: function uuid_generate_v4() does not exist`	Extension not enabled	Add `create extension if not exists "uuid-ossp"`
`supabase db push` succeeds but tables missing	Migration was already recorded	Check `supabase_migrations.schema_migrations` and repair
`PGRST204: column not found`	TypeScript types out of sync	Re-run `npx supabase gen types typescript --local > types/supabase.ts`
`new row violates row-level security`	RLS policy blocks the operation	Verify `auth.uid()` matches expected value; check policy `using` clause
`moddatetime` trigger fails	Extension not enabled	Add `create extension if not exists "moddatetime"` at top of migration

supabase-schema-from-requirements

Opções de instalação

Revise os arquivos de origem

Supabase Schema from Requirements

Overview

Prerequisites

Instructions

Step 1: Parse Requirements and Create Migration

Supabase Schema from Requirements

Overview

Prerequisites

Instructions

Step 1: Parse Requirements and Create Migration

Step 2: Add Row Level Security Policies

Step 3: Apply Migration and Generate Types

Output

Error Handling

Examples

Resources

Next Steps

supabase-schema-from-requirements

Informações da origem

Opções de instalação

Revise os arquivos de origem

Mais deste repositório

Supabase Schema from Requirements

Overview

Prerequisites

Instructions

Step 1: Parse Requirements and Create Migration

Mais deste repositório

Supabase Schema from Requirements

Overview

Prerequisites

Instructions

Step 1: Parse Requirements and Create Migration

Step 2: Add Row Level Security Policies

Step 3: Apply Migration and Generate Types

Output

Error Handling

Examples

Resources

Next Steps