What problem does it solve? Building backend endpoints in an Appflare project requires knowing the exact handler conventions: which helper to use, how file paths map to routes and client names, how Zod args are validated, and how auth, errors, background jobs, and R2 storage rules behave. This Skill encodes those conventions so generated handlers are discovered correctly and behave as expected. ## Core Features & Use Cases - Endpoint authoring: Create query (GET) and mutation (POST) handlers with Zod args, authRequired, middleware role checks, and ctx.error responses that map cleanly to HTTP status codes. - Background and scheduled work: Define scheduler tasks enqueued via ctx.scheduler.enqueue with optional delays, and cron handlers with literal cron triggers, including naming rules and no-retry semantics. - Storage authorization: Write storageManager rules that gate R2 access for ctx.storage calls and the generated /storage/* routes, which are denied by default. - Use Case: You need a new endpoint that lets admins list a project's tasks and a nightly job that cleans expired sessions. The Skill guides you to export listTasks = query({...}) in the right file, add a cron handler with a literal trigger, and run bun appflare dev to confirm discovery. ## Quick Start Ask the agent to create an Appflare query handler that lists a project's tasks with auth required, then run bun appflare dev to verify it is discovered.
