supabase-realtime

Implement scalable Supabase Realtime features with broadcast-based channels.

6|Updated Oct 29, 2025
One-click install
npx skills add https://github.com/Raudbjorn/claude --skill supabase-realtime-raudbjorn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: supabase-realtime
Source: https://github.com/Raudbjorn/claude/tree/main/supabase-realtime
Command: npx skills add https://github.com/Raudbjorn/claude --skill supabase-realtime-raudbjorn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides comprehensive guidance to implement scalable Supabase Realtime features, replacing fragile, non-scalable change feeds with robust broadcast-based patterns.

Core Features & Use Cases

  • Client setup patterns for private, granular channels
  • Database triggers using realtime.broadcast_changes with per-topic topics
  • RLS-enabled access control and optimized policies
  • Migration guidance from postgres_changes to broadcast
  • Performance tips and indexing strategies

Quick Start

Example: Create a room messages channel and subscribe to message events. Use: const channel = supabase.channel('room:123:messages', { config: { private: true } }) channel .on('broadcast', { event: 'message_created' }, payload => { /* handle payload */ }) .subscribe()

Frequently Asked Questions about supabase-realtime

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build scalable real-time features in Supabase for live messaging and collaboration?▼

To build scalable Supabase real-time features, use broadcast-based patterns with private, granular channels and database triggers. This replaces fragile change feeds with robust per-topic channel design for messaging and collaboration.

What is the best way to migrate from postgres_changes to broadcast in Supabase Realtime?▼

Migrating from postgres_changes to broadcast involves using database triggers with realtime.broadcast_changes and setting up per-topic channels. This break-glass migration pattern ensures your real-time updates remain scalable and reliable.

How does Supabase Realtime broadcast work with RLS for private channel access control?▼

Supabase Realtime broadcast works with RLS by enabling private channels and applying optimized RLS policies. You configure channels with private: true and use granular access control to secure per-topic event subscriptions.

Can I use Supabase database triggers to send broadcast events for specific topics?▼

Yes, you can use Supabase database triggers to send broadcast events by implementing realtime.broadcast_changes with per-topic topics. This allows targeted real-time updates for specific entities like room messages.

Why are my Supabase Realtime broadcasts not scaling and how do I optimize performance?▼

Supabase Realtime broadcasts may not scale if using non-scalable change feeds instead of broadcast patterns. Optimize performance by implementing indexing strategies and migrating to per-topic broadcast channels.

Do I need to use database triggers for Supabase Realtime presence and live updates?▼

For Supabase Realtime presence and live updates, database triggers using realtime.broadcast_changes are recommended to push events to private channels. This ensures scalable per-topic delivery for collaboration features.