standard-security-auth
Security & Authentication Specialist - Expert in JWT, cookie-based auth, MFA, and generic security patterns
When & Why to Use This Skill
This Claude skill serves as a specialized Security & Authentication expert, streamlining the implementation of robust identity management systems. It provides deep technical guidance on JWT and cookie-based authentication, multi-factor authentication (MFA) flows, and secure API integration using Backend-for-Frontend (BFF) proxy patterns. By automating security reviews and enforcing best practices in middleware and role-based access control (RBAC), it ensures application integrity and audit compliance.
Use Cases
- Implementing Secure Auth Flows: Designing and coding JWT or cookie-based authentication mechanisms with proper middleware protection and session management.
- Security Vulnerability Auditing: Reviewing codebases for common security pitfalls such as hardcoded credentials, unencrypted local storage, or misconfigured CSP headers.
- RBAC & MFA Integration: Configuring complex role-based access controls and secondary verification steps for sensitive administrative actions and protected routes.
- Secure API Proxying: Establishing secure communication between frontend components and backend services using authenticated API clients and standardized proxy architectures.
- Compliance & Event Logging: Implementing standardized audit logging for security-critical events like token refreshes, login failures, and unauthorized access attempts.
| name | standard-security-auth |
|---|---|
| description | Security & Authentication Specialist - Expert in JWT, cookie-based auth, MFA, and generic security patterns |
| last_updated | 2025-12-27 |
Security & Authentication Specialist
Overview
An expert agent specializing in the project's authentication system, security patterns, and API integration. This agent understands JWT, cookie-based, and multi-factor authentication flows, as well as proxy architectures for secure backend communication.
When To Use
- Authentication Implementation: When implementing or modifying auth flows
- Security Review: When reviewing code for security vulnerabilities
- API Integration: When connecting new features to the auth system
- MFA/Role-based Logic: When working with multi-factor authentication or role-based access
- Audit Compliance: When ensuring code follows audit logging requirements
Instrumentation
# Log usage when using this skill
./scripts/log-skill.sh "standard-security-auth" "manual" "$$"
What do you want to do?
- Implement Authentication Flow → See "Auth Flow Patterns" below
- Review Security Vulnerabilities → See "Security Checklist" below
- Connect API to Auth System → See "API Integration" below
- MFA/Role-based Access → See "Role Management" below
- Audit & Compliance → See "Audit Patterns" below
Auth Flow Patterns
Cookie-Based Authentication
- Use the standard API client for calls that require authentication
- Never manually attach Authorization headers in cookie mode
- The middleware automatically handles JWT validation and refresh
- Session state is maintained in a centralized
AuthContext
JWT Token Management
- Tokens are stored in HttpOnly cookies for security
- Middleware handles proactive refresh before expiration
- Multi-Factor Authentication (MFA) sessions require secondary verification
- Role-based access is enforced at both middleware and component levels
Security Checklist
Critical Security Checks
- All API calls use the canonical API client
- No hardcoded API URLs or fallbacks (use environment variables)
- Middleware route protection is properly configured
- Role-based access control is enforced at both frontend and backend
- No sensitive data is stored in unencrypted local storage
- Content Security Policy (CSP) headers are properly applied
API Integration
Proxy Architecture
The application uses a Backend for Frontend (BFF) proxy pattern:
// Correct way to make authenticated API calls
import { fetchWithAuth } from '@/lib/apiClient';
const response = await fetchWithAuth('/api/resource/data');
Role Management
Role Definitions
admin: Full administrative access, typically requires MFAuser: Standard access to personal/assigned resources
Route Protection
Routes are typically configured in middleware.ts:
- Public routes: Login, callback, and landing pages
- Protected routes: Administrative and user dashboard routes
Audit Patterns
Security Event Logging
All security-relevant events must be logged:
- Token refresh events
- Login/logout success and failure
- Role access violations
- Critical data modifications
Common Pitfalls & Solutions
Pitfall: Guest State Handling
- ❌ WRONG: Auth status endpoint returns 401 for unauthenticated users (causes browser noise)
- ✅ CORRECT: Auth status endpoint returns 200 with
{ authenticated: false }
Pitfall: Duplicate API Calls
- ❌ WRONG: Session initialization called multiple times outside of controlled effects
- ✅ CORRECT: Use controlled effects with proper guards to prevent duplicate calls
Troubleshooting
Debugging Authentication Issues
- Check browser cookies for valid auth tokens
- Verify the token is a properly formatted JWT
- Check middleware logs for route protection decisions
- Confirm user role matches expected access level