Toolverse
All skills
Backend

supabase-known-pitfalls

by jeremylongshore

Execute identify and avoid Supabase anti-patterns and common integration mistakes.\nUse when reviewing Supabase code for issues, onboarding new developers,\nor auditing existing Supabase integrations for best practices violations.\nTrigger with phrases like \

Installation

Pick a client and clone the repository into its skills directory.

Installation

Quick info

Author
jeremylongshore
Category
Backend
GitHub repo

About this skill

Execute identify and avoid Supabase anti-patterns and common integration mistakes.\nUse when reviewing Supabase code for issues, onboarding new developers,\nor auditing existing Supabase integrations for best practices violations.\nTrigger with phrases like \

How to use

  1. Zainstaluj skill w swoim środowisku Claude/Codex, upewniając się, że masz dostęp do repozytorium kodu Supabase, który chcesz przeanalizować. 2. Przygotuj fragment kodu lub całą ścieżkę do projektu Supabase — skill będzie szukać typowych błędów przy użyciu narzędzi Read i Grep. 3. Wyzwól skill jedną z fraz: "supabase mistakes", "supabase anti-patterns", "supabase pitfalls", "supabase code review", "supabase gotchas", "supabase debugging" lub "what not to do supabase". 4. Skill przeanalizuje kod pod kątem 12 najczęstszych pułapek: ekspozycji service_role key, braku RLS, braku connection pooling, nieprawidłowego obsługiwania { data, error }, brakującego .select() po insert/update, .single() na opcjonalnych wynikach, wielu instancji klienta i braku typów generowanych. 5. Przejrzyj raporty z wyjaśnieniami, dlaczego każdy błąd jest niebezpieczny, i otrzymaj poprawne wzorce kodu używające createClient z @supabase/supabase-js v2+. 6. Zastosuj rekomendacje w swoim projekcie, szczególnie skupiając się na błędach bezpieczeństwa i integralności danych.

Related skills

literature-review

by K-Dense-AI

Conduct comprehensive, systematic literature reviews using multiple academic databases (PubMed, arXiv, bioRxiv, Semantic Scholar, etc.). This skill should be used when conducting systematic literature reviews, meta-analyses, research synthesis, or comprehensive literature

Backend
238507

stripe-integration

by wshobson

Implement Stripe payment processing for robust, PCI-compliant payment flows including checkout, subscriptions, and webhooks. Use when integrating Stripe payments, building subscription systems, or implementing secure checkout flows.

Backend
40147

himalaya

by openclaw

CLI to manage emails via IMAP/SMTP. Use `himalaya` to list, read, write, reply, forward, search, and organize emails from the terminal. Supports multiple accounts and message composition with MML (MIME Meta Language).

Backend
35108

supabase-operations

by elevanaltd

Supabase operational knowledge for migrations, RLS optimization, MCP tool benchmarks, and ADR-003 compliance. Use when validating database migrations, optimizing Row-Level Security policies, checking MCP tool performance, or ensuring Supabase operational standards. Triggers on:

Backend
27109

scientific-writing

by K-Dense-AI

Write scientific manuscripts. IMRAD structure, citations (APA/AMA/Vancouver), figures/tables, reporting guidelines (CONSORT/STROBE/PRISMA), abstracts, for research papers and journal submissions.

Backend
47191

architecture-decision-records

by wshobson

Write and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation. Use when documenting significant technical decisions, reviewing past architectural choices, or establishing decision processes.

Backend
29130