Navigate to definition — AI Prompts for Visual Studio Code

2 ready prompts

Written for the moment this actually comes up.

Improve — make it easier to accept

Before I navigate to calculateScore’s definition, surface the definition’s public API details: show…

Before I navigate to calculateScore’s definition, surface the definition’s public API details: show its parameter names and types, any deprecation notes, and recent commits that modified its logic. If there are overloads or exported wrapper functions, present them so I don’t jump to an obsolete internal helper by mistake.

Decide — diagnose the stuck moment

I used Go to Definition on calculateScore and it took me to a generated bindings file instead of…

Go to definition landed in a generated file

I used Go to Definition on calculateScore and it took me to a generated bindings file instead of the source. I need the real implementation to understand the logic. Who set up the codegen that could be redirecting symbols, what indicators tell me where the source lives, and what’s the least risky next step to reach the true source rather than the generated artifact?

Next to this one

Other code editor work people do in Visual Studio Code.

Format current file Inspect variable values Install an extension Manage extension settings Move a file Open a project folder Open command palette Open integrated notebook Open integrated terminal Open recent 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