Results for “pattern”

TypeORM for TypeScript/JavaScript. Covers entities, repositories, and relations. Use with SQL databases. USE WHEN: user mentions "typeorm", "@Entity", "Repository", "DataSource", "QueryBuilder", "typeorm migration", asks about "decorators for database", "active record pattern", "entity relationships", "typeorm relations" DO NOT USE FOR: Prisma projects - use `prisma` skill; Drizzle - use `drizzle` skill; SQLAlchemy (Python) - use `sqlalchemy` skill; raw SQL - use `database-query` MCP; NoSQL - use `mongodb` skill; Sequelize - not supported

Supabase-first database schema design for Nick's app stack. Generate production-ready Postgres schemas, Supabase SQL migrations, RLS policies, TypeScript types, seed data, role-aware access patterns, and schema checklists from plain English requirements. Use when starting any new project database, designing or reviewing schemas, adding tables, planning migrations, or turning product requirements into Supabase-ready data models. Bias toward product-led schema design, MVP discipline, core-workflow-first modeling, and avoiding premature table/role sprawl.

Structured data + RAG. NL2SQL hybrid patterns (text-to-SQL then execute vs embed rows), table embedding strategies (row-level, schema-level, hybrid), semantic layer integration (Cube, dbt metrics), LangChain SQLDatabaseChain, LlamaIndex PandasQueryEngine, safe SQL execution (read-only, sandboxed), schema-aware retrieval. Full PostgreSQL + pgvector hybrid code. USE WHEN: user mentions "tabular RAG", "NL2SQL", "text to SQL", "RAG on tables", "database RAG", "SQL RAG", "semantic layer", "structured data RAG" DO NOT USE FOR: unstructured doc RAG - use `rag-architecture`; metadata filtering only - use `self-querying-retriever`; KG retrieval - use `graph-rag`