What problem does it solve? Mobile apps often need server-side logic to hide API keys, proxy third-party services like OpenAI or Stripe, receive webhooks, and validate data — but standing up a separate backend is heavy. This Skill guides you through writing Expo Router API routes (+api.ts) and deploying them together with your web bundle to EAS Hosting, Expo's managed edge runtime on Cloudflare Workers. ## Core Features & Use Cases - API Route Authoring: Create +api.ts endpoints with GET/POST/PUT/DELETE handlers, dynamic routes, query params, headers, JSON bodies, CORS, and error handling. - Secret Management: Keep OpenAI, Stripe, and database credentials server-side via process.env and eas env:create, never in client code. - Deployment Workflow: Export with npx expo export -p web, deploy previews and production with eas deploy, and automate via EAS Workflows on push or pull request. - Edge Runtime Guidance: Work within Cloudflare Workers constraints (no Node fs, 30s CPU limit) using Web APIs and cloud databases like Turso, D1, or Supabase. - Use Case: You need to call the OpenAI API from your Expo app without exposing the key — create app/api/ai+api.ts as a proxy endpoint, set the secret with eas env:create, and deploy with eas deploy --prod. ## Quick Start Ask the assistant to create an Expo Router API route that proxies requests to OpenAI with the key stored as an environment variable, then deploy it to EAS Hosting production.
