Provision Supabase projects with schema, RLS policies, and client integration.
npx skills add https://github.com/lhz960904/code-artisan --skill supabase-lhz960904
Please help me install this Agent Skill. Skill: supabase Source: https://github.com/lhz960904/code-artisan/tree/main/sandbox-template/skills/supabase Command: npx skills add https://github.com/lhz960904/code-artisan --skill supabase-lhz960904
This Skill helps you add persistent data, authentication, file storage, and realtime updates to an app by provisioning a Supabase project and wiring your frontend to it securely with Row Level Security (RLS).
Use cases: todo apps that sync across reloads, apps with user accounts and protected per-user data, apps that upload user files, and multi-user experiences like chats or live feeds.
Use the supabase skill to create your Supabase-backed todo app with user-scoped tables protected by RLS, then wire the frontend to Supabase JS using the injected VITE_SUPABASE_URL and VITE_SUPABASE_ANON_KEY.
High-intent search queries and answers about installing and using this skill.
Supabase RLS setup provisions your project, defines Postgres tables, and applies auth.uid()-scoped policies via a privileged SQL tool. This securely protects per-user data by enforcing Row Level Security without exposing your service-role key.
Realtime subscriptions are enabled by configuring the Supabase JS client using injected VITE_SUPABASE_URL and VITE_SUPABASE_ANON_KEY environment variables. Live updates across sessions and users are delivered while still respecting your active RLS policies.
Yes, you can provision Supabase file storage for user uploads. The Skill provisions a Supabase project and wires your frontend to securely handle file storage uploads alongside authentication and protected data.
You wire the frontend using the injected VITE_SUPABASE_URL and VITE_SUPABASE_ANON_KEY environment variables. Schema and RLS are applied through a privileged SQL tool using your OAuth context, ensuring the service-role key is never exposed.
Yes, Supabase realtime respects RLS policies across multiple users. When you configure the Supabase JS client for live updates, the realtime subscriptions enforce your auth.uid()-scoped policies to secure multi-user experiences like chats or live feeds.
The best way is to create or reuse a Supabase project, define your Postgres schema with indexes and seeds via SQL, and wire the frontend client using VITE environment variables. This provisions secure CRUD apps needing auth, protected tables, and realtime sync.
Tresillo2017Configure Better Auth server and client with adapters, sessions, and plugins.
Nice-Wolf-StudioMonitor Supabase database changes via WebSocket subscriptions.
desibarraConfigure Supabase PostgreSQL authentication and memory storage for SaaS apps.
photon-hqSend and receive iMessages programmatically via WebSockets and AppleScript.
