Objective
Your mission
Map the AI coding tool landscape by categorizing tools you know into four stable categories. Output: tool_landscape_map.md.
You need: A text editor. Internet to look up tools.
Time: 15 minutes.
Step 1: learn the four categories (5 min)
Every AI coding tool fits one of these:
1. Browser App Builders — Run in your browser. Type a description, get a full app with live preview and deploy button. Zero setup. Examples: Lovable, v0, Bolt.new, Replit Agent Best for: Prototypes, landing pages, first builds, getting to a live URL fast
2. IDE-Native Tools — AI inside your code editor. Full visibility into code, works with existing projects, shows every diff. Examples: Cursor, GitHub Copilot, Windsurf Best for: Existing codebases, multi-file changes, when you want to see every change
3. Terminal Agents — Command-line tools that edit your local files and run commands. Maximum control, maximum responsibility. Examples: Claude Code, Aider Best for: Git workflows, local development, when you need the AI to act as a full developer
4. Design-to-Code — Convert screenshots, mockups, or Figma files into working code. Examples: v0 (screenshot mode), Figma-to-code plugins Best for: When you have a visual design and want to skip describing it in words
Why categories matter more than brands
A new tool called "SuperCoder AI" launches tomorrow. Ask: Does it run in the browser with zero setup? → Browser app builder. Does it integrate into my editor? → IDE-native. Does it run in the terminal? → Terminal agent. Does it convert designs? → Design-to-code. Once you know the category, you know its strengths and limitations — without reading a tutorial.
Step 2: map tools you know (5 min)
List at least 5 AI coding tools you've heard of. Categorize each.
Write in your file:
## My Tool Landscape Map
1. [Tool name] — Category: [browser app builder / IDE-native / terminal agent / design-to-code]
Spans multiple categories? [no / yes — which ones and why]
2. [Tool name] — Category: [...]
...
(aim for at least 5)
Step 3: pick your category (5 min)
Based on your current skill level and the project you want to build (from Phase 00's scoping exercise):
Write in your file:
## My Category
Current skill level: [browser-only / basic terminal / terminal-comfortable]
Project I want to build: [name]
Category that fits: [which one]
Why: [1-2 sentences]
A new tool runs in your terminal, edits files on your machine and runs commands. Which category is it, and what follows?
Knowing the category tells you its strengths and risks without a tutorial: a terminal agent can change and delete real files, so you review and commit before big changes.