lovable-cloud-edge-functions

Enforces tier-specific verify_jwt and authentication rules for Supabase Edge Functions in Lovable Cloud projects.

4|1|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/jcdendrite/claude-config --skill lovable-cloud-edge-functions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lovable-cloud-edge-functions
Source: https://github.com/jcdendrite/claude-config/tree/main/plugins/lovable-cloud/skills/lovable-cloud-edge-functions
Command: npx skills add https://github.com/jcdendrite/claude-config --skill lovable-cloud-edge-functions

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It prevents misconfigured Supabase Edge Functions in Lovable Cloud that could accidentally expose browser-invoked endpoints or weaken defense-in-depth around service-role and webhook access control.

Core Features & Use Cases

  • Auth tier guidance for Edge Functions: Enforces a clear mapping between caller type (browser, service role/cron, external webhook, or intentionally public) and the required verify_jwt behavior.
  • config.toml security guardrails: Provides strict rules so every edge function has an explicit functions.<name> section and avoids risky bulk changes.
  • In-code authentication requirements: Ensures Tier 1 relies on cryptographic user JWT validation (since gateway verification cannot apply) and Tier 2 includes both gateway verification and role-claim validation.
  • Webhook signature verification correctness: Reduces HMAC verification failures by requiring raw-body consumption before any other body read.
  • Deployment awareness for Lovable: Clarifies that Lovable does not auto-deploy external changes, and instructs how to request deployment for new/modified functions and verify_jwt updates.

Quick Start

Update your Supabase supabase/config.toml and edge function code to match the tier-based verify_jwt and in-code auth requirements described in this skill, then explicitly ask Lovable to deploy the affected edge functions.

Frequently Asked Questions about lovable-cloud-edge-functions

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

FAQPage Schema
How do I configure verify_jwt for Supabase Edge Functions in Lovable?

Configuring verify_jwt requires adding explicit functions.<name> sections in supabase/config.toml for each edge function, ensuring browser-invoked functions enforce cryptographic JWT validation while service callers enforce role-claim validation.

What is the correct way to verify webhook signatures in Supabase Edge Functions?

Verifying webhook signatures correctly requires consuming the raw request body before any other body read to perform HMAC verification, preventing signature validation failures caused by body parsing alterations.

Why are my Supabase Edge Function authentication changes not deploying in Lovable?

Edge Function changes are not deploying because Lovable does not auto-deploy external modifications; you must explicitly request deployment for new or modified functions and verify_jwt updates after changing config.toml.

Does Supabase gateway JWT verification apply to all edge function tiers?

Gateway JWT verification does not apply to browser-invoked Tier 1 functions, which require in-code cryptographic user JWT validation, whereas Tier 2 service callers require both gateway verification and role-claim validation.

Can I use bulk verify_jwt settings in supabase config.toml for Lovable Cloud projects?

Bulk verify_jwt settings in config.toml are discouraged for Lovable Cloud projects; you must define strict per-function functions.<name> entries to avoid accidentally exposing browser-invoked endpoints or weakening access control.