Create a new file — 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

Create a new source file under src for a quick bug fix: add src/auth/sessionManager.js, open it for…

Create a new source file under src for a quick bug fix: add src/auth/sessionManager.js, open it for editing, and put a minimal export function with a TODO comment for integration tests so I can hand it to Priya by 3pm.

Improve — make it easier to accept

Before I add a new file for the auth module, make approval easy: create src/auth/sessionManager.js…

Before I add a new file for the auth module, make approval easy: create src/auth/sessionManager.js and place a one-line description and the public function at the top, add a comment showing where to add unit tests, and ensure the file uses the project's ESLint rules so reviewers don't reject it for style.

Decide — diagnose the stuck moment

I tried to add a new file and it appeared in the workspace root, not under src where the codebase…

I hit New File and it put the file in the workspace root instead of src.

I tried to add a new file and it appeared in the workspace root, not under src where the codebase expects it. The reviewer is waiting; I don't know if I clicked in the wrong pane, the project explorer lost focus, or the default new-file location changed. What's the most likely diagnosis and the quickest correction so the file ends up in src and keeps git history sensible?

Become — change the pattern

I keep creating files in inconsistent locations and spend time every week moving them, fixing…

I scatter new files across the repo and then reorganize later.

I keep creating files in inconsistent locations and spend time every week moving them, fixing imports, and dealing with broken tests. Which change to my workflow when adding files will prevent that rework—something small I can train myself to do immediately and that scales across team projects?

Next to this one

Other code editor work people do in Visual Studio Code.

Close current editor Commit changes Configure tasks.json Create a launch configuration Create a new branch Create a new folder Delete a file Disable an extension Edit settings JSON Format current file

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