05-ENRICH-edge

Evaluate necessity and compare implementation approaches for Supabase edge functions.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/medtrics/medtrics-acumen --skill 05-enrich-edge
Or copy as Structured Prompt for Agentโ–ผ
Please help me install this Agent Skill.
Skill: 05-ENRICH-edge
Source: https://github.com/medtrics/medtrics-acumen/tree/main/templates/shared/skills/05-ENRICH-edge
Command: npx skills add https://github.com/medtrics/medtrics-acumen --skill 05-enrich-edge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill rigorously evaluates the need for edge functions in Supabase projects, ensuring they are only implemented when truly necessary and guiding the selection of the most appropriate approach.

Core Features & Use Cases

  • Necessity Gate: Filters out edge functions that can be handled by simpler means (client-side, DB functions).
  • Approach Analysis: Compares three distinct implementation strategies for essential edge functions, evaluating them across key dimensions.
  • Decision Framework: Provides a clear recommendation based on a scoring system and justification.
  • Use Case: When planning a new feature that involves user authentication and data validation, this Skill helps determine if a new edge function is required, or if existing Supabase features like RLS and database functions suffice.

Quick Start

Analyze the necessity and approach for a proposed 'user-profile-update' edge function.

Frequently Asked Questions about 05-ENRICH-edge

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

FAQPage Schema
Do I need Supabase edge functions for multi-table transactions and secret access?โ–ผ

Determining if you need edge functions involves validating requirements like multi-table transactions, secret access, heavy computation, or scheduled jobs against simpler alternatives like DB functions or client-side orchestration.

What is the best way to implement a Supabase edge function?โ–ผ

The best approach is determined by comparing DB Functions (RPC), minimal or full Edge Functions, client-side orchestration, and hybrid models across simplicity, scalability, maintainability, testability, and operational cost.

How do I decide between using Supabase RPC and edge functions for backend development?โ–ผ

Deciding between Supabase RPC and edge functions involves analyzing a proposed feature's necessity and comparing implementation approaches via a scoring system that evaluates simplicity, scalability, maintainability, testability, and operational cost.

When should I avoid using edge functions in my Supabase architecture?โ–ผ

You should avoid edge functions when proposed features can be handled by simpler means like client-side logic, Row Level Security, or database functions, failing the necessity gate for heavy computation or scheduled jobs.

How does a decision framework evaluate serverless API design approaches?โ–ผ

A decision framework evaluates serverless API design approaches by scoring three distinct implementation strategies across maintainability, testability, and operational cost, providing a clear recommendation and justification for edge functions.