smithery.ai

supabase-backend

Expert in Supabase architecture, SQL optimization (PostgreSQL), and backend security (RLS) for real-time tracking systems.

First seen Mar 24, 2026

Installation

$ npx skills add https://smithery.ai

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,837 B
  • docs SUMMARY.md 146 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 2 installs

SKILL.md

Supabase & Backend Architecture Skill

This skill enables the assistant to provide high-level architectural advice and implementation details for the iTaxiBcn backend.

Knowledge Areas

1. Database Schema Optimization

  • Time-Series Data: Guidelines for handling high-frequency location updates in registrosreten and geofencelogs.
  • Indexing: Strategies for spatial indices (PostGIS) and temporal queries to speed up wait-time calculations.
  • Materialized Views: Recommendation for replacing heavy queries on registros_reten with materialized views for zone aggregations.

2. Row Level Security (RLS)

  • Device-Based Access: Ensuring device_id based security since the app currently uses device identifiers instead of full user auth (until Phase 2).
  • Audit Logs: Best practices for geofencelogs and locationdebug_logs security.

3. Edge Functions (Deno/TypeScript)

  • Geofencing Logic: Optimization of the Ray-casting algorithm in check-geofence.
  • Performance: Minimizing startup time and memory footprint of edge functions.
  • Error Handling: Robust try-catch patterns and standard JSON responses.

4. SQL Scripting

  • Migrations: Following the supabase/migrations/ structure.
  • Stored Procedures: Writing efficient PL/pgSQL for complex logic like useWhereNext score calculation on the server side.

Guidelines for Responses

  • Always suggest Materialized Views for dashboard metrics that don't need second-by-second accuracy.
  • When writing SQL, ensure idempotency (use CREATE OR REPLACE or IF NOT EXISTS).
  • Prioritize PostGIS functions for distance and polygon math.