VS Code
How do you extract the most out of VS Code?
Context
AI Coding
Extensions
Best Practices
Create a .vscode/settings.json to maintain consistent workspace settings
Use an .editorconfig file for basic editor settings:
root = true
[*]
indent_style = space
indent_size = 2
end_of_line = lf
charset = utf-8
trim_trailing_whitespace = true
insert_final_newline = true
[*.md]
trim_trailing_whitespace = false
Extensions
- git
- ESLint
- Nextjs Snippets
- Kubernetes
- NX Console
- Stripe
- Snapshot-Tools
- Hardhat Solidity
- Writing Tools
- Pretty TS Errors
Extract list of Extension using VS Code UI:
- Press Ctrl+Shift+P (Windows/Linux) or Cmd+Shift+P (Mac)
- Type "Show Extensions" and press Enter
- Click on the "..." (ellipsis) menu in the Extensions panel
- Select "Show Running Extensions"
code --list-extensions
Smart Contract Dev
Links
Questions
As AI coding tools like Claude Code increasingly operate outside the editor entirely, when does investing in VS Code extensions stop compounding and start competing with the terminal-first workflow?
- The Hardhat Solidity extension and NX Console both assume VS Code as the primary surface — how do you maintain smart contract development ergonomics when the AI agent is driving most of the edits?
- The
.editorconfigfile enforces basic consistency but VS Code workspace settings can override it — what is the minimal set of settings that must be in.vscode/settings.jsonto prevent drift across a multi-person team? - Pretty TS Errors makes TypeScript feedback readable in the editor — does this reduce the incentive to fix upstream type problems versus just reading better error messages at the point of use?