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>
2.0 KiB
2.0 KiB
allowed-tools: Read, Write, Edit, Bash
argument-hint: [rate-limit-type] | --api | --authentication | --file-upload | --database
description: Implement comprehensive API rate limiting with advanced algorithms and user-specific policies
Setup Rate Limiting
Implement comprehensive API rate limiting with advanced control mechanisms: $ARGUMENTS
Current API State
- Framework detection: @package.json or @requirements.txt (Express, FastAPI, Spring Boot, etc.)
- Existing rate limiting: !
grep -r "rate.limit\|throttle\|rateLimit" src/ 2>/dev/null | wc -l - Redis availability: !
redis-cli ping 2>/dev/null || echo "Redis not available" - API endpoints: !
grep -r "route\|endpoint\|@app\\.route" src/ 2>/dev/null | wc -l
Task
Implement production-ready rate limiting system with sophisticated algorithms and user policies:
Rate Limit Type: Use $ARGUMENTS to focus on API rate limiting, authentication limiting, file upload controls, or database access limiting
Rate Limiting Architecture:
- Algorithm Implementation - Token bucket, sliding window, fixed window, leaky bucket algorithms
- User Policies - Tier-based limits, authenticated vs anonymous, user-specific quotas, IP-based controls
- Storage Backend - Redis integration, distributed rate limiting, persistence strategies, failover mechanisms
- Endpoint Configuration - Per-route limits, method-specific rules, dynamic configuration, A/B testing
- Monitoring & Analytics - Usage tracking, abuse detection, performance metrics, alerting systems
- Bypass Mechanisms - Whitelist management, internal request handling, emergency overrides
Advanced Features: Adaptive rate limiting, geo-based controls, API key management, quota systems, abuse prevention.
Production Readiness: High availability, performance optimization, security controls, comprehensive monitoring.
Output: Complete rate limiting system with intelligent policies, comprehensive monitoring, and advanced abuse prevention capabilities.