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>
1.5 KiB
1.5 KiB
allowed-tools: Read, Write, Edit, Bash
argument-hint: [focus-area] | --headers | --auth | --encryption | --infrastructure
description: Harden application security configuration with comprehensive security controls
Security Hardening
Harden application security configuration and controls: $ARGUMENTS
Current Security Posture
- Framework: @package.json or @requirements.txt or @Cargo.toml (detect framework)
- Security headers: !
curl -I http://localhost:3000 2>/dev/null | grep -i 'x-\|content-security\|strict-transport' || echo "No server running" - Environment config: @.env* (check for security-related variables)
- Dependencies: !
npm audit --audit-level=moderate 2>/dev/null || echo "Run dependency audit first"
Task
Implement comprehensive security hardening based on security best practices:
Hardening Focus: Use $ARGUMENTS to target specific areas or apply comprehensive hardening
Security Controls:
- Authentication & Authorization - MFA, RBAC, session security, password policies
- Input Validation - XSS prevention, SQL injection protection, CSRF tokens
- Secure Communication - HTTPS/TLS, HSTS, certificate management
- Data Protection - Encryption at rest/transit, key management, secure storage
- Security Headers - CSP, CORS, security response headers
- Infrastructure Security - Container hardening, network segmentation, monitoring
Output: Hardened application with comprehensive security controls, proper configuration, and monitoring capabilities.