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.8 KiB
1.8 KiB
allowed-tools: Read, Write, Edit, Bash
argument-hint: [environment-type] | --development | --production | --microservices | --compose
description: Setup Docker containerization with multi-stage builds and development workflows
Setup Docker Containers
Setup comprehensive Docker containerization for development and production: $ARGUMENTS
Current Project State
- Application type: @package.json or @requirements.txt (detect Node.js, Python, etc.)
- Existing Docker: @Dockerfile or @docker-compose.yml (if exists)
- Dependencies: !
find . -name "package-lock.json" -o -name "poetry.lock" -o -name "Pipfile.lock" | wc -l - Services needed: Database, cache, message queue detection from configs
Task
Implement production-ready Docker containerization with optimized builds and development workflows:
Environment Type: Use $ARGUMENTS to specify development, production, microservices, or Docker Compose setup
Containerization Strategy:
- Dockerfile Creation - Multi-stage builds, layer optimization, security best practices
- Development Workflow - Hot reloading, volume mounts, debugging capabilities
- Production Optimization - Image size reduction, security scanning, health checks
- Multi-Service Setup - Docker Compose, service discovery, networking configuration
- CI/CD Integration - Build automation, registry management, deployment pipelines
- Monitoring & Logs - Container observability, log aggregation, resource monitoring
Security Features: Non-root users, minimal base images, vulnerability scanning, secrets management.
Performance Optimization: Layer caching, build contexts, multi-platform builds, and resource constraints.
Output: Complete Docker setup with optimized containers, development workflows, production deployment, and comprehensive documentation.