setup-development-environment — Claude Code command: what it does
A slash command that builds out a dev environment: runtimes, tooling, build setup, linters, configs. Handy when you spin up a project on a fresh machine.
npx claude-code-templates@latest --command setup/setup-development-environmentWhat setup-development-environment does
It starts by reading the machine. The command detects the operating system, checks which runtime is available (node or python), counts installed package managers, and looks for editors such as VS Code. From there it configures the environment for the type you asked for: local, Docker, cloud, or full-stack.
Six steps sit inside. Language and version manager installs (nvm, pyenv, rustup), IDE setup with extensions and debuggers, a build layer with compilers and CI/CD, linting plus pre-commit hooks, environment variables and secrets, and finally shared configs with an onboarding guide. You pick the type with an argument: --local, --docker, --cloud, or --full-stack.
The command can read, write, edit files and run bash, so it touches your real system rather than a sandbox. If the repo already has hand-tuned configs or hooks, run it against a copy first — it will overwrite what you set up yourself.
What it helps with
- set up a dev environment on a new machine without installing everything by hand
- give the whole team the same configs and skip repeating onboarding
- spin up a Docker or cloud environment for a specific project type
- add linters, formatters and pre-commit hooks without wiring them manually
- lay out environment variables and secrets across config files
Example prompts for the agent
- /setup-development-environment --local
- /setup-development-environment --docker
- /setup-development-environment --full-stack
How to install setup-development-environment
1claude-code-templates
npx claude-code-templates@latest --command setup/setup-development-environment2Manually: put the files in place
.claude/commands/setup-development-environment.mdCall it with /setup-development-environment. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/setup-development-environment.mdCall it with /prompts:setup-development-environment. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/setup-development-environment.prompt.mdManually: put the files in place
.gemini/commands/setup-development-environment.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about setup-development-environment
How do I install setup-development-environment in Claude?
Through the templates package: npx claude-code-templates@latest --command setup/setup-development-environment. The command file then lives at .claude/commands/setup-development-environment.md.
What does setup-development-environment do?
It inspects the current system, then configures runtimes, dev tools, build tooling, linters and config files for the environment type you choose. It finishes with setup documentation and a team onboarding guide.
Which environment types are supported?
Four argument values: --local, --docker, --cloud and --full-stack. Without an argument the command reads the type from your phrasing.
Source text
setup-development-environment.md · MIT
--- 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.
© davila7 · MIT · davila7/claude-code-templates
