Edit settings JSON

Edit settings JSON in Visual Studio Code — with the four heights of help laid out: do it now, make it easier for the next person to accept, work out the right move when you are stuck, and learn the pattern so it stops coming back.

4prompt heights
Open it in the interactive atlas →

The four heights

The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.

Execute — do the immediate task

+
I need the workspace settings JSON updated so the project uses soft tabs, an indent size of 2, and…
I need the workspace settings JSON updated so the project uses soft tabs, an indent size of 2, and disables automatic format on save. Edit .vscode/settings.json, add "editor.insertSpaces": true, "editor.tabSize": 2, and "editor.formatOnSave": false, then validate the file is syntactically correct before committing to the repo.

Improve — make it easier to accept

+
Before I push these settings to the team, make the change reviewer-friendly: move…
Before I push these settings to the team, make the change reviewer-friendly: move editor.insertSpaces, editor.tabSize, and editor.formatOnSave to the top of settings.json, add a one-line comment explaining why (consistency with frontend style guide), and highlight any other settings that conflict with these three.

Decide — diagnose the stuck moment

+
I changed the workspace settings to use two-space soft tabs but the CI linter on main now fails and…

I just saved settings.json and a teammate's linter started failing.

I changed the workspace settings to use two-space soft tabs but the CI linter on main now fails and Zoe in frontend says her editor keeps reformatting. I don't know whether CI reads workspace or project config, and I can't see Zoe's local overrides. Do I revert my settings, add an .editorconfig that explicitly sets insertSpaces and tabSize, or ask Zoe to share her editor settings first? Recommend the most likely fix and the exact next message to send Zoe.

Become — change the pattern

+
Across several projects we repeatedly lose time to whitespace and format disagreements: developers…

We keep fighting over whitespace in shared repos.

Across several projects we repeatedly lose time to whitespace and format disagreements: developers commit different editor settings, CI flips on different formatters, and PRs get blocked. I want a durable habit to stop this. Should we standardize by adding an .editorconfig at repo root, enforce formatting in CI with autofix, or mandate a shared settings.json in .vscode? Tell me which habit will cut friction fastest and the one-line rule to enforce in PR reviews.

Next to this one

Other code editor work people do in Visual Studio Code.

Every task here came from the work, not from a feature list — which is why the prompts name what you want done and never the button that does it. The tool changes; the work does not.
Copyright © LLOS.ai · 2026 — original pedagogy, voice, and design — all rights reserved.

The rest of the map

Same library, five ways in.