backend-worker

Automate Supabase edge function scaffolding, testing, and deployment workflows.

2|1|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/passionseed/ps_app --skill backend-worker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backend-worker
Source: https://github.com/passionseed/ps_app/tree/main/.factory/skills/backend-worker
Command: npx skills add https://github.com/passionseed/ps_app --skill backend-worker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill encapsulates the end-to-end workflow for building, deploying, and maintaining Supabase edge functions and associated client libraries, reducing manual boilerplate and deployment drift.

Core Features & Use Cases

  • Edge function scaffolding, pattern alignment, and deployment automation for Supabase projects.
  • Client library development and integration with serverless backends, including tests and type checks.
  • End-to-end deployment workflow, including testing, linting, and continuous integration readiness.

Quick Start

Create and deploy a new backend-worker workflow to scaffold edge functions and client libraries for your Supabase project.

Frequently Asked Questions about backend-worker

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

FAQPage Schema
How do I automate Supabase edge function deployment and client library integration?

It supports an end-to-end workflow covering edge function scaffolding, client library development, and deployment procedures with build-time testing and type checking. This reduces manual boilerplate and deployment drift for Supabase projects.

What is the best way to scaffold edge functions and manage client library releases?

The best way to scaffold edge functions and manage client library releases is through a unified workflow that aligns patterns and automates deployment. This includes linting and continuous integration readiness to prevent deployment drift across distributed teams.

Can I use this workflow for teams building serverless backends and distributed client libraries?

Yes, this workflow is specifically applicable to teams building serverless backends and distributed client libraries. It provides reliable deployment pipelines, API integration support, and continuous integration readiness.

Does the edge function deployment workflow include build-time testing and type checking?

Yes, the edge function deployment workflow includes build-time testing and type checking. It ensures continuous integration readiness by automating tests, linting, and type checks before deploying Supabase edge functions and client libraries.

Why does manual boilerplate cause deployment drift in serverless backend projects?

Manual boilerplate causes deployment drift in serverless backend projects because it relies on inconsistent, repetitive setup across edge functions and client libraries. Automating the end-to-end workflow standardizes patterns and reduces these discrepancies.

What are the limitations of manual edge function scaffolding compared to an automated workflow?

Manual edge function scaffolding lacks continuous integration readiness, automated type checking, and standardized pattern alignment. An automated workflow resolves these limitations by enforcing build-time testing and reliable deployment pipelines across the project.