Skip to content
Back to search

claude-warmup

MarketplaceWorks with Claude CodeGitHub

Claude Code skill: set up, audit and organize a Windows dev machine — what to install, from which sources, and how to organize it.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/gav4you--claude-warmup/badge.svg)](/listings/gav4you--claude-warmup)

HTML

<a href="/listings/gav4you--claude-warmup"><img src="/api/listings/gav4you--claude-warmup/badge.svg" alt="findsafeskills safety rating" /></a>

Install

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

In Claude Code:

/plugin marketplace add gav4you/claude-warmup
/plugin install warmup@claude-warmup

Then just ask, for example: *"set up my machine for Go and web development"* or *"audit my dev tools and organize them"*. The skill triggers on requests like these.

**New to all this?** Read [`skills/warmup/MANUAL.md`](skills/warmup/MANUAL.md), a five-minute guide to what gets installed, why, and the best practices.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 20 lines
  1. {
  2. "name": "claude-warmup",
  3. "owner": {
  4. "name": "gav4you",
  5. "url": "https://github.com/gav4you"
  6. },
  7. "metadata": {
  8. "description": "Dev-machine warmup skill for Claude Code"
  9. },
  10. "plugins": [
  11. {
  12. "name": "warmup",
  13. "source": "./",
  14. "description": "Set up, audit and organize a Windows dev machine for Claude Code: what to install, from which sources, and where it goes.",
  15. "version": "1.1.0",
  16. "license": "MIT",
  17. "keywords": ["setup", "onboarding", "windows", "dev-environment"]
  18. }
  19. ]
  20. }
README.md · README · 61 lines
  1. # warmup: a dev-machine setup skill for Claude Code
  2. When you start using Claude Code on a Windows machine, `warmup` tells Claude:
  3. - **what to install** for web and app development (Go, Node/pnpm, Python, Ruby, Flutter, Expo, Android, databases, cloud CLIs, editors)
  4. - **which source to install each tool from**
  5. - **how to organize it all** in one folder, `C:\DevTools`, with category shortcuts and a generated `catalog.json`
  6. It also tells Claude how to do this without breaking work that's already running: agent loops, builds and containers. And it lists the pitfalls that actually happened on a real setup.
  7. ## Install
  8. In Claude Code:
  9. ```
  10. /plugin marketplace add gav4you/claude-warmup
  11. /plugin install warmup@claude-warmup
  12. ```
  13. Then just ask, for example: *"set up my machine for Go and web development"* or *"audit my dev tools and organize them"*. The skill triggers on requests like these.
  14. **New to all this?** Read [`skills/warmup/MANUAL.md`](skills/warmup/MANUAL.md), a five-minute guide to what gets installed, why, and the best practices.
  15. ## What's inside
  16. ```
  17. skills/warmup/
  18. ├─ SKILL.md eight phases, source priority, red flags
  19. ├─ MANUAL.md plain-language guide: what gets installed and best practices
  20. ├─ reference/
  21. │ ├─ terminal-shell.md Windows Terminal as default, PowerShell 7 LTS (+ current), profiles: do first
  22. │ ├─ tool-catalog.md what to install per category, the exact source, and when
  23. │ ├─ layout.md C:\DevTools layout; how to migrate from winget/MSI to Scoop safely
  24. │ ├─ disk-recovery.md find space in seconds (Everything/MFT); what's safe to delete
  25. │ └─ gotchas.md real failures and their fixes
  26. └─ scripts/
  27. ├─ inventory.ps1 read-only audit: tools, duplicates, dead PATH entries, disk, running work
  28. ├─ build-catalog.ps1 category shortcut folders + README.md + catalog.json
  29. ├─ go-tools.ps1 (re)install the Go toolset @latest
  30. ├─ golang-x-tools.ps1 developer-facing golang.org/x commands
  31. └─ dirsize.ps1, essize.ps1 folder sizing helpers
  32. ```
  33. ## Principles
  34. 1. **Take an inventory before installing anything.**
  35. 2. **Recover disk space first** if C: has less than ~30 GB free.
  36. 3. **Fix the foundation:** make Windows Terminal the default terminal (paste breaks in the old console) and install PowerShell 7 LTS.
  37. 4. **Pick tools by what your code uses.** Read the go.mod, package.json and pyproject files, including their version pins.
  38. 5. **Source priority:**
  39. - Scoop, rooted at `C:\DevTools\scoop`
  40. - language-native tools: `go install`, `npm -g`, `uv tool`, `gem`
  41. - an official release zip with its SHA-256 checked
  42. - winget/MSI only for services and deep Windows integration
  43. 6. **Stage changes while work is running.** Swap toolchains only when the user confirms things are idle.
  44. 7. **Verify from a fresh PATH.** Each `where.exe <tool>` should resolve exactly once, then run smoke tests.
  45. Windows-focused. On macOS or Linux the same phases apply with Homebrew or mise.
  46. ## License
  47. MIT

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.