Create intermediate Works with: Any AI

VS Code Shared Workspace Settings and Extensions Recommendation

Structured brief Has example

• 🧑‍💻 VS Code

Standardise formatting and tools for a team repository.

The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.

[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.

Plan shared Visual Studio Code settings for a team repository. Languages and frameworks: [STACK]. Formatting and linting tools already used in the project: [TOOLS]. Problems we see (inconsistent formatting, different line endings, noisy diffs): [PROBLEMS]. Operating systems used by the team: [OPERATING_SYSTEMS].

Propose the contents of .vscode/settings.json, .vscode/extensions.json (recommended extensions only, one-line reason for each) and .editorconfig, each as a code block with comments where the format allows, and mark any setting name or value you are unsure exists in the current version [VERIFY]. Explain every setting in plain words: format on save, default formatter per language, tab and space rules, trailing whitespace, final newline, line endings, files excluded from search and the explorer, and spell checking if used. Worked example described in words for a JavaScript project: format on save on, the project formatter as default, tab size 2, trailing whitespace trimmed, final newline inserted, lint results shown, build output hidden from search, with the reason for each. Add five recommended extensions with reasons and a note on checking publishers and permissions, since some execute code or send data.

Distinguish user settings from workspace settings and say which belong in the repository. Limit shared settings to what keeps code consistent; do not force personal preferences, and explain how a member can override a setting locally and when they should not. Test on a clean profile: confirm the formatter runs on save and a sample file produces no diff after formatting. Changes go via pull request.

Fill in before use

Optional: type your details and the prompt above updates. Nothing is saved or sent.

Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.

Invented project settings explained in words: format on save is on; the project formatter is the default for the language; indentation is two spaces; trailing whitespace is removed; a final newline is added; build output and dependency folders are hidden from search. Recommended extensions: the formatter, the linter, a spell checker, and the language support. Test: open the repository on a fresh profile, edit a file with messy spacing, save, and confirm that a second developer sees no formatting diff. Result target: pull request diffs contain only meaningful changes.

• structured
• vs-code