resonate-lovable-usage-prompt-typescript

What problem does it solve?

This skill eliminates the friction of running durable Resonate workflows inside the Lovable.dev environment by describing patterns to delegate execution to external Resonate servers and workers while using Lovable as the UI and HTTP client. It clarifies when you must avoid local long-running processes in Lovable, how to treat Resonate as the source of truth for workflow state, and when a separate database is truly necessary.

Core Features & Use Cases

• Architecture guidance for using Lovable as a frontend and control plane while hosting Resonate workers on Cloud Run, Fly.io, Railway, or similar platforms.
• Protocol guidance for when to use the Resonate SDK versus the HTTP API: start workflows with beginRpc when execution is required and use the promises endpoints to query or resolve state from the Lovable backend.
• Human-in-the-loop patterns showing how external workers create approval promises, notify the Lovable backend, and accept resolution actions from Lovable UIs.
• Practical deployment and integration tips including recommended timeout semantics (absolute epoch milliseconds), base64-encoded payload conventions, and Supabase integration for optional UI state tracking.

Quick Start

Deploy an external Resonate server and worker, configure your Lovable backend to invoke beginRpc for starting workflows and use the Resonate HTTP promises endpoints to list and resolve approvals.