t1mmen
diff --git a/‎.claude/rules/srtd.md‎
Lines changed: 18 additions & 0 deletions b/‎.claude/rules/srtd.md‎
Lines changed: 18 additions & 0 deletions
diff --git a/‎.claude/skills/srtd-cli/SKILL.md‎
Lines changed: 21 additions & 205 deletions b/‎.claude/skills/srtd-cli/SKILL.md‎
Lines changed: 21 additions & 205 deletions
diff --git a/‎README.md‎
Lines changed: 12 additions & 0 deletions b/‎README.md‎
Lines changed: 12 additions & 0 deletions
diff --git a/‎supabase/migrations-templates/.srtd.buildlog.json‎
Lines changed: 0 additions & 11 deletions b/‎supabase/migrations-templates/.srtd.buildlog.json‎
Lines changed: 0 additions & 11 deletions
diff --git a/‎supabase/migrations-templates/test.sql‎
Lines changed: 0 additions & 6 deletions b/‎supabase/migrations-templates/test.sql‎
Lines changed: 0 additions & 6 deletions
@@ -0,0 +1,18 @@
+---
+paths:
+  - "**/supabase/migrations-templates/**/*.sql"
+---
+
+# SRTD Template
+
+Load `Skill('srtd-cli')` for full context.
+
+**Idempotency rules:**
+- Functions/Views: `CREATE OR REPLACE` (use `DROP` only when changing signature)
+- Policies: `DROP IF EXISTS` then `CREATE`
+- Triggers: Drop both trigger AND function first
+
+**Quick reference:**
+- Dependencies: `-- @depends-on: other.sql` at top
+- WIP files: `.wip.sql` suffix (local only, won't build)
+- Watch mode: `srtd watch --json` in background
@@ -1,224 +1,40 @@
 ---
 name: srtd-cli
-description: Guide users through SRTD CLI for live-reloading SQL templates into Supabase. Use when users ask about srtd commands, template writing, migrations, watch mode, or Supabase database object management.
+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 CLI Usage Guide
+# SRTD - Iterative SQL Template Development
 
-SRTD makes database objects (functions, views, RLS policies, triggers) reviewable like regular code. Templates are the source of truth; they build to timestamped migrations.
-
-## Quick Start
-
-```bash
-# Install
-npm install -g @t1mmen/srtd   # or: npx @t1mmen/srtd
-
-# Initialize in Supabase project
-npx @t1mmen/srtd init
-
-# Create first template
-cat > supabase/migrations-templates/hello.sql << 'EOF'
-DROP FUNCTION IF EXISTS public.hello;
-CREATE FUNCTION public.hello() RETURNS text AS $$
-BEGIN
-  RETURN 'Hello from SRTD!';
-END;
-$$ LANGUAGE plpgsql;
-EOF
-
-# Start live reload
-npx @t1mmen/srtd watch
-```
-
-## Commands
-
-| Command | Purpose |
-|---------|---------|
-| `srtd` | Interactive menu |
-| `srtd watch` | Live reload - edits apply instantly to local DB |
-| `srtd build` | Generate migration files from templates |
-| `srtd apply` | Apply templates to DB without generating migrations |
-| `srtd register` | Mark existing templates as already deployed |
-| `srtd promote` | Convert `.wip` template to buildable |
-| `srtd clear` | Reset build logs |
-
-### Command Options
-
-```bash
-srtd build --force          # Rebuild all templates
-srtd build --bundle         # All templates → single migration
-srtd apply --force          # Reapply all templates
-srtd clear --local          # Clear local state only
-srtd clear --shared         # Clear shared state only
-srtd clear --reset          # Full reset
-```
-
-## Core Workflow
-
-```
-1. CREATE template     → supabase/migrations-templates/my_func.sql
-2. WATCH mode         → srtd watch (auto-applies on save)
-3. TEST locally       → Query your function in Supabase Studio
-4. BUILD migration    → srtd build
-5. DEPLOY            → supabase migration up
-```
-
-## Template Patterns
-
-### Functions (Most Common)
-
-```sql
--- Always DROP first to allow parameter changes
-DROP FUNCTION IF EXISTS public.calculate_total;
-CREATE FUNCTION public.calculate_total(order_id uuid)
-RETURNS numeric AS $$
-BEGIN
-  RETURN (SELECT SUM(price * quantity) FROM order_items WHERE order_id = $1);
-END;
-$$ LANGUAGE plpgsql;
-```
-
-### RLS Policies
-
-```sql
-DROP POLICY IF EXISTS "users_own_data" ON profiles;
-CREATE POLICY "users_own_data" ON profiles
-  USING (auth.uid() = user_id);
-```
-
-### Views
-
-```sql
-CREATE OR REPLACE VIEW active_users AS
-SELECT id, email, last_seen
-FROM users
-WHERE last_seen > NOW() - INTERVAL '30 days';
-```
-
-### Triggers
-
-```sql
-DROP TRIGGER IF EXISTS on_user_created ON auth.users;
-DROP FUNCTION IF EXISTS handle_new_user;
-
-CREATE FUNCTION handle_new_user() RETURNS trigger AS $$
-BEGIN
-  INSERT INTO public.profiles (id, email)
-  VALUES (NEW.id, NEW.email);
-  RETURN NEW;
-END;
-$$ LANGUAGE plpgsql SECURITY DEFINER;
-
-CREATE TRIGGER on_user_created
-  AFTER INSERT ON auth.users
-  FOR EACH ROW EXECUTE FUNCTION handle_new_user();
-```
-
-### Enum Extensions
-
-```sql
-DO $$
-BEGIN
-  IF NOT EXISTS (SELECT 1 FROM pg_type WHERE typname = 'status') THEN
-    CREATE TYPE status AS ENUM ('pending', 'active');
-  END IF;
-  ALTER TYPE status ADD VALUE IF NOT EXISTS 'archived';
-END $$;
-```
-
-## WIP Templates
-
-Use `.wip.sql` suffix for work-in-progress:
-
-```bash
-# Create WIP template (applies locally, never builds to migration)
-touch supabase/migrations-templates/experimental.wip.sql
-
-# When ready to deploy
-srtd promote experimental.wip.sql
-# Renames to experimental.sql, next build creates migration
-```
-
-## Registering Existing Objects
-
-When adopting SRTD on existing project:
+## Workflow
 
+Start watch in background immediately:
 ```bash
-# Create templates for existing functions
-# Then register them (prevents immediate migration generation)
-srtd register my_existing_function.sql another_function.sql
-
-# Or interactively select which to register
-srtd register
-```
-
-## Configuration
-
-`srtd.config.json` (optional - sensible defaults):
-
-```jsonc
-{
-  "templateDir": "supabase/migrations-templates",
-  "migrationDir": "supabase/migrations",
-  "pgConnection": "postgresql://postgres:postgres@localhost:54322/postgres",
-  "wipIndicator": ".wip",
-  "migrationPrefix": "srtd",
-  "wrapInTransaction": true
-}
+srtd watch --json
 ```
+Use `run_in_background: true`. Monitor with `TaskOutput` for events: `templateApplied` (success), `templateError` (check `errorMessage`/`errorHint`).
 
-## State Files
+## Templates
 
-| File | Purpose | Git |
-|------|---------|-----|
-| `.buildlog.json` | Tracks built migrations | Commit |
-| `.buildlog.local.json` | Tracks local DB state | Gitignore |
+Location: `supabase/migrations-templates/*.sql`. Must be idempotent.
 
-## What SRTD Is For
+**Idempotency patterns:**
+- Functions/Views: `CREATE OR REPLACE` (use `DROP` only when changing signature)
+- Policies: `DROP POLICY IF EXISTS` then `CREATE POLICY` (not replaceable)
+- Triggers: Drop BOTH trigger AND function first
 
-**Use SRTD for** (idempotent, replaceable):
-- Functions
-- Views
-- RLS policies
-- Triggers
-- Roles/permissions
-- Enum extensions
+**Dependencies:** `-- @depends-on: other.sql` at top
 
-**Use regular migrations for** (stateful):
-- Table structures
-- Indexes
-- Data modifications
-- Column alterations
+**WIP:** `.wip.sql` suffix → applies locally, never builds
 
-## Troubleshooting
-
-### "Could not find project root"
-Run from directory containing `supabase/` folder.
-
-### Database connection failed
-Check `pgConnection` in config. Default Supabase local:
-```
-postgresql://postgres:postgres@localhost:54322/postgres
-```
-Ensure Supabase is running: `supabase start`
-
-### Template not applying
-1. Check for SQL syntax errors (shown in watch output)
-2. Ensure template uses idempotent pattern (DROP IF EXISTS)
-3. Try `srtd apply --force`
+## Commands
 
-### Build logs out of sync
 ```bash
-srtd clear --reset   # Full reset
-srtd watch           # Reapply all templates
+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
 ```
 
-### "Interactive mode requires TTY"
-Use flags instead: `srtd clear --local` not `srtd clear`
-
-## Watch Mode Tips
+## State
 
-- Press `u` to toggle history display
-- Press `q` to quit
-- Errors show immediately with file path and message
-- Multiple terminals: one for watch, one for testing
+- `.buildlog.json` → commit (tracks built migrations)
+- `.buildlog.local.json` → gitignored (local DB state)
@@ -233,6 +233,18 @@ Nested directories are created automatically.
 | `.buildlog.json`       | What's been built to migrations | Commit    |
 | `.buildlog.local.json` | What's applied to your local DB | Gitignore |
 
+## Claude Code Integration
+
+SRTD includes a skill and rule for [Claude Code](https://claude.ai/code) users:
+
+```bash
+# Copy to your project's .claude directory
+cp -r node_modules/@t1mmen/srtd/.claude/skills/srtd-cli .claude/skills/
+cp -r node_modules/@t1mmen/srtd/.claude/rules/srtd.md .claude/rules/
+```
+
+The skill activates when working with SQL templates. The rule provides inline guidance for template files.
+
 ## Contributing
 
 Bug fixes, docs, and test coverage welcome. See [CONTRIBUTING.md](./CONTRIBUTING.md).