Name: Serverless Patterns
Author: mauriciosepulveda-max

"Firebase Functions are your backend. Design them like microservices, deploy them like magic."

Purpose

Fan-out (Firestore trigger to multiple ops). Saga (compensating transactions). Event sourcing with Firestore. When to use: Backend development within Firebase/Google ecosystem.

1. The Physics

Law of Functions: Each Cloud Function does ONE thing. Single responsibility.
Law of Cold Start: Minimize dependencies. Use lazy imports. Set min instances for critical functions.
Law of Security: Every HTTP function verifies Firebase ID tokens. No public endpoints without auth.

2. The Protocol

Phase 1: Design

Map requirements to Cloud Functions triggers (HTTP, Firestore, Auth, Storage, scheduled).

"Firebase Functions are your backend. Design them like microservices, deploy them like magic."

Purpose

Fan-out (Firestore trigger to multiple ops). Saga (compensating transactions). Event sourcing with Firestore. When to use: Backend development within Firebase/Google ecosystem.

1. The Physics

Law of Functions: Each Cloud Function does ONE thing. Single responsibility.
Law of Cold Start: Minimize dependencies. Use lazy imports. Set min instances for critical functions.
Law of Security: Every HTTP function verifies Firebase ID tokens. No public endpoints without auth.

2. The Protocol

Phase 1: Design

Map requirements to Cloud Functions triggers (HTTP, Firestore, Auth, Storage, scheduled).

Input	Type	Required	Description
Requirements	Text/Spec	Yes	What the function does
Output	Type	Description
--------	------	-------------
Cloud Function code	TypeScript	Deployable function

Serverless Patterns

Purpose

1. The Physics

2. The Protocol

Phase 1: Design

Serverless Patterns

Purpose

1. The Physics

2. The Protocol

Phase 1: Design

Phase 2: Implement

Phase 3: Test + Deploy

3. Inputs / Outputs

4. Quality Gates

5. Self-Correction Triggers

Prose

Golang Patterns

Audiocraft Audio Generation

Pokemon Player

Ideation

Storybook Upgrade