mirror of
https://github.com/davila7/claude-code-templates.git
synced 2026-09-19 01:30:23 +08:00
Dani
054c0e56e9
Removed the deprecated 'model: sonnet' field from command frontmatter to fix compatibility issues with Claude Code. Commands will now inherit the model from the active conversation instead of using a hardcoded deprecated model identifier. Changes: - Removed 'model: sonnet' from 142 command files across all categories - Commands now use default model inheritance behavior - Preserved 'model: claude-sonnet-4-5-20250929' in gemini-review.md (valid model) - 67 commands without model field remain unchanged This resolves the "model: sonnet not found" error reported in GitHub issues and aligns with Claude Code's recommended practice of letting commands inherit the conversation model. Affected categories: - Database/Supabase commands (8 files) - Documentation commands (8 files) - Deployment commands (11 files) - Setup commands (14 files) - Performance commands (8 files) - Team commands (14 files) - Security commands (6 files) - NextJS/Vercel commands (10 files) - Sync commands (14 files) - And more across other categories 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
34 lines
1.5 KiB
Markdown
34 lines
1.5 KiB
Markdown
---
|
|
allowed-tools: Read, Write, Edit, Bash
|
|
argument-hint: [auth-method] | --oauth | --jwt | --mfa | --passwordless
|
|
description: Implement secure user authentication system with chosen method and security best practices
|
|
---
|
|
|
|
# Add Authentication System
|
|
|
|
Implement secure user authentication system: **$ARGUMENTS**
|
|
|
|
## Current Application State
|
|
|
|
- Framework detection: @package.json or @requirements.txt or @Cargo.toml
|
|
- Existing auth: !`grep -r "auth\|login\|jwt\|session" src/ --include="*.js" --include="*.py" --include="*.rs" | wc -l`
|
|
- Security config: @.env* (check for auth-related variables)
|
|
- Database setup: Check for user models or auth tables
|
|
|
|
## Task
|
|
|
|
Implement comprehensive authentication system with security best practices:
|
|
|
|
**Authentication Methods**: Choose from username/password, OAuth 2.0, JWT, SAML, MFA, or passwordless based on $ARGUMENTS
|
|
|
|
**Implementation Areas**:
|
|
1. **User Management** - Registration, profiles, password policies, account verification
|
|
2. **Authentication Flow** - Login/logout, session management, token handling, middleware
|
|
3. **Authorization System** - RBAC, permissions, route protection, API security
|
|
4. **Security Hardening** - Password hashing, rate limiting, CSRF protection, secure cookies
|
|
5. **Integration** - Frontend components, API endpoints, database models, middleware
|
|
|
|
**Security Standards**: Implement OWASP authentication guidelines, secure session management, and proper error handling.
|
|
|
|
**Output**: Production-ready authentication system with comprehensive security controls and user-friendly interface.
|