agentleFS
Ampli-GroupAmpli-Group/agentic-mobile-blueprint/.agents/skills/edge-functions/SKILL.md

edge-functions

Skill4 starsChanged 6 months agoMITView on GitHub

Supabase Edge Function development patterns with Deno runtime. Use when creating, modifying, or debugging edge functions. For Langfuse tracing see the langfuse-tracing skill. For Sentry error handling see the sentry-integration skill.

  • Reads credentials

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Add updated_at trigger for mutable tables

    line 62

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Supabase Edge Functions

Runtime

Deno. Entry point: Deno.serve(). Files live in supabase/functions/<name>/index.ts.

New Function Scaffold

import { initSentry, handleError } from "../_shared/sentry.ts";

initSentry();

const corsHeaders = {
  "Access-Control-Allow-Origin": "*",
  "Access-Control-Allow-Headers": "authorization, x-client-info, apikey, content-type",
};

Deno.serve(async (req: Request) => {
  if (req.method === "OPTIONS") return new Response("ok", { headers: corsHeaders });

  try {
    const body = await req.json();
    const result = { message: "Hello" };
    return new Response(JSON.stringify(result), {
      headers: { ...corsHeaders, "Content-Type": "application/json" },
    });
  } catch (error) {
    return handleError(error, { functionName: "my-function", corsHeaders });
  }
});

For AI calls, wrap with withTrace() — see the langfuse-tracing skill.

Imports

  • Shared code: ../_shared/sentry.ts, ../_shared/langfuse/gemini.ts
  • External: via import map in supabase/functions/deno.json
  • Convention: npm: prefix for npm packages, URLs for Deno packages

Calling from Frontend/Mobile

const { data, error } = await supabase.functions.invoke('my-function', {
  body: { prompt: 'Hello' },
});

Database Migrations

Path: supabase/migrations/. Naming: 00000000000000_slug.sql.

Rules:

  • Enable RLS on every table
  • Policies use auth.uid() for row-level access
  • Add updated_at trigger for mutable tables
  • Index foreign keys and common filter columns
  • Storage bucket policies: auth.uid()::text = (storage.foldername(name))[1]

Local Development

mise run supabase:function   # Starts functions with hot reload

Env vars for functions go in supabase/functions/.env.local.

Deploy

supabase functions deploy <function-name>

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.