skills/security-auth/SKILL.md
Comprehensive security and authentication workflow that orchestrates security architecture, identity management, access control, and compliance implementation. Handles everything from authentication system design and authorization frameworks to security auditing and threat protection.
npx skillsauth add ajianaz/skills-collection security-authInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
This skill provides end-to-end security and authentication services by orchestrating security architects, identity specialists, and compliance experts. It transforms security requirements into production-ready authentication and authorization systems with comprehensive threat protection, compliance adherence, and security monitoring.
Key Capabilities:
Perfect for:
Triggers:
Use when: Starting security implementation or security assessment
Tools Used:
/sc:analyze security-requirements
Security Architect: threat modeling and risk assessment
Compliance Expert: regulatory requirement analysis
Threat Analyst: attack surface analysis
Activities:
Use when: Designing and implementing authentication systems
Tools Used:
/sc:design --type authentication auth-system
Identity Specialist: authentication framework design
Cryptographic Specialist: secure credential management
Security Architect: authentication security controls
Activities:
Use when: Implementing authorization and access control systems
Tools Used:
/sc:design --type authorization rbac-system
Identity Specialist: role-based access control implementation
Security Architect: privilege management design
Compliance Expert: access control auditing
Activities:
Use when: Integrating security controls and protecting APIs
Tools Used:
/sc:implement security-integration
Security Architect: API security and integration
Cryptographic Specialist: encryption and data protection
Threat Analyst: input validation and sanitization
Activities:
Use when: Ensuring regulatory compliance and security auditing
Tools Used:
/sc:implement compliance-auditing
Compliance Expert: compliance framework implementation
Security Architect: security monitoring and logging
Threat Analyst: audit trail and forensics
Activities:
Use when: Setting up proactive threat detection and response
Tools Used:
/sc:implement threat-protection
Threat Analyst: security monitoring and detection
Security Architect: incident response procedures
Compliance Expert: security metrics and reporting
Activities:
| Command | Use Case | Output |
|---------|---------|--------|
| /sc:design --type authentication | Authentication system | Complete auth architecture |
| /sc:design --type authorization | Authorization framework | RBAC/ABAC implementation |
| /sc:implement security | Security controls | Production-ready security |
| /sc:analyze threats | Threat analysis | Threat model and mitigation |
| /sc:implement compliance | Compliance | Regulatory compliance system |
| Framework | Role | Capabilities | |-----------|------|------------| | OWASP Top 10 | Security standards | Comprehensive vulnerability protection | | NIST Cybersecurity | Security framework | Complete security program implementation | | ISO 27001 | Compliance management | Information security management system | | Zero Trust | Security model | Zero-trust architecture implementation |
| Server | Expertise | Use Case | |--------|----------|---------| | Sequential | Security reasoning | Complex security analysis and design | | Better Auth | Authentication | Modern authentication implementation | | Web Search | Threat intelligence | Latest security threats and vulnerabilities |
User: "Implement a secure authentication system for our SaaS application with MFA and SSO support"
Workflow:
1. Phase 1: Analyze security requirements and compliance needs
2. Phase 2: Design OAuth 2.0/OpenID Connect authentication system
3. Phase 3: Implement RBAC with fine-grained permissions
4. Phase 4: Integrate with SSO providers and MFA services
5. Phase 5: Set up audit logging and compliance reporting
6. Phase 6: Implement threat detection and security monitoring
Output: Production-ready authentication system with enterprise-grade security
User: "Implement SOC 2 compliance for our financial services platform"
Workflow:
1. Phase 1: Analyze SOC 2 requirements and current security posture
2. Phase 2: Design security controls to meet SOC 2 criteria
3. Phase 3: Implement access controls and audit trails
4. Phase 4: Set up security monitoring and incident response
5. Phase 5: Create compliance documentation and reporting
6. Phase 6: Implement continuous compliance monitoring
Output: SOC 2 compliant security framework with comprehensive audit capabilities
User: "Secure our REST API with proper authentication, authorization, and threat protection"
Workflow:
1. Phase 1: Analyze API security requirements and threat model
2. Phase 2: Design JWT-based authentication and authorization
3. Phase 3: Implement API gateway with security controls
4. Phase 4: Add rate limiting, input validation, and encryption
5. Phase 5: Set up API security monitoring and logging
6. Phase 6: Implement API security testing and validation
Output: Secure API with comprehensive protection against common attacks
security-system/
├── authentication/
│ ├── providers/ # Authentication provider implementations
│ ├── middleware/ # Auth middleware and guards
│ ├── tokens/ # Token generation and validation
│ └── sessions/ # Session management
├── authorization/
│ ├── rbac/ # Role-based access control
│ ├── permissions/ # Permission definitions
│ ├── policies/ # Access control policies
│ └── admin/ # Admin interfaces
├── security/
│ ├── encryption/ # Encryption utilities
│ ├── validation/ # Input validation and sanitization
│ ├── headers/ # Security headers and CORS
│ └── rate-limiting/ # Rate limiting and DDoS protection
├── compliance/
│ ├── audit-logs/ # Audit logging and tracking
│ ├── reports/ # Compliance reports
│ ├── policies/ # Security policies and procedures
│ └── documentation/ # Compliance documentation
├── monitoring/
│ ├── siem/ # Security information and event management
│ ├── alerts/ # Security alerts and notifications
│ ├── dashboards/ # Security monitoring dashboards
│ └── incident-response/ # Incident response procedures
└── config/
├── development/ # Development security config
├── staging/ # Staging security config
└── production/ # Production security config
This security and authentication skill transforms the complex process of security system implementation into a guided, expert-supported workflow that ensures comprehensive protection, regulatory compliance, and operational excellence.
tools
Replace with description of the skill and when Claude should use it.
testing
Generate structured task lists from specs or requirements. IMPORTANT: After completing ANY spec via ExitSpecMode, ALWAYS ask the user: "Would you like me to generate a task list for this spec?" Use when user confirms or explicitly requests task generation from a plan/spec/PRD.
tools
Optimize SvelteKit applications by leveraging SvelteKit's full-stack architecture for instant server-side rendering and progressive enhancement. Specialized in load functions, form actions, and SvelteKit's data loading patterns. Use when: - User reports slow initial page load with loading spinners - Page uses onMount + fetch for data fetching - Store patterns cause waterfall fetching - Need to improve SEO (content not in initial HTML) - Converting client-side data fetching to server-side load functions - Implementing progressive enhancement patterns Triggers: "slow loading", "optimize fetching", "SSR data", "SvelteKit optimization", "remove loading spinner", "server-side fetch", "convert to load function", "progressive enhancement", "data fetch lambat", "loading lama"
development
Implement or extend user-facing workflows in SvelteKit applications with full-stack capabilities. Specialized in SvelteKit's load functions, form actions, and progressive enhancement. Use when the feature is primarily a UI/UX change backed by existing APIs, affects only the web frontend, and requires following SvelteKit conventions.