Menu
Expert guidance on Supabase/PostgreSQL implementation for RAG, including pgvector semantic search and full-text search.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Help the team document and maintain Architecture Decision Records (ADRs).
Expert guidance on document processing with Docling and audio transcription with Whisper.
Standard for creating technical documentation in this repository. Use this when writing new documentation in docs/ to ensure consistent hierarchy and formatting.
Expert guidance on creating accurate, visually polished Mermaid diagrams for architecture documentation.
Expert guidance on MongoDB implementation for RAG, including aggregation pipelines and search patterns.
Expert guidance on building agents and tools with Pydantic AI.
| name | supabase |
| description | Expert guidance on Supabase/PostgreSQL implementation for RAG, including pgvector semantic search and full-text search. |
This skill provides patterns for implementing RAG logic with Supabase and the pgvector extension.
documents: Stores source document text and global metadata.chunks: Stores text fragments, embedding (vector), and a foreign key document_id (UUID).ON DELETE CASCADE from chunks to documents for clean deletions.Semantic Search (pgvector):
match_chunks exists in the database.query_embedding (vector), match_threshold (float), match_count (int).self.client.rpc("match_chunks", rpc_params).execute().Text Search (WFTS):
self.client.table("chunks").select("...").filter("content", "wfts", query).range(0, limit - 1).execute().supabase Python library (create_client).match_chunks RPC is properly defined in the database schema before use.threshold for semantic matches is usually configurable in the repository's __init__.