vibecode.wiki
RU EN
~/wiki / rabochee-mesto / редактор-кода-ставим-основу-рабочего-места

VScode: laying the foundation of the workplace

◷ 4 min read 1/31/2026

Next step

Open the bot or continue inside this section.

$ cd section/ $ open @mmorecil_bot

Article -> plan in AI

Paste this article URL into any AI and get an implementation plan for your project.

Read this article: https://vibecode.morecil.ru/en/rabochee-mesto/%D1%80%D0%B5%D0%B4%D0%B0%D0%BA%D1%82%D0%BE%D1%80-%D0%BA%D0%BE%D0%B4%D0%B0-%D1%81%D1%82%D0%B0%D0%B2%D0%B8%D0%BC-%D0%BE%D1%81%D0%BD%D0%BE%D0%B2%D1%83-%D1%80%D0%B0%D0%B1%D0%BE%D1%87%D0%B5%D0%B3%D0%BE-%D0%BC%D0%B5%D1%81%D1%82%D0%B0/ Work in my current project context. Create an implementation plan for this stack: 1) what to change 2) which files to edit 3) risks and typical mistakes 4) how to verify everything works If there are options, provide "quick" and "production-ready".
How to use
  1. Copy this prompt and send it to your AI chat.
  2. Attach your project or open the repository folder in the AI tool.
  3. Ask for file-level changes, risks, and a quick verification checklist.

Code Editor: Why It Is the Basis of Everything

In short, the code editor is your primary workspace. Not AI, not a model and not a clever setting, namely the editor. In vibcoding, everything is built around it, because here the AI generates the code, and you follow the process.

Why an Editor When AI Writes Code

Many beginners ask: if AI can create code for me, why even an editor? Why not just chat with AI and get ready?

The fact is that code is not just words. These are files, structure, versions, and relationships. Without an editor, you can’t see where the AI added a line, changed a function, or broke logic. The editor gives control: you observe the changes, roll back the mistakes and understand what is happening in the project.

In the end, an editor is needed to:

  • Storage of project files.
  • Tracking edits from AI.
  • Return to previous versions (via Git or just copies).

Without it, vibcoding slides into chaos, where every prompt is a lottery.

Why is it that VS Code is

First, choose Visual Studio Code (VS Code). Not because he's "perfect" or "coolest," but because:

  • Free and open.
  • It works on Windows, macOS, Linux.
  • Simple interface, like a regular program.
  • Easily connects AI extensions (such as Cursor or Codex).

Remember, this is not an eternal choice. Start with VS Code and then, if necessary, go to Cursor, PyCharm or something else. The main thing is to start without barriers.

How to Install VS Code

It's simple and simple

  1. Go to the official Visual Studio Code website.
  2. Choose a version for your OS (Windows, macOS or Linux).
  3. Download and install like any program - click "Next" and wait.
  4. Launch VS Code. Ready, no activations or keys.

If something goes wrong (rarely), just restart the installer or check the antivirus.

What you will see on the first launch and what to ignore

When you open VS Code, you will see panels, buttons, and a welcome screen. Don't be scared, it's okay. At the start, focus on the minimum:

  • File window (conductor on the left).
  • Central area for text (where files are opened).
  • File > Open Folder menu to open the folder.

Ignore the rest (themes, extensions, terminal) for now. They will not speed up your start, they will only confuse you.

How to open the project folder

VS Code comes to life when linked to a project:

  1. Create an empty folder on your computer (for example, “my first project” on your desktop).
  2. In VS Code, go to File > Open Folder and select this folder.
  3. Now you'll see the structure on the left: even if there are no files, it's your project.

From now on, all actions (AI code generation, edits) will be here. This is a key step – the project becomes “live”.

Why you should not set up immediately

A common mistake: immediately climb into the settings, put themes, fonts and plugins on advice from the Internet. This gives the illusion of progress, but distracts from the essence.

Leave VS Code "boring" by default. When you start working with AI (e.g., generating code through prompts), you’ll understand what’s missing and add what you need. It saves time and nerves.

Key lessons at this stage

You don't learn to code here. You're mastering space:

  • Where the project is stored (folder on disk).
  • Where files and changes are visible (conductor in VS Code).
  • How the AI will inject the code here.

If that's clear, you're ready for the next step in vibcoding. Next, you can add AI extensions, but about this in other articles.