mcpbeat Sign in

Update Cursor Settings Skill for Cursor

Modify Cursor/VSCode user settings in settings.json. Use when the user wants to change editor settings, preferences, configuration, themes, font size, tab size, format on save, auto save, keybindings, or any settings.json values.

854 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
196
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/coco-research/coco --skill update-cursor-settings

The instruction itself

10 sections, as written by the author

Updating Cursor Settings

This skill guides you through modifying Cursor/VSCode user settings. Use this when the user wants to change editor settings, preferences, configuration, themes, keybindings, or any settings.json values.

Settings File Location

| OS | Path |

|----|------|

| macOS | ~/Library/Application Support/Cursor/User/settings.json |

| Linux | ~/.config/Cursor/User/settings.json |

| Windows | %APPDATA%\Cursor\User\settings.json |

Before Modifying Settings

  • Read the existing settings file to understand current configuration
  • Preserve existing settings - only add/modify what the user requested
  • Validate JSON syntax before writing to avoid breaking the editor

Modifying Settings

Step 1: Read Current Settings

// Read the settings file first
const settingsPath = "~/Library/Application Support/Cursor/User/settings.json";
// Use the Read tool to get current contents

Step 2: Identify the Setting to Change

Common setting categories:

  • Editor: editor.fontSize, editor.tabSize, editor.wordWrap, editor.formatOnSave
  • Workbench: workbench.colorTheme, workbench.iconTheme, workbench.sideBar.location
  • Files: files.autoSave, files.exclude, files.associations
  • Terminal: terminal.integrated.fontSize, terminal.integrated.shell.*
  • Cursor-specific: Settings prefixed with cursor. or aipopup.

Step 3: Update the Setting

When modifying settings.json:

  • Parse the existing JSON (handle comments - VSCode settings support JSON with comments)
  • Add or update the requested setting
  • Preserve all other existing settings
  • Write back with proper formatting (2-space indentation)

Common User Requests

| User Request | Setting |

|--------------|---------|

| "bigger/smaller font" | editor.fontSize |

| "change tab size" | editor.tabSize |

| "format on save" | editor.formatOnSave |

| "word wrap" | editor.wordWrap |

| "change theme" | workbench.colorTheme |

| "hide minimap" | editor.minimap.enabled |

| "auto save" | files.autoSave |

| "line numbers" | editor.lineNumbers |

| "bracket matching" | editor.bracketPairColorization.enabled |

| "cursor style" | editor.cursorStyle |

| "smooth scrolling" | editor.smoothScrolling |

Important Notes

  • JSON with Comments: VSCode/Cursor settings.json supports comments (// and /* */). When reading, be aware comments may exist. When writing, preserve comments if possible.
  • Restart May Be Required: Some settings take effect immediately, others require reloading the window or restarting Cursor.
  • Backup: For significant changes, consider mentioning the user can undo via Ctrl/Cmd+Z in the settings file.
  • Workspace vs User Settings: User settings apply globally; workspace settings (.vscode/settings.json) apply only to the current project.

Workflow

  • Read ~/Library/Application Support/Cursor/User/settings.json
  • Parse the JSON content
  • Add/modify the requested setting(s)
  • Write the updated JSON back to the file
  • Inform the user the setting has been changed and whether a reload is needed

Other skills for the same job

different authors, same section of the catalogue
Theme Factory
by anthropics
vendor ×16

Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors/fonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.

36k tokens
Brand Guidelines
by anthropics
vendor ×13

Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.

3k tokens
Artifacts Builder
by JayZeeDesign
×8

Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.

11k tokens scripts
Web Artifacts Builder
by anthropics
vendor ×7

Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.

11k tokens scripts
Frontend Design
by Karanjot786
×6

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.

1k tokens
Frontend Design
by anthropics
vendor ×4

Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.

5k tokens
Expo Tailwind Setup
by openai
vendor ×4

Set up Tailwind CSS v4 in Expo with react-native-css and NativeWind v5 for universal styling

3k tokens
Use Dom
by openai
vendor ×3

Use Expo DOM components to run web code in a webview on native and as-is on web. Migrate web code to native incrementally.

3k tokens

How to use it

Copy the folder

Take coco-research/update-cursor-settings from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.