These Cursor Extensions Took Me From Debugging to Deploying

AI Parker Rex · 10m 13s · Watch on YouTube · 19 sources

Decision Card

Effort: About 30–60 minutes. Install the 5–8 extensions you’d actually use with Cmd/Ctrl+Shift+X, then copy the few settings.json lines shown (relative line numbers, Vim system clipboard, per-language default formatter).

Honest take: Most of this is a scroll through the extensions panel, not a curated setup, and parts of it overlap. He runs Black alongside Ruff, which ships a formatter built to replace Black. He uses a bracket-pair colorization extension even though VS Code has had that feature built in since v1.60. He keeps ESLint next to Biome, which is meant to replace ESLint and Prettier. The opening line about OpenAI “purchasing” Windsurf is also out of date: the deal never closed, and Cognition acquired Windsurf instead.

Concrete next steps:

  • Error Lens: adopt (2 min). It shows diagnostics inline, so you see errors without hovering.
  • Biome: try (30 min on one JS/TS repo). Install @biomejs/biome and run npx biome check --write . to see if it can replace ESLint and Prettier for you. Details: https://github.com/biomejs/biome
  • Ruff: adopt (for Python); skip running Black alongside it (15 min). ruff format keeps Black’s style, with over 99.9% of lines identical. Details: https://docs.astral.sh/ruff/formatter/
  • Bracket-pair colorization extension: skip. Turn on the built-in editor.bracketPairColorization.enabled setting instead: https://code.visualstudio.com/blogs/2021/09/29/bracket-pair-colorization
  • VSCodeVim: try if you already know Vim motions (10 min). Turn on vim.useSystemClipboard and the extensions.experimental.affinity performance setting from the README: https://github.com/VSCodeVim/Vim/
  • Postgres Tools: try if you work with Postgres or Supabase (10 min). Install @postgrestools/postgrestools as a dev dependency so the extension can find the language server: https://github.com/supabase-community/postgres-language-server-vscode
  • Token count extension: try (2 min). It shows how big a file is in LLM tokens, in the status bar.
  • Cloak, Live Share, Figma, Project Manager, Noctis: skip. He says himself that he doesn’t use them, or only needs them for screen sharing.

TL;DR

Parker Rex walks through the extensions and settings.json he keeps the same across Windsurf, Cursor and VS Code. The list covers formatters and linters (Biome, Black, Ruff), visibility aids (Error Lens, GitLens, Pretty TypeScript Errors, Todo Tree), Vim emulation, and an LLM token counter. It is a broad inventory rather than a debugging-to-deploy workflow, and some of the tools overlap.

Key Points

  • He keeps Windsurf, Cursor and VS Code on the same extensions and settings, and says the reason was OpenAI buying Windsurf. 00:04
  • A token count extension in the status bar shows how large a file is “through the lens of an LLM”. 01:44
  • He recommends Biome for web projects as one Rust-based formatter and linter that replaces ESLint and Prettier. 02:11
  • For Python he uses Black for formatting and Ruff as the linter/formatter “that you combine with black”. 02:30
  • The ChatGPT macOS “work with code” integration lets the desktop app read the editor, but he doesn’t think it will replace in-editor agents. 02:59
  • Error Lens shows errors inline, GitLens shows file history and blame, and Pretty TypeScript Errors makes type errors readable on hover. 04:07
  • Postgres Tools gives Postgres language support inside the IDE, which he finds especially useful with Supabase. 05:36
  • He calls Vim emulation “maybe the most important” extension and has it tuned so it doesn’t hurt editor performance. 07:03
  • In settings.json he uses SF Mono Nerd Font (ligatures, icons) at 13/17, relative line numbers for Vim jumps, the Catppuccin Frappé icon theme, and per-language default formatters. 07:36
  • He keeps an “AI docs” folder in each app, holding examples, a memory bank and prompts, and credits the idea to IndyDevDan. 09:34

Notable Quotes

  • “biome I think is the way to go when you’re working with web projects” 02:11
  • “If you see red, go fix it.” 04:10
  • “Vim. This is the most maybe the most important one for me, but just being able to hop around using Vim motions.” 07:03

Verified Claims

Tools, Papers & Standards Mentioned

Follow-up Questions

  1. Does a workflow with Ruff only (lint + format) give the same results as Ruff + Black on a real repo, and how much faster is it in pre-commit and CI?
  2. How completely does Biome cover the ESLint rules and plugins that typical TanStack Start or Turborepo projects use, and what is still missing?
  3. What does the “AI docs” folder pattern (examples + memory bank + prompts) look like in practice, and does it measurably improve agent output in Cursor or Windsurf compared with tool-native rules files?

Sources