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>
36 lines
1.8 KiB
Markdown
36 lines
1.8 KiB
Markdown
---
|
|
allowed-tools: Read, Write, Edit, Bash
|
|
argument-hint: [environment-type] | --local | --docker | --cloud | --full-stack
|
|
description: Setup comprehensive development environment with tools, configurations, and workflows
|
|
---
|
|
|
|
# Setup Development Environment
|
|
|
|
Setup comprehensive development environment with modern tooling: **$ARGUMENTS**
|
|
|
|
## Current Environment State
|
|
|
|
- Operating system: !`uname -s` and architecture detection
|
|
- Development tools: !`node --version 2>/dev/null || python --version 2>/dev/null || echo "No runtime detected"`
|
|
- Package managers: !`which npm yarn pnpm pip poetry cargo 2>/dev/null | wc -l` managers available
|
|
- IDE/Editor: Check for VS Code, IntelliJ, or other development environments
|
|
|
|
## Task
|
|
|
|
Configure complete development environment with modern tools and best practices:
|
|
|
|
**Environment Type**: Use $ARGUMENTS to specify local setup, Docker-based, cloud environment, or full-stack development
|
|
|
|
**Environment Setup**:
|
|
1. **Runtime Installation** - Programming languages, package managers, version managers (nvm, pyenv, rustup)
|
|
2. **Development Tools** - IDE configuration, extensions, debuggers, profilers, database clients
|
|
3. **Build System** - Compilers, bundlers, task runners, CI/CD tools, testing frameworks
|
|
4. **Code Quality** - Linting, formatting, pre-commit hooks, code analysis tools
|
|
5. **Environment Configuration** - Environment variables, secrets management, configuration files
|
|
6. **Team Synchronization** - Shared configurations, documentation, onboarding guides
|
|
|
|
**Advanced Features**: Hot reloading, debugging configuration, performance monitoring, container orchestration.
|
|
|
|
**Automation**: Automated setup scripts, configuration management, team environment synchronization.
|
|
|
|
**Output**: Complete development environment with documented setup process, team configurations, and troubleshooting guides. |