insforge

This skill covers client-side SDK integration using @insforge/sdk . For backend infrastructure operations (creating tables, inspecting schema, deploying functions, secrets, managing storage buckets, website deployments, cron job and schedules, logs, etc.), use the insforge-cli skill. For real-time channels and database triggers, use insforge db query with SQL to create triggers that publish to channels. The real-time SDK is for frontend event handling and messaging, not backend configuration. Automatically publish events when database records change. RLS is disabled by default. To restrict channel access: Create channel patterns first before subscribing from frontend Use specific channel patterns These modules still require HTTP API calls because the CLI does not yet support them: All SDK methods return { data, error } . - Enable RLS - Restrict Subscribe (SELECT on channels) - Restrict Publish (INSERT on messages) - Quick Reference - Create channel patterns first before subscribing from frontend - Insert channel patterns into realtime.channels table - Ensure enabled is set to true - Use specific channel patterns - Use wildcard % patterns for dynamic channels (e.g., order:% for order:123 ) - Use exact patterns for global channels (e.g., notifications ) - Database inserts require array format : insert([{...}]) not insert({...}) - Storage : Save both url AND key to database for...