chore: add VSCode extensions recommendations

[kpj2006]

Addressed Issues:

Fixes #(issue number)

Screenshots/Recordings:

Additional Notes:

Checklist

• My code follows the project's code style and conventions
• I have made corresponding changes to the documentation
• My changes generate no new warnings or errors
• I have joined the Discord server and I will share a link to this PR with the project maintainers there
• I have read the Contributing Guidelines

⚠️ AI Notice - Important!

We encourage contributors to use AI tools responsibly when creating Pull Requests. While AI can be a valuable aid, it is essential to ensure that your contributions meet the task requirements, build successfully, include relevant tests, and pass all linters. Submissions that do not meet these standards may be closed without warning to maintain the quality and integrity of the project. Please take the time to understand the changes you are proposing and their impact.

Summary by CodeRabbit

• Chores
  • Added recommended development extensions for Visual Studio Code users, including Markdown, Git, formatting, GitHub integration, REST client, Docker, ESLint, YAML, spell checking, and debugging tools.

[coderabbitai]

Walkthrough

A .vscode/extensions.json configuration file is added to specify recommended VS Code extensions for the repository. The file declares 14 extensions covering formatting, linting, Git integration, Docker support, and language tooling to establish a consistent development environment.

VS Code Extensions Configuration

Layer / File(s)	Summary
VS Code extensions recommendations .vscode/extensions.json	A recommendations array lists 14 VS Code extensions including Prettier, ESLint, Markdown linting, Git Graph, GitHub Pull Requests, Docker, Draw.io, REST Client, EditorConfig, YAML support, Error Lens, spell checker, and Markdown preview tools.

---

🎯 1 (Trivial) | ⏱️ ~2 minutes

---

• Zahnentferner

---

🐰 With whiskers twitching and nose held high,
A config file hops right on by,
Extensions recommended, fourteen strong,
Tools aligned to help devs along!
VS Code shines, a workspace so bright. ✨

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: adding VSCode extensions recommendations to the repository configuration.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

	Messages
📖	⚠️ PR Template Check These are non-blocking, but please fix: Please replace the placeholder Fixes #(issue number) with the actual issue number (e.g. Fixes #42). Some required checklist items are not completed: My PR addresses a single issue

Generated by 🚫 dangerJS against 616de4f

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.vscode/extensions.json:
- Around line 3-17: The extensions array contains inline C-style comments (e.g.,
after "DavidAnson.vscode-markdownlint", "eamodio.gitlens", etc.) which makes the
JSON invalid; remove all trailing comment text beginning with // so each entry
is just a quoted string (e.g., "DavidAnson.vscode-markdownlint") with proper
commas and the surrounding array/JSON structure intact, then validate the file
with a strict JSON parser (jq or similar).

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: e68cca81-37eb-4ef3-acee-e137b41fd7a8

📥 Commits

Reviewing files that changed from the base of the PR and between 549c2f8 and 616de4f.

📒 Files selected for processing (1)

• .vscode/extensions.json