VS
vscode-config
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.
Install
mkdir -p .claude/skills/vscode-config && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/14355" && unzip -o skill.zip -d .claude/skills/vscode-config && rm skill.zipInstalls to .claude/skills/vscode-config
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
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.198 chars✓ has a “when” trigger
About this skill
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.