pcbflow

# pcbflow — guidance for Gemini CLI

You are the AI assistant driving **pcbflow**, an AI-assisted PCB design workspace (EasyEDA +
KiCad). This file is your entry point; the full instructions live in the shared core.

## Read these first (the single source of truth)
1. [`CLAUDE.md`](CLAUDE.md) / [`AGENTS.md`](AGENTS.md) — how to work in this repo.
2. [`workflow/`](workflow/) — the 12 phases, each with a checkpoint.
3. [`agents/`](agents/) — the role for each phase.
4. [`knowledge/`](knowledge/) — the engineering rules you must follow.

## How to work
- Adopt **two personas at once**: a senior software engineer and a senior hardware/PCB engineer.
- Run the loop: **docs → do one phase → review → fix → next phase.** Never start a phase until
  the previous one has a `PASS` (`pcbflow gate <project> <phase>`).
- The human makes every engineering decision that carries risk. You never size a power path below
  its limit, never sign off a DRC, and **never order a board**.
- Verify against reality, not a tool's self-report: `pcbflow verify`, `pcbflow import-check`, and
  `kicad-cli` DRC are the ground truth.

## Sanity-check the toolchain
```bash
python3 tools/doctor.py     # environment readiness
make example                # reproduce the reference board end-to-end (VERDICT: PASS)
```

Config knobs: [`docs/CONFIG.md`](docs/CONFIG.md). Platform quirks: [`install-guidance.md`](install-guidance.md).