What problem does it solve?
Atomic CRM relies entirely on Supabase for server-side logic, so developers need clear, consistent guidelines to implement backend changes safely and avoid common security vulnerabilities like privilege escalation, quota bypass, and data leaks from misconfigured RLS policies or edge functions.
Core Features & Use Cases
- Backend Logic Decision Framework: Guides developers on when to implement backend changes versus using frontend-only custom dataProvider methods for Atomic CRM features.
- Supabase Implementation Standards: Defines conventions for database migrations, RLS policies, edge functions, and maintenance of summary views like contacts_summary and companies_summary.
- Critical Security Guardrails: Highlights high-risk pitfalls (e.g., insecure RLS policies, misconfigured edge function middleware) and provides a verification checklist to avoid vulnerabilities.
Use Case: When adding a new customer subscription tracking feature to Atomic CRM, this skill ensures you implement secure quota-enforcing triggers, proper RLS policies, and correctly ordered edge function middleware to prevent billing bypasses and unauthorized data access.
Quick Start
Use the backend-dev skill to implement a secure RLS policy for the new customer subscriptions table that restricts row access to the owning sales user and prevents unauthorized modification of sensitive columns like subscription status and billing amounts.
