VSCode/Cursor Config Management

VerifiedSafe

Manage VSCode/Cursor configuration in this dotfiles repository. Use when working with settings.json, keybindings.json, or tasks.json files.

Sby Skills Guide Bot
DevelopmentIntermediate
207/23/2026
Claude CodeCursor
#vscode#cursor#configuration#dotfiles#settings

Recommended for

Our review

Manages VSCode and Cursor configuration files in a dotfiles repository, including machine-specific, user, and profile layers with symlink-based setup.

Strengths

  • Organizes config into layers for different machines and profiles.
  • Uses a setup script to symlink machine-specific configs.
  • Supports Settings Sync for user and profile configs.
  • Encapsulates common tasks like adding machine configs or updating keybindings.

Limitations

  • Requires manual creation of machine directories for each host.
  • Relies on Settings Sync for user/profile configs, which may have latency or conflicts.
  • Setup script only handles machine configs; user and profile sync is external.
When to use it

Use when setting up or maintaining a dotfiles repository for VSCode/Cursor cross-machine configuration management.

When not to use it

Avoid if you prefer a single global config without machine-specific overrides, or if you use a different editor config management tool.

Security analysis

Safe
Quality score85/100

The skill is purely documentation about VSCode configuration file organization. It contains no executable commands, data exfiltration, or destructive instructions.

No concerns found

Examples

Add Machine Config
Add a new machine configuration for 'office-pc' in the vscode dotfiles repository. Create the necessary directory and settings.json file.
Update Keybindings
Edit the user settings.json in the vscode dotfiles repo to add keybindings for Ctrl+P and Ctrl+N to navigate up and down.
Run Setup Script
Run the vscode setup script to symlink the machine config for the current host.

name: vscode-config description: Manage VSCode/Cursor configuration in this dotfiles repository. Use when working with settings.json, keybindings.json, or tasks.json files, or when asked about VSCode/Cursor configuration structure.

VSCode Config Management

Repository Structure

vscode/
├── user/           # Client-side, synced via Settings Sync
├── profiles/OPS/   # Profile-specific (vim bindings, editor prefs)
├── machines/ops/   # Server-side, symlinked via setup.sh
└── setup.sh        # Symlinks machine configs only

Configuration Layers

| Layer | Location | Sync Method | |-------|----------|-------------| | Machine | machines/<hostname>/ | setup.sh symlink | | User | user/ | Settings Sync | | Profile | profiles/<name>/ | Settings Sync |

Common Tasks

Add machine config: Create machines/<hostname>/settings.json

Update vim bindings: Edit user/settings.json (keybindings sync to all machines)

Run setup on server: ./vscode/setup.sh (uses hostname, or --machine <name>)

Machine settings override user/profile. Put machine-specific paths and extensions in machine config.

Related skills