Build with Supabase (Auth, Database, Functions)

Manage Supabase databases and auth

This supabase beats generic alternative approaches.

• · file or document content
• · configuration JSON
• · natural language query/prompt
• · session or state context
• · database schema or SQL
• · URL or file path
• · specification or requirements document

• · structured JSON output
• · task list or implementation plan
• · code, migrations, or SQL
• · database schema definition
• · active session handle
• · design specifications or mockups

• · MCP servers (standard)
• · Supabase API and CLI
• · PostgreSQL database
• · Git/GitHub API
• · local runtime (Node/Python/bash)

• · Tool/MCP installed and configured
• · Authentication credentials present
• · Database accessible with required permissions
• · Input file exists and is readable
• · Specification or requirements document prepared

• · Authentication failure or expired credentials
• · Timeout or rate limit exceeded on external calls
• · Network or API service unavailable
• · Input file missing or malformed
• · Validation fails on input or output
• · MCP server unreachable or schema mismatch

• · Open-source repo available: Sheshiyer/skill-clusters
• · Version and compatibility specified
• · Concrete usage examples provided
• · Verification/testing guidance included