pcbflow

# PCB Flow Handbook — Learn the Framework Step by Step

A guided path for electronics engineers. No programming background needed. Read it
in order the first time; after that, jump to whichever step you're on.

Each page follows the same shape so you always know what to expect:
**Purpose · What you need · What you get · What you do · What the AI does · What good
looks like · Common mistakes · Checklist · Next step.**

## The learning path

| # | Page | You'll learn |
|---|---|---|
| 01 | [Introduction](01-introduction.md) | what PCB Flow is, and how you and the AI split the work |
| 02 | [Installing the tools](02-installing-tools.md) | VS Code, an AI assistant, EasyEDA, KiCad, Git |
| 03 | [VS Code & your AI assistant](03-vscode-and-ai.md) | opening the workspace and talking to the AI |
| 04 | [Creating your first project](04-your-first-project.md) | starting a board and giving requirements |
| 05 | [BOM planning](05-bom-planning.md) | building and validating the parts list |
| 06 | [Schematic generation](06-schematic-generation.md) | the AI draws the schematic; you review it |
| 07 | [PCB placement](07-pcb-placement.md) | planning and placing components |
| 08 | [Routing](08-routing.md) | routing the board in KiCad |
| 09 | [Verification](09-verification.md) | the final engineering checks |
| 10 | [Manufacturing](10-manufacturing.md) | producing the files and ordering the board |
| — | [Glossary](glossary.md) | every software term, explained in plain English |
| 🪟 | [Windows setup](windows-setup.md) | using PCB Flow on Windows (`python`/`py`, the `.py` tools, close Chrome first) |
| 🍎 | [macOS setup](macos-setup.md) | using PCB Flow on macOS (Homebrew installs, the `.sh` tools work, the EasyEDA Bridge) |

## Two ideas to hold onto

1. **You are the engineer; the AI is your assistant.** It does the repetitive and the
   checking; you make the decisions. It never orders a board on its own.
2. **Nothing moves forward until it's confirmed correct.** Every step has a
   checkpoint. This is the same discipline as a good design review — just enforced
   at every stage.

> Stuck on a word like *API*, *Node.js*, or *repository*? It's in the
> [glossary](glossary.md). You rarely need these terms to use PCB Flow — but they're
> there when you want them.

---
Next ▶ [01 — Introduction](01-introduction.md)