What problem does it solve? Fusebase apps sometimes need server-side logic beyond the client-side Dashboard SDK, such as custom REST endpoints, WebSocket push, scheduled jobs, or secret-bearing operations, and this Skill guides when and how to add that backend correctly. ## Core Features & Use Cases - Backend Scaffolding: Sets up a backend/ folder with its own package.json using Hono, tsx, and tsup, keeping backend dependencies out of the SPA bundle. - API Contract Management: Maintains openapi.json as the published API contract with x-fusebase-visibility and x-fusebase-execution-mode metadata for registry discovery. - Sidecars & Resource Budgets: Adds Docker sidecar containers (Chromium, Redis) while respecting the 2.0 CPU / 4 Gi total revision cap. - Auth & Webhooks: Handles service-account tokens, magic-link session exchange, webhook registration, cold starts, and multi-user state partitioning. - Use Case: When building an app that must receive Stripe webhooks and write to an isolated store, use this Skill to configure backend.minReplicas: 1, a secret webhook path, and the correct FBS_FEATURE_TOKEN transport. ## Quick Start Ask the AI to add a Hono backend with a REST endpoint and update openapi.json for my Fusebase app.
