VS Code Extensions I Use Daily as a Frontend Developer

A long extension list slows the editor and hides the tools that matter. These are the ones still enabled after I audit the list. The rest of the daily setup is smaller than people expect.

• ESLint. Shows the repo's rules in the editor. I trust the project config, not a personal ruleset.
• Prettier. Only if the repo already uses it. Format on save, and the config file wins.
• Tailwind CSS IntelliSense. Class names, when the project is Tailwind. Useless everywhere else, so it stays enabled per workspace.
• Pretty TypeScript Errors. Turns a four-line generic failure into something I can read before I open the type.
• Error Lens. Inline diagnostics so I do not wait until the next terminal run to see a type error.
• GitLens. Blame on the line I am changing, so I know who to ask and which commit introduced the behaviour.

What I skip

Icon theme packs, AI chat extensions that duplicate the one I already use, and any linter that is not the one in the repo. If a teammate cannot reproduce a red squiggle, the squiggle is my problem, not the code's.

Check the extensions into the conversation, not necessarily into the repo, unless the team agrees. A recommended list in the README is enough. Forcing installs on clone is how a workspace.json file starts fighting people.