kodo-supabase

Architecture decision guide for multi-language applications (TypeScript, Python, Rust) using Supabase. Use when implementing backend features to decide between Supabase Edge Functions, Database Functions, Realtime, Storage, Auth, Queues, or custom backend services. Triggers on API endpoint implementation, webhook handling, background jobs, real-time features, file storage, authentication, database operations. Triggers on API endpoint implementation, webhook handling, background jobs, AI/vector search, hybrid ORM workflows, or any architectural decisions involving Supabase services vs custom backend code.

What problem does it solve?

This Skill helps engineering teams standardize decision-making around backend architecture when using Supabase across multiple programming languages, clarifying when to rely on managed services versus custom implementations.

Core Features & Use Cases

• Provides framework for evaluating when to adopt Supabase managed services vs custom backends
• Covers multi-language workflows (TypeScript, Python, Rust) and cross-service patterns
• Real-world example: selecting storage and auth integration for a multi-tenant app with webhooks and edge runtimes

Quick Start

Decide on the primary backend pattern (Edge Functions vs Database Functions), then outline the required triggers, migrations, and RLS across your languages.