superkit-mcp-server 1.1.4 → 1.2.0

package/skills/meta/examples/supabase/templates/migration-template.sql

@@ -1,49 +1,49 @@
--- Migration: {Brief description of what this migration does}
--- Date: {YYYY-MM-DD}
--- Purpose: {Detailed explanation of why this migration is needed}
--- Requirements: {Requirement IDs if applicable, e.g., "4.1, 4.2"}
--- Feature: {feature-name if part of a larger feature}
-
--- ============================================================================
--- TODO: Replace placeholders with actual migration code
--- ============================================================================
-
--- Example: Create ENUM type (use DO block for idempotency)
-DO $$ BEGIN
-    CREATE TYPE {type_name} AS ENUM ('{value1}', '{value2}');
-EXCEPTION
-    WHEN duplicate_object THEN null;
-END $$;
-
--- Example: Create table
-CREATE TABLE IF NOT EXISTS {schema}.{table_name} (
-    id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
-    {column_name} {data_type} {constraints},
-    created_at TIMESTAMPTZ DEFAULT NOW() NOT NULL,
-    updated_at TIMESTAMPTZ DEFAULT NOW() NOT NULL
-);
-
--- Example: Create indexes
-CREATE INDEX IF NOT EXISTS idx_{table}_{column} 
-ON {schema}.{table} ({column});
-
--- Example: Create updated_at trigger
-DROP TRIGGER IF EXISTS update_{table}_updated_at ON {schema}.{table};
-CREATE TRIGGER update_{table}_updated_at
-    BEFORE UPDATE ON {schema}.{table}
-    FOR EACH ROW
-    EXECUTE FUNCTION public.update_updated_at_column();
-
--- Example: Enable Row Level Security
-ALTER TABLE {schema}.{table} ENABLE ROW LEVEL SECURITY;
-
--- Example: Create RLS policy
-CREATE POLICY "{policy description}"
-ON {schema}.{table}
-FOR {operation}
-TO authenticated
-USING ({condition});
-
--- Example: Add documentation
-COMMENT ON TABLE {schema}.{table} IS '{table description}';
-COMMENT ON COLUMN {schema}.{table}.{column} IS '{column description}';
+-- Migration: {Brief description of what this migration does}
+-- Date: {YYYY-MM-DD}
+-- Purpose: {Detailed explanation of why this migration is needed}
+-- Requirements: {Requirement IDs if applicable, e.g., "4.1, 4.2"}
+-- Feature: {feature-name if part of a larger feature}
+
+-- ============================================================================
+-- TODO: Replace placeholders with actual migration code
+-- ============================================================================
+
+-- Example: Create ENUM type (use DO block for idempotency)
+DO $$ BEGIN
+    CREATE TYPE {type_name} AS ENUM ('{value1}', '{value2}');
+EXCEPTION
+    WHEN duplicate_object THEN null;
+END $$;
+
+-- Example: Create table
+CREATE TABLE IF NOT EXISTS {schema}.{table_name} (
+    id UUID PRIMARY KEY DEFAULT gen_random_uuid(),
+    {column_name} {data_type} {constraints},
+    created_at TIMESTAMPTZ DEFAULT NOW() NOT NULL,
+    updated_at TIMESTAMPTZ DEFAULT NOW() NOT NULL
+);
+
+-- Example: Create indexes
+CREATE INDEX IF NOT EXISTS idx_{table}_{column} 
+ON {schema}.{table} ({column});
+
+-- Example: Create updated_at trigger
+DROP TRIGGER IF EXISTS update_{table}_updated_at ON {schema}.{table};
+CREATE TRIGGER update_{table}_updated_at
+    BEFORE UPDATE ON {schema}.{table}
+    FOR EACH ROW
+    EXECUTE FUNCTION public.update_updated_at_column();
+
+-- Example: Enable Row Level Security
+ALTER TABLE {schema}.{table} ENABLE ROW LEVEL SECURITY;
+
+-- Example: Create RLS policy
+CREATE POLICY "{policy description}"
+ON {schema}.{table}
+FOR {operation}
+TO authenticated
+USING ({condition});
+
+-- Example: Add documentation
+COMMENT ON TABLE {schema}.{table} IS '{table description}';
+COMMENT ON COLUMN {schema}.{table}.{column} IS '{column description}';

package/skills/meta/examples/supabase/templates/rls-policy-template.sql

@@ -1,77 +1,77 @@
--- Row Level Security Policy Template
--- Table: {schema}.{table_name}
--- Description: {What data access this policy controls}
-
--- ============================================================================
--- Policy: User-Owned Data
--- Use when: Users should only see/modify their own data
--- ============================================================================
-
-CREATE POLICY "Users can view own data"
-ON {schema}.{table}
-FOR SELECT
-TO authenticated
-USING (user_id = auth.uid());
-
-CREATE POLICY "Users can update own data"
-ON {schema}.{table}
-FOR UPDATE
-TO authenticated
-USING (user_id = auth.uid())
-WITH CHECK (user_id = auth.uid());
-
--- ============================================================================
--- Policy: Role-Based Access
--- Use when: Certain roles should have broader access
--- ============================================================================
-
-CREATE POLICY "Fund Managers can view all"
-ON {schema}.{table}
-FOR SELECT
-TO authenticated
-USING (
-    EXISTS (
-        SELECT 1 FROM public.profiles
-        WHERE profiles.id = auth.uid()
-        AND profiles.role = 'fund_manager'
-    )
-);
-
--- ============================================================================
--- Policy: Fund-Scoped Multi-Tenancy
--- Use when: Data belongs to a fund and users should see only their fund's data
--- ============================================================================
-
-CREATE POLICY "Users see own fund data"
-ON {schema}.{table}
-FOR SELECT
-TO authenticated
-USING (
-    fund_id IN (
-        SELECT fund_id FROM user_fund_access
-        WHERE user_id = auth.uid()
-    )
-);
-
--- ============================================================================
--- Policy: Service Role Operations
--- Use when: System operations need unrestricted access
--- ============================================================================
-
-CREATE POLICY "Service role can insert"
-ON {schema}.{table}
-FOR INSERT
-TO authenticated
-WITH CHECK (true);
--- NOTE: Document why unrestricted access is needed
-
--- ============================================================================
--- Policy: Public Read
--- Use when: Data is public and anyone can read it
--- ============================================================================
-
-CREATE POLICY "Public can view"
-ON {schema}.{table}
-FOR SELECT
-TO anon, authenticated
-USING (true);
+-- Row Level Security Policy Template
+-- Table: {schema}.{table_name}
+-- Description: {What data access this policy controls}
+
+-- ============================================================================
+-- Policy: User-Owned Data
+-- Use when: Users should only see/modify their own data
+-- ============================================================================
+
+CREATE POLICY "Users can view own data"
+ON {schema}.{table}
+FOR SELECT
+TO authenticated
+USING (user_id = auth.uid());
+
+CREATE POLICY "Users can update own data"
+ON {schema}.{table}
+FOR UPDATE
+TO authenticated
+USING (user_id = auth.uid())
+WITH CHECK (user_id = auth.uid());
+
+-- ============================================================================
+-- Policy: Role-Based Access
+-- Use when: Certain roles should have broader access
+-- ============================================================================
+
+CREATE POLICY "Fund Managers can view all"
+ON {schema}.{table}
+FOR SELECT
+TO authenticated
+USING (
+    EXISTS (
+        SELECT 1 FROM public.profiles
+        WHERE profiles.id = auth.uid()
+        AND profiles.role = 'fund_manager'
+    )
+);
+
+-- ============================================================================
+-- Policy: Fund-Scoped Multi-Tenancy
+-- Use when: Data belongs to a fund and users should see only their fund's data
+-- ============================================================================
+
+CREATE POLICY "Users see own fund data"
+ON {schema}.{table}
+FOR SELECT
+TO authenticated
+USING (
+    fund_id IN (
+        SELECT fund_id FROM user_fund_access
+        WHERE user_id = auth.uid()
+    )
+);
+
+-- ============================================================================
+-- Policy: Service Role Operations
+-- Use when: System operations need unrestricted access
+-- ============================================================================
+
+CREATE POLICY "Service role can insert"
+ON {schema}.{table}
+FOR INSERT
+TO authenticated
+WITH CHECK (true);
+-- NOTE: Document why unrestricted access is needed
+
+-- ============================================================================
+-- Policy: Public Read
+-- Use when: Data is public and anyone can read it
+-- ============================================================================
+
+CREATE POLICY "Public can view"
+ON {schema}.{table}
+FOR SELECT
+TO anon, authenticated
+USING (true);