platform-auth

Implements authentication and authorization patterns using JWT, OAuth2, RBAC, and managed auth services.

3|2|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/Yoodaddy0311/artibot --skill platform-auth-yoodaddy0311
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: platform-auth
Source: https://github.com/Yoodaddy0311/artibot/tree/main/plugins/artibot/skills/platform-auth
Command: npx skills add https://github.com/Yoodaddy0311/artibot --skill platform-auth-yoodaddy0311

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Designing secure authentication and authorization is error-prone, and mistakes like weak password hashing, non-expiring tokens, or missing CSRF protection become real vulnerabilities. This Skill provides vetted patterns for login flows, token lifecycle, access control, and managed auth integrations so you avoid common security pitfalls. ## Core Features & Use Cases - Strategy Selection: Compare JWT, session cookies, OAuth2/OIDC, and passkeys to pick the right authentication model for your architecture. - Managed Auth Integration: Guidance for Auth0, Clerk, and Firebase Auth including SDK choices and integration patterns. - Token & Session Security: Best practices for access/refresh token rotation, httpOnly cookie storage, revocation lists, and CSRF protection. - Use Case: When building a Next.js SaaS app, use this Skill to choose between Auth0 and Clerk, implement Authorization Code + PKCE flow, and design a permission-based RBAC model with hierarchical roles. ## Quick Start Ask the AI to design an authentication flow with OAuth2 and role-based access control for your web application.

Frequently Asked Questions about platform-auth

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose between JWT and session cookies for authentication?▼

JWT suits API-first and microservice architectures with stateless token-based auth, while session cookies fit traditional server-rendered web apps with lower complexity. The Skill provides a comparison table covering complexity and session type for each strategy.

Auth0 vs Clerk: which managed auth service should I use?▼

Auth0 fits enterprise SSO needs with extensive customization via Actions and Rules, while Clerk targets modern Next.js apps with prebuilt UI components and middleware-based auth. Firebase Auth is better for mobile-first apps in the Google ecosystem.

Where should I store JWT tokens in a single-page application?▼

Store access tokens in memory or short-lived httpOnly cookies, and refresh tokens in httpOnly, secure, sameSite=strict cookies. Never use localStorage or sessionStorage because they are vulnerable to XSS attacks.

Is PKCE required for OAuth2 in mobile and SPA apps?▼

Yes, PKCE is mandatory for all public clients including SPAs and mobile apps using the Authorization Code flow. It prevents authorization code interception attacks without requiring a client secret.

When should I not use this authentication guidance?▼

Skip it for public read-only routes or internal tooling with no access control requirements. The Skill explicitly excludes features that have no authentication or permission boundary.