2/5 VSCode Isn't a Code Editor. It's an AI Workspace.
Previous: Markdown Is the Interface Between You and AI
In Post 1, you wrote a fairy tale outline in Markdown. You could have done that in Notepad. So why do you need VSCode?
Because VSCode isn’t a text editor. It’s an environment where you write, preview, version-control, and AI-assist your content — all in one window. 100 million developers already use it. 50,000+ extensions. And it’s free.
The key insight: every feature developers use for code works just as well for content.
The Setup (10 Minutes)
Install VSCode
Download from code.visualstudio.com. Windows, Mac, Linux.
Install Four Extensions
Open the Extensions panel (Ctrl+Shift+X) and install:
| Extension | What it does |
|---|---|
| Markdown Preview Enhanced | Live preview of your Markdown next to your editor |
| Mermaid Markdown Syntax Highlighting | Syntax highlighting for diagrams in Markdown |
| Marp for VS Code | Preview and export Marp presentations |
| GitHub Copilot | AI assistant ($10/month or free for students/OSS) |
That’s it. Four extensions. You now have a complete AI content workspace.
For details on what each Markdown feature does, see Markdown Essentials. For Mermaid diagram types, see Mermaid Diagrams: When Text Becomes Visual.
The Workspace Concept
Create a folder. That’s your project. Everything lives inside it — Markdown files, images, configuration, AI instructions. VSCode calls this a “workspace.”
algorithm-fairy-tales/
├── tales/
│ └── lady-binary.md ← your file from Post 1
├── presentations/ ← slides (Post 5)
└── AGENTS.md ← AI instructions (Post 4)
Open the folder in VSCode: File → Open Folder. Now the sidebar shows your project structure. Every file is one click away. AI tools see the whole project, not just a single chat message.
Live Preview: See What You’re Writing
Open lady-binary.md. Press Ctrl+Shift+V (or click the preview icon in the top-right). Your Markdown renders as formatted text in a split pane.
Edit the left pane. The right pane updates instantly.
This is what replaces the copy-paste loop between a text editor and a chat interface. You write, you see, you iterate — all without switching windows.
Why VSCode Beats Chat Interfaces
If you’ve been writing content by chatting with ChatGPT or Claude, you know the friction:
| Chat interface | VSCode workspace |
|---|---|
| Content lives in a conversation thread | Content lives in files you own |
| Context resets between sessions | Files persist forever |
| Single document at a time | Multiple files open simultaneously |
| No version history | Full Git history of every change |
| Copy-paste to use the output | Output IS the file |
| AI sees one message | AI sees your entire project |
The workspace model is fundamentally different: your content is the source of truth, and AI assists within it — not the other way around.
Git: Your Undo Button on Steroids
Git tracks every change to every file. For non-coders, here’s what matters:
- Commit = a checkpoint. “Everything looked good at this point.”
- Diff = what changed since the last checkpoint.
- Branch = an experiment. Try something wild without risking your working version.
- Revert = go back to any checkpoint, instantly.
Your First Commit
Open the terminal in VSCode (Ctrl+`` ) and run:
cd algorithm-fairy-tales
git init
git add tales/lady-binary.md
git commit -m "Initial fairy tale outline"
Done. Your first checkpoint. Now you can change anything fearlessly — you can always get back here.
VSCode’s Source Control panel (Ctrl+Shift+G) shows changes visually. Green lines are additions. Red lines are deletions. Click to see exactly what changed.
Why This Matters for AI Workflows
When you ask Copilot to rewrite a section and it ruins the tone, you don’t undo manually. You git diff to see exactly what it changed, keep what works, and revert what doesn’t.
Git turns AI collaboration from “hope it works” into “experiment safely.”
Hands-On: Set Up the Fairy Tales Project
-
Create the folder structure:
algorithm-fairy-tales/ ├── tales/ │ └── lady-binary.md └── presentations/ -
Move your
lady-binary.mdfrom Post 1 intotales/ -
Open the folder in VSCode
-
Open
lady-binary.mdand split the view: editor left, preview right -
Initialize Git and make your first commit
You now have: a structured project, live preview, and version control. The same setup a developer uses for code — but for your fairy tale.
Next post, we add the AI. Copilot will expand that outline into a full story and generate a Mermaid diagram of the binary search algorithm.