From cortex
This skill should be used before writing any Supabase or PostgREST query — 8 gotchas that cause silent failures.
How this skill is triggered — by the user, by Claude, or both
Slash command
/cortex:database-query-safetyThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Auto-injected**: These gotchas are automatically surfaced via PreToolUse prompt hook every time you write Supabase/PostgREST code. No need to invoke this skill for routine query writing.
Auto-injected: These gotchas are automatically surfaced via PreToolUse prompt hook every time you write Supabase/PostgREST code. No need to invoke this skill for routine query writing.
When to invoke explicitly: Deep-dive review of complex queries, debugging silent data loss, or onboarding to PostgREST patterns. See:
references/postgrest-gotchas.md — detailed explanations with real incident history and code examplesexamples/ — safe query patterns for common operationsnpx claudepluginhub crombieman/undercurrent-cortex --plugin cortexGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Implements work from a spec or tickets using TDD at agreed seams, with regular typechecking and test runs, followed by code review.