setup-wsl-dev-environment
About
This Claude Skill automates the setup of a WSL2 development environment on Windows, installing and configuring essential tools like Git, Node.js, Python, and SSH keys. It's designed for initial machine setup, adding tools to existing WSL, or establishing cross-platform workflows between WSL and Windows. Developers should use it to quickly bootstrap a standardized dev environment with integrated shell configuration and path management.
Quick Install
Claude Code
Recommendednpx skills add pjt222/agent-almanac -a claude-code/plugin add https://github.com/pjt222/agent-almanacgit clone https://github.com/pjt222/agent-almanac.git ~/.claude/skills/setup-wsl-dev-environmentCopy and paste this command in Claude Code to install this skill
Documentation
Set Up WSL Development Environment
Configure complete WSL2 dev environment for cross-platform work.
When Use
- Setting up new Windows machine for development
- Configuring WSL2 first time
- Adding dev tools to existing WSL install
- Cross-platform workflow (WSL + Windows tools)
Inputs
- Required: Windows 10/11 with WSL2 support
- Optional: Preferred Linux distro (default: Ubuntu)
- Optional: Languages (Node.js, Python, R)
- Optional: Extra tools (Docker, tmux, fzf)
Steps
Step 1: Install WSL2
In PowerShell (Administrator):
wsl --install
wsl --set-default-version 2
Restart if prompted. Ubuntu installs default.
Got: After reboot, wsl --list --verbose shows distro running WSL version 2. wsl cmd opens Linux shell.
If fail: WSL2 install fail? Enable "Virtual Machine Platform" and "Windows Subsystem for Linux" features manual via optionalfeatures.exe. Old Windows 10 builds? Kernel update from Microsoft needed.
Step 2: Configure WSL Resource Limits
Create ~/.wslconfig in Windows home dir:
[wsl2]
memory=8GB
processors=4
localhostForwarding=true
Got: .wslconfig file exists in Windows user home (e.g., C:\Users\Name\.wslconfig). After wsl --shutdown and restart WSL, limits applied.
If fail: Config no effect? Verify file in correct location (Windows home, not WSL home). Run wsl --shutdown, reopen WSL.
Step 3: Update and Install Essentials
sudo apt update && sudo apt upgrade -y
sudo apt install -y \
build-essential \
curl \
wget \
git \
git-lfs \
vim \
htop \
tree \
jq \
ripgrep \
fd-find \
unzip \
zip
Create useful aliases:
echo 'alias fd="fdfind"' >> ~/.bashrc
Got: All packages install no errors. Cmds git --version, jq --version, rg --version, tree work.
If fail: apt install fail? Run sudo apt update first to refresh pkg lists. Pkg not found? Check Ubuntu version supports it or install alt source (snap, cargo, manual).
Step 4: Configure Git
git config --global user.name "Your Name"
git config --global user.email "[email protected]"
git config --global init.defaultBranch main
git config --global core.autocrlf input
git config --global color.ui auto
git config --global core.editor vim
Got: git config --list shows correct user name, email, default branch (main), autocrlf (input), editor settings.
If fail: Settings not applied? Verify used --global (not --local which only applies to current repo). Check ~/.gitconfig has expected entries.
Step 5: Set Up SSH Keys
ssh-keygen -t ed25519 -C "[email protected]"
eval "$(ssh-agent -s)"
ssh-add ~/.ssh/id_ed25519
cat ~/.ssh/id_ed25519.pub
# Add to GitHub: Settings > SSH and GPG keys
Test: ssh -T [email protected]
Got: ssh -T [email protected] returns "Hi username! You've successfully authenticated." SSH key pair exists at ~/.ssh/id_ed25519 and ~/.ssh/id_ed25519.pub.
If fail: Auth fails? Verify public key added to GitHub (Settings > SSH and GPG keys). Check ssh-agent running, key loaded with ssh-add -l. Agent not running? Add eval "$(ssh-agent -s)" to ~/.bashrc.
Step 6: Install Node.js (via nvm)
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.0/install.sh | bash
source ~/.bashrc
nvm install --lts
nvm use --lts
Got: node --version and npm --version return current LTS versions. nvm ls shows installed version marked default.
If fail: nvm not found after install? Source ~/.bashrc or open new terminal. Install script fails? Download, review, run manual.
Step 7: Install Python (via pyenv)
# Install build dependencies
sudo apt install -y make libssl-dev zlib1g-dev libbz2-dev \
libreadline-dev libsqlite3-dev libncursesw5-dev xz-utils \
tk-dev libxml2-dev libxmlsec1-dev libffi-dev liblzma-dev
curl https://pyenv.run | bash
# Add to ~/.bashrc
echo 'export PATH="$HOME/.pyenv/bin:$PATH"' >> ~/.bashrc
echo 'eval "$(pyenv init -)"' >> ~/.bashrc
source ~/.bashrc
pyenv install 3.12
pyenv global 3.12
Got: python --version returns Python 3.12.x. pyenv versions shows installed version set global.
If fail: pyenv install fail with build errors? Ensure all build deps from apt install cmd installed. Missing libs (especially libssl-dev or zlib1g-dev) most common cause of Python build failure.
Step 8: Configure Shell
Add to ~/.bashrc:
# History
export HISTSIZE=10000
export HISTFILESIZE=20000
export HISTCONTROL=ignoredups:erasedups
shopt -s histappend
# Navigation aliases
alias ll='ls -alF'
alias la='ls -A'
alias ..='cd ..'
alias ...='cd ../..'
# Development paths
export DEV_HOME="/mnt/d/dev/p"
alias dev='cd $DEV_HOME'
# Functions
mkcd() { mkdir -p "$1" && cd "$1"; }
# PATH additions
export PATH="$HOME/bin:$HOME/.local/bin:$PATH"
Got: After source ~/.bashrc, all aliases (ll, la, .., dev) work, mkcd function creates and enters dirs, $DEV_HOME points to dev dir.
If fail: Aliases not available? Verify additions appended to ~/.bashrc (not ~/.bash_profile or ~/.profile). Run source ~/.bashrc to reload without new terminal.
Step 9: Set Up Claude Code CLI
# Add Claude CLI to PATH (after installation)
echo 'export PATH="$HOME/.claude/local/node_modules/.bin:$PATH"' >> ~/.bashrc
source ~/.bashrc
# Verify
which claude
Got: which claude returns path to Claude Code CLI binary (e.g., ~/.claude/local/node_modules/.bin/claude). Run claude --version prints installed version.
If fail: claude not found? Verify PATH export added to ~/.bashrc and sourced. Check Claude Code installed at ~/.claude/local/. Not installed? Follow Claude Code install instructions first.
Step 10: Cross-Platform Path Reference
| Windows | WSL |
|---|---|
C:\Users\Name | /mnt/c/Users/Name |
D:\dev\projects | /mnt/d/dev/projects |
%APPDATA% | /mnt/c/Users/Name/AppData/Roaming |
Open Windows Explorer from WSL: explorer.exe .
Got: Path conversion table understood and tested: access Windows path from WSL works (e.g., ls /mnt/c/Users/), explorer.exe . opens Windows Explorer to current WSL dir.
If fail: /mnt/c/ not accessible? Verify WSL automount configured. Check /etc/wsl.conf for [automount] settings. Run wsl --shutdown and restart if mount points stale.
Checks
- WSL2 running with correct distro
- Git configured with correct identity
- SSH key added to GitHub, connection verified
- Node.js installed, working
- Python installed, working
- Shell aliases, functions work
- Claude Code CLI accessible
Pitfalls
- Slow file access on
/mnt/: Store frequent projects in WSL filesystem (~/) for better speed. Use/mnt/for projects shared with Windows tools. - Line endings:
core.autocrlf=inputprevents CRLF issues. Configure editors use LF. - Permission issues: Files on
/mnt/may show incorrect permissions. Add to/etc/wsl.conf:[automount]\noptions = "metadata,umask=22,fmask=11" - Windows Defender: Exclude WSL dirs from real-time scanning for better speed.
See Also
configure-git-repository- detailed Git repo setupconfigure-mcp-server- MCP setup needs WSL environmentwrite-claude-md- configure AI assistant for projects
GitHub Repository
Related Skills
qmd
Developmentqmd is a local search and indexing CLI tool that enables developers to index and search through local files using hybrid search combining BM25, vector embeddings, and reranking. It supports both command-line usage and MCP (Model Context Protocol) mode for integration with Claude. The tool uses Ollama for embeddings and stores indexes locally, making it ideal for searching documentation or codebases directly from the terminal.
subagent-driven-development
DevelopmentThis skill executes implementation plans by dispatching a fresh subagent for each independent task, with code review between tasks. It enables fast iteration while maintaining quality gates through this review process. Use it when working on mostly independent tasks within the same session to ensure continuous progress with built-in quality checks.
mcporter
DevelopmentThe mcporter skill enables developers to manage and call Model Context Protocol (MCP) servers directly from Claude. It provides commands to list available servers, call their tools with arguments, and handle authentication and daemon lifecycle. Use this skill for integrating and testing MCP server functionality in your development workflow.
adk-deployment-specialist
DevelopmentThis skill deploys and orchestrates Vertex AI ADK agents using A2A protocol, managing AgentCard discovery, task submission, and supporting tools like Code Execution Sandbox and Memory Bank. It enables building multi-agent systems with sequential, parallel, or loop orchestration patterns in Python, Java, or Go. Use it when asked to deploy ADK agents or orchestrate agent workflows on Google Cloud.
