Select OAuth 2.x/OIDC authentication flows by client type and constraints.
npx skills add https://github.com/vTRKA/supervibe --skill auth-flow-design
Please help me install this Agent Skill. Skill: auth-flow-design Source: https://github.com/vTRKA/supervibe/tree/main/skills/auth-flow-design Command: npx skills add https://github.com/vTRKA/supervibe --skill auth-flow-design
This Skill prevents insecure or incompatible authentication implementations by forcing a deliberate OAuth 2.1 / OIDC flow choice before writing auth code.
Tell the AI tool which app and clients you are building, then ask it to design your authentication authorization flow with redirect URIs, PKCE, refresh rotation, storage, and logout steps.
High-intent search queries and answers about installing and using this skill.
Choosing the correct OAuth 2.x or OIDC authentication flow requires evaluating your client type and runtime constraints to select authorization-code with PKCE, client-credentials, or device authorization, while rejecting risky mismatches like ROPC.
Handling refresh token rotation and storage involves defining secure boundaries between cookie and token storage, ensuring proper rotation, and coordinating logout across SPA, mobile, API, and IdP environments.
Yes, the authorization code flow with PKCE is the recommended approach for new SPA and API authentication design, preventing insecure token storage in localStorage by enforcing safer client-specific flow selection.
Logout coordination works by defining explicit logout steps that synchronize session termination across SPA, mobile, API, and IdP, ensuring tokens are invalidated and users are fully logged out from all client runtimes.
Avoiding the ROPC flow and token storage in localStorage during OAuth modernization is necessary because they introduce severe security risks, prompting the selection of safer alternatives like authorization-code with PKCE and secure cookie boundaries.
Producing an authentication design handoff with confidence gating requires reading relevant standards, inventorying existing grant and client configuration, and validating evidence to output a PASS, PARTIAL, or BLOCKED status.
panaversityConfigure an application as an OIDC/OAuth issuer with Better Auth 1.6.x.
manutejImplement OAuth2 and OpenID Connect flows with PKCE and token management.
salavenderImplement JWT, cookie, and MFA authentication workflows with RBAC and audit logging.
JaganproConfigure Salesforce Connected Apps and External Client Apps with OAuth security policies.
