mcpField
A
auth-implementation-patterns

auth-implementation-patterns

github.com/rmyndharisSecurity1.9k103 installsUpdated 2w ago
Repository

About auth-implementation-patterns

auth-implementation-patterns is a skill for developers building authentication and authorization systems. It guides choices around identity flows, policy enforcement, token lifecycle, and credential safety.

Key features

  1. 01Authentication strategy selection
  2. 02Authorization model design
  3. 03Token lifecycle planning
  4. 04Secrets and audit guidance
  5. 05Implementation playbook reference

Use cases

  1. 01Adding OAuth2, social login, or SSO
  2. 02Securing REST or GraphQL APIs
  3. 03Designing sessions or RBAC
  4. 04Troubleshooting access control

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/rmyndharis/antigravity-skills --skill auth-implementation-patterns

After installing, type/auth-implementation-patternsin Claude Code to confirm it loaded.

Bundled filesresources/implementation-playbook.md

Details

From the project README

Authentication & Authorization Implementation Patterns

Build secure, scalable authentication and authorization systems using industry-standard patterns and modern best practices.

Use this skill when

  • Implementing user authentication systems
  • Securing REST or GraphQL APIs
  • Adding OAuth2/social login or SSO
  • Designing session management or RBAC
  • Debugging authentication or authorization issues

Do not use this skill when

  • You only need UI copy or login page styling
  • The task is infrastructure-only without identity concerns
  • You cannot change auth policies or credential storage

Instructions

  • Define users, tenants, flows, and threat model constraints.
  • Choose auth strategy (session, JWT, OIDC) and token lifecycle.
  • Design authorization model and policy enforcement points.
  • Plan secrets storage, rotation, logging, and audit requirements.
  • If detailed examples are required, open resources/implementation-playbook.md.

Safety

  • Never log secrets, tokens, or credentials.
  • Enforce least privilege and secure storage for keys.

Resources

  • resources/implementation-playbook.md for detailed patterns and examples.

Comments

Markdown supported