skills.rest
yaresimeonthomas
yaresimeonthomasCOMMUNITY
Explore all skills by this author →
GitHub

backend-dev

Configure Supabase migrations, RLS policies, and edge functions for Atomic CRM.

Updated Jul 1, 2026
Search Tags:#supabase#crm#access-control#edge-functions#database-migrations#backend-development#rls-policies
One-click install
npx skills add https://github.com/yaresimeonthomas/-kate-crm --skill backend-dev-yaresimeonthomas
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: backend-dev
Source: https://github.com/yaresimeonthomas/-kate-crm/tree/main/.claude/skills/backend-dev
Command: npx skills add https://github.com/yaresimeonthomas/-kate-crm --skill backend-dev-yaresimeonthomas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Atomic CRM relies entirely on Supabase for all server-side logic with no custom backend server, creating risks of inconsistent database changes, security gaps in RLS policies, and misconfigured edge functions if developers do not follow standardized conventions. This skill eliminates those risks by providing clear, actionable guidance for all backend-related tasks.

Core Features & Use Cases

  • Backend Logic Decision Framework: Helps developers quickly determine if a change requires server-side logic or can be handled frontend-only, reducing unnecessary backend work.
  • Supabase Implementation Standards: Provides explicit rules for creating database migrations, views, triggers, RLS policies, and edge functions to ensure consistency across the codebase.
  • Security Guardrails: Includes critical, security-focused rules to prevent common vulnerabilities like privilege escalation via misconfigured WITH CHECK clauses, under-counting row limits for quotas, and incorrect edge function middleware ordering. Use case: When adding a new custom table to Atomic CRM to track customer support tickets, this skill guides you to add the required RLS policies, auto-set sales_id trigger, and avoid security pitfalls when enforcing per-user ticket limits.

Quick Start

Use the backend-dev skill to review your planned Supabase RLS policy for a new custom table to confirm it follows all required security and convention rules.

Frequently Asked Questions about backend-dev

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure Supabase RLS policies to avoid privilege escalation in a serverless CRM?▼

Supabase RLS policies require properly configured WITH CHECK clauses to prevent privilege escalation. This skill provides explicit security guardrails for RLS policy configuration, ensuring your serverless CRM backend avoids common vulnerabilities like misconfigured access control and under-counting row limits.

What's the best way to structure Supabase database migrations for Atomic CRM?▼

The best way to structure Supabase database migrations is by following standardized conventions for creating views, triggers, and RLS policies. This skill provides explicit implementation standards to ensure database migration consistency across the Atomic CRM codebase.

When do I need a Supabase edge function versus frontend-only logic for CRM features?▼

You need a Supabase edge function when server-side logic is required for secure data processing or custom dataProvider methods. This skill offers a backend logic decision framework to help determine if a change requires edge function development or can be handled frontend-only.

How do I enforce per-user ticket limits in Supabase without under-counting rows?▼

Enforcing per-user ticket limits in Supabase requires careful RLS policy configuration to avoid under-counting rows for quotas. This skill includes critical security-focused rules to prevent miscounted row limits and other common vulnerabilities in access control.

Does this Supabase backend guidance work for custom tables beyond the default Atomic CRM schema?▼

Yes, this Supabase backend guidance applies to custom tables like customer support tickets. It directs you to add required RLS policies, auto-set sales_id triggers, and follow edge function middleware patterns, ensuring secure integration with the existing Atomic CRM architecture.

Why are my Supabase edge functions failing due to middleware ordering?▼

Supabase edge functions fail when middleware ordering is incorrect. This skill enforces standardized edge function middleware patterns, providing explicit rules to prevent misconfigured middleware and ensure consistent serverless architecture execution.

Related Skills

Explore More Software Engineering Skills→
jclfocusedjclfocused
2

supabase-local

Manage local Supabase environments with custom ports and migrations.

Community
Intermediate
Yanick-mjYanick-mj

mb-be-dev

Implement backend migrations, APIs, edge functions, and RLS policies with test-driven code.

Community
Advanced
git-taogit-tao

supabase

Integrate Supabase services for PostgreSQL, authentication, storage, real-time subscriptions, and edge functions.

Community
Intermediate
xoaixoai
25

baas

Correct BaaS architectural mistakes in Firebase and Supabase apps.

Community
Advanced