skills/nvm-skills/nvm-defaults-and-nvmrc/SKILL.md
Set default Node versions via nvm aliases, create .nvmrc files for project-specific versions, and configure shell auto-switching per directory. Use when the user asks about nvm alias default, .nvmrc configuration, auto-switching Node versions on directory change, or pinning a Node version for a project.
npx skillsauth add partme-ai/full-stack-skills nvm-defaults-and-nvmrcInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Configure default Node versions and project-level version pinning with nvm.
Set the default Node version using an alias:
nvm alias default 20
# Or use an LTS alias
nvm alias default lts/iron
Create or update .nvmrc in the project root:
# Pin to a specific version
echo "20.11.0" > .nvmrc
# Or use an LTS alias
echo "lts/iron" > .nvmrc
Enable shell auto-switching if requested (see auto-use examples per shell).
Verify the configuration works:
# Open a new shell, then:
nvm current # Should show the default version
cd /path/to/project
node -v # Should match .nvmrc version
Important: Keep .nvmrc consistent across team repos to avoid version drift. Basic install/use belongs to nvm-usage-basics.
examples/default-version.md - Setting default aliasesexamples/nvmrc.md - .nvmrc file creation and usageexamples/auto-use-bash.md - Auto-switching for bashexamples/auto-use-zsh.md - Auto-switching for zshexamples/auto-use-fish.md - Auto-switching for fishnvm alias, default version, .nvmrc, auto use, project version, defaults
development
Provides per-component and per-API examples with cross-platform compatibility details for uni-app, covering built-in components, uni-ui components, and APIs (network, storage, device, UI, navigation, media). Use when the user needs official uni-app components or APIs, wants per-component examples with doc links, or needs platform compatibility checks.
tools
Creates new uni-app projects via the official CLI or HBuilderX with Vue 2/Vue 3 template selection, manifest.json and pages.json configuration, and directory structure setup. Use when the user wants to scaffold a new uni-app project, initialize project files with a single command, or set up the development environment.
tools
Browses, installs, configures, and manages plugins from the uni-app plugin market (ext.dcloud.net.cn) including component plugins, API plugins, and template plugins with dependency handling. Use when the user needs to find and install uni-app plugins, configure plugin settings, manage plugin dependencies, or integrate third-party components.
tools
Develops native Android and iOS plugins for uni-app including module creation, JavaScript-to-native communication, and plugin packaging for distribution. Use when the user needs to build custom native modules, extend uni-app with native capabilities (camera, Bluetooth, sensors), or create publishable native plugins.