Install an extension — AI Prompts for Visual Studio Code

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 to install an extension so Claire can use the linter. Install the extension that provides…

I need to install an extension so Claire can use the linter. Install the extension that provides ESLint, ensure it is enabled for our workspace, restart the editor window if required, and run a lint check on src to confirm problems appear. Tell Claire when it’s ready and how to enable it for her workspace. Ladder L1

Improve — make it easier to accept

Before I install, make it easy for Claire to accept: choose the marketplace extension with the most…

Before I install, make it easy for Claire to accept: choose the marketplace extension with the most recent updates and active installs, confirm compatibility with our runtime, list the settings to enable, and note any workspace file changes it will suggest. Warn if it requires a reload or exposes telemetry. Ladder L2

Decide — diagnose the stuck moment

I installed the linter extension and it shows as installed but it won’t activate for the workspace;…

I tried to install the linter extension but it failed to activate

I installed the linter extension and it shows as installed but it won’t activate for the workspace; no diagnostics appear. I’m unsure whether the workspace settings disable extensions, the extension needs a companion language server, or there is a permissions issue. Should I check workspace settings, run the extension host log, or try a fresh user profile? Which will most quickly identify the activation blocker? Ladder L5

Become — change the pattern

Every sprint I spend time resolving extension conflicts: one person’s formatter changes others’…

I waste time repeatedly on extensions that conflict or break teammates

Every sprint I spend time resolving extension conflicts: one person’s formatter changes others’ commits, some extensions require manual setup, and onboarding slows. What practice will cut this overhead — a curated workspace extensions list, a devcontainer configuration that preinstalls and pins versions, or a team standard on settings sync? Recommend the single change to adopt now and a short rollout plan. Ladder L6

Next to this one

Other code editor work people do in Visual Studio Code.

Delete a file Disable an extension Edit settings JSON Format current file Inspect variable values Manage extension settings Move a file Navigate to definition Open a project folder Open command palette

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.

The rest of the map

Same library, five ways in.

Work Atlasthe whole map, interactive Careers1,949 jobs and their real tasks Soft skillsthe human part of the work Activities500 things people do Prompt Librarybrowse every prompt