What problem does it solve? Browser-to-backend calls in DaaS applications fail with CORS errors and missing session cookies when client components call Supabase Auth or the DaaS backend directly. This Skill enforces a same-origin proxy architecture so authentication and data requests work reliably. ## Core Features & Use Cases - Proxy Route Enforcement: Mandates that all login, logout, user lookup, and data API calls go through Next.js API routes like /api/auth/login and /api/items/* instead of direct cross-origin calls. - Correct Auth Patterns: Provides copy-ready code for login, logout, protected layouts, and server-side JWT forwarding via the getAuthHeaders helper. - External OAuth Support: Documents SSO flows for Azure AD, Okta, Auth0, and Google through /api/auth/oauth/[provider] routes. - Use Case: When building a login page for a Buildpad-generated app, use this Skill to implement the fetch call to /api/auth/login with credentials included, avoiding the common mistake of calling supabase.auth.signInWithPassword directly from the browser. ## Quick Start Ask the AI to implement a login page that authenticates through the /api/auth/login proxy route instead of calling Supabase directly from the client.
