What problem does it solve? Wiring login, signup, silent refresh, and logout against the Overlens Identity Provider involves many subtle failure points — PKCE generation, state validation, exact redirect_uri matching, cookie maxAge unit bugs, and refresh token rotation. This Skill gives developers copy-paste templates and framework-specific guides so the integration is correct on the first pass. ## Core Features & Use Cases - Framework-specific templates: Ready-to-copy handlers for Next.js App Router (Server Actions and Route Handlers), NestJS BFF, and Express/Hono/Fastify, plus a generic guide for Rails, Django, ASP.NET, and other server-side frameworks. - Complete OAuth flow coverage: PKCE generation, login/signup redirects, callback code exchange with Basic Auth, silent refresh with token rotation, and OIDC RP-Initiated Logout via the end_session_endpoint. - Pitfall and troubleshooting references: A symptom-to-cause-to-fix guide covering redirect_uri mismatches, maxAge unit bugs, state validation failures, and refresh token reuse. - Use Case: A developer with a NestJS backend copies the auth controller and IDP client service templates, sets six environment variables, and has working Overlens login, refresh, and logout in one session. ## Quick Start Ask the assistant to integrate Overlens login into your web backend, mentioning your framework such as Next.js, NestJS, or Express.