This skill should be used when the user mentions "srtd", "sql templates", "migrations-templates", "live reload sql", "supabase functions", when working with files in supabase/migrations-templates/, when .buildlog.json or srtd.config.json is detected, or when writing Postgres functions/views/triggers for Supabase.
Installation
Details
Usage
After installing, this skill will be available to your AI coding assistant.
Verify installation:
skills listSkill Instructions
name: srtd-cli description: This skill should be used when the user mentions "srtd", "sql templates", "migrations-templates", "live reload sql", "supabase functions", when working with files in supabase/migrations-templates/, when .buildlog.json or srtd.config.json is detected, or when writing Postgres functions/views/triggers for Supabase.
SRTD - Iterative SQL Template Development
Workflow
Start watch in background immediately:
srtd watch --json
Use run_in_background: true. Monitor with TaskOutput for events: templateApplied (success), templateError (check errorMessage/errorHint).
Templates
Location: supabase/migrations-templates/*.sql. Must be idempotent.
Idempotency patterns:
- Functions/Views:
CREATE OR REPLACE(useDROPonly when changing signature) - Policies:
DROP POLICY IF EXISTSthenCREATE POLICY(not replaceable) - Triggers: Drop BOTH trigger AND function first
Dependencies: -- @depends-on: other.sql at top
WIP: .wip.sql suffix → applies locally, never builds
Commands
srtd apply [--force] [--json] # Apply to local DB (use instead of watch for one-off)
srtd build [--bundle] # Generate migration FILES only (does NOT apply to DB)
srtd clear --reset # Reset state if confused
State
.buildlog.json→ commit (tracks built migrations).buildlog.local.json→ gitignored (local DB state)
More by t1mmen
View allExpert knowledge for developing the SRTD codebase itself. Use when implementing features, fixing bugs, understanding architecture, or writing tests for SRTD internals. NOT for end users of srtd CLI.
Structured code review workflow for SRTD development. Use after implementing features, fixing bugs, or before merging to main. Ensures production-readiness through systematic review.