Chapter 4: Key Takeaways

Setting Up Your Vibe Coding Environment — Summary Card

1. Your vibe coding environment consists of seven core components: Python 3.10+, VS Code (with extensions), Claude Code (CLI), GitHub Copilot (inline completions), Cursor (AI-native IDE), Git (version control), and a properly configured terminal and shell.

2. AI coding tools run on remote servers, not your local machine. A stable internet connection is more important than a powerful processor. Your computer sends prompts to the cloud and receives responses back.

3. Always add Python to your PATH during installation on Windows. Forgetting this single checkbox is the most common cause of "python not found" errors. On macOS and Linux, use python3 and pip3 to avoid ambiguity with older system Python versions.

4. Claude Code requires Node.js as a prerequisite. Install Node.js 18+ first, then install Claude Code globally with npm install -g @anthropic-ai/claude-code. Configure your API key via the ANTHROPIC_API_KEY environment variable.

5. API keys are secrets — treat them like passwords. Never hardcode them in source files, never commit them to Git, and never share them in documentation. Use .env files with python-dotenv for project-specific keys, and add .env to your .gitignore immediately.

6. VS Code and Cursor are complementary, not competing. VS Code with Copilot handles inline completions and traditional editing workflows. Cursor provides deeper AI integration with inline editing (Ctrl+K), chat (Ctrl+L), and multi-file Composer (Ctrl+I). Start with one, explore the other later.

7. Create a virtual environment for every project. The command python3 -m venv .venv takes seconds and prevents hours of dependency conflicts. Activate it before installing packages, and use pip freeze > requirements.txt to record dependencies.

8. Your shell profile is your environment's configuration file. The ~/.bashrc (Linux), ~/.zshrc (macOS), or $PROFILE (PowerShell) file sets environment variables, aliases, and PATH entries every time you open a terminal. This is where API keys and tool paths belong.

9. Git should be initialized at the very start of every project. The recommended sequence is: create directory, initialize Git, create virtual environment, install packages, create .gitignore, and make your first commit. Version control from day one gives you a safety net for every change.

10. Follow the standard project setup order: directory, Git, venv, packages, .gitignore, commit. This sequence ensures version control tracks everything from the start, dependencies are isolated, and sensitive files are excluded before the first commit.

11. Use a verification script to confirm your setup. Running a script that checks all components saves time and catches configuration issues before they become debugging headaches. Re-run it whenever something seems wrong.

12. When troubleshooting, change one thing at a time. Changing multiple things simultaneously makes it impossible to identify which fix solved the problem — and may introduce new issues.

13. The which command (or where on Windows) is your best troubleshooting friend. It shows exactly which version of a program your shell is using, revealing PATH conflicts and wrong-version issues instantly.

14. The three AI tools serve different roles in your workflow. Copilot handles small completions (finishing lines, suggesting names), Claude Code handles complex reasoning (multi-file edits, debugging, architecture), and Cursor provides an AI-native editing experience. Use them together for maximum productivity.

Quick Reference: Essential Commands