Skip to the content
2 layers70 × 45 mmBackpack defender, the printed circuit board in 3D

Let's see how quickly we can get a product idea off the ground.

Size
70 × 45 mm
Copper layers
2
Thickness
1.6 mm
Parts
55
Nets
38
Pads
184
Tracks, vias
521, 179
Pours
12
Routed
Yes
KiCad
KiCad 10.0 (file 20260206)
Created
27 Oct 2026
Updated
7 Nov 2026

Overview

Backpack defender is an open-source printed circuit board by donaldbell, from the donaldbell/productspeedrun repository on GitHub. It is a 2-layer board of 70 × 45 mm with 55 parts on 38 nets, routed with 521 tracks and 179 vias.

It is built around the ESP32-C3-WROOM-02-N4, MAX98357AETE+T and CC0603KRX7R9BB104, with the CL21A106KAYNNNE, CL21A226MAQNNNE and CL31A476MQHNNNE among its other parts. Its parts include 16 resistors, 13 capacitors, 4 connectors, 3 ICs and 3 diodes. It belongs with the ESP32 and RISC-V boards of this library.

Main components

12

README

README.md

Product Speedrun

A show about racing a random product idea from brainstorm to a showcase-ready concept. Each episode runs seven stages, and this repo holds the show console, every episode's work, and the public site.

  1. Roll & brief: roll ingredients with the Random Project Generator and write the brief.
  2. Concept sketches: AI concept art of the product in use.
  3. Control drawing: AI front, side and top views of the outside, which the 3D model traces its shape from.
  4. 3D model: Claude Code + Solidcraft build a first-pass model.
  5. Electronics: Claude Code designs a schematic, a routed KiCad board and a BOM, using the shared kit in tools/kicad/.
  6. Showcase: Claude Code builds an interactive product page.
  7. Keep or shelve: the hosts decide.

Run the show console

The easy way: double-click Start Product Speedrun.command in this folder. It stops any copy that's already running, gets the latest updates, starts the console and opens it in Chrome. Close its Terminal window to stop. To keep it handy, drag it to the right-hand side of the Dock. If macOS says it can't be opened the first time, right-click it, choose Open, then Open again.

It also opens Claude Code in this folder in a second Terminal window. To stop that, open the file in a text editor and change OPEN_CLAUDE_CODE="yes" to "no".

By hand: needs Node 20 or newer, no packages to install.

sh
npm start

Then open http://localhost:4321 in Chrome and share that window in Riverside.

Controls

KeyAction
← → or 1–7Change stage
N (or the button next to the stage name)Mark the stage done and move to the next one
EEpisodes: switch or start a new one
,Settings: image generators, room for your faces, sound
FFull screen
Click an imageShow it full screen (← → to browse, F to favorite, Esc to close)

In stage 1, click into the roller and use its own keys (Space to roll, 1–9 to cast off, Enter to lock in). The roll lands in the brief as you go: every roll, cast-off and re-roll updates it.

Stages also tick themselves off once their output exists: a roll and a product name, an image in stages 2 and 3, model.glb, a KiCad file or BOM, the showcase page, and the keep-or-shelve decision.

Drag files from anywhere onto stages 2–6 to add them to that stage's folder.

Prompts

The brief in stage 1 (what it is, what it does, what's inside, design language, a reference product and rough size) writes starting prompts for the concept art (stage 2), the control drawing (stage 3), and Claude Code in stages 4–6. Edit any prompt freely: edited prompts are kept, and Rebuild rewrites one from the brief. Copy puts it on the clipboard for Gemini, ChatGPT or Claude Code. Style buttons in stages 2 and 3 swap the drawing style.

Hero render

Stage 4 has a Hero render card. Once the model's iso.png screenshot exists, it writes a prompt for a photorealistic product shot that takes its shape from the CAD screenshot and its look from the favourite concept art. Press Generate render (needs a Gemini or OpenAI key), or Copy the prompt into Gemini with those two images and drag the result onto stage 4. Renders are saved as 4-model/render-*.png; mark one Use as hero and the showcase page and the public gallery use it as the episode's main image.

Image generation

Stages 2 and 3 can generate images in the console. Pollinations works with no setup (free, best effort). For better results and the ability to refine from a reference image, copy .env.example to .env, add a Gemini or OpenAI API key, and restart npm start. Keys stay on your computer: the browser never sees them. Each generated image is saved next to a .prompt.txt recording the prompt.

Stages 4–6 with Claude Code

Open Claude Code in this folder. Stages 4 and 5 run at the same time in two Claude Code windows: paste the stage 4 prompt into one, then go straight to stage 5 and paste its prompt into a second. They share the board's measurements through the episode's fit.json and pass change requests through FIT.md. Each of those stages has a prompt written from the brief: edit it, press Copy, and paste it into Claude Code, which follows CLAUDE.md and writes into the episode's folder. The console watches the folder, so the model, schematic, board, BOM and showcase page appear on screen as they're saved.

For stage 5, Claude Code only writes the parts list and placement for the new board. The kit in tools/kicad/ does the rest: the schematic and ERC, then placement, Freerouting, DRC, renders and the 3D board. The schematic shows up within seconds, the placed board in about a minute, and the routed board after 5–15 minutes of routing.

Leaving it running overnight

The model, board and showcase stages run after the recording. To let them finish while you sleep:

  • .claude/settings.json lets Claude Code run the project's own commands without asking each time: the board kit, the fit check, Python, Solidcraft, reading files and git add/commit. File edits in this folder are accepted too. Pushing to GitHub still asks, and it can't force-push, wipe changes, delete folders, read .env (your API keys) or edit the console's episode.json and rev.json. To see or change the list, type /permissions in Claude Code.
  • When Claude Code would normally stop to ask you something, it writes the question under "Questions for the hosts" in that stage's NOTES.md, takes the safer option and carries on. Each stage's NOTES.md starts with a summary for the morning.
  • The launcher keeps the Mac awake while the console is open (the screen can still turn off). Leave it plugged in with the lid open, since closing the lid sleeps it anyway.
  • In the morning, read the summaries, then Publish from the console.

Back on the bench: revisions

While Claude Code builds this week's model and board, the show revisits an older product. Products marked Keep building in stage 7 wait on the shelf at the bottom of the Episodes menu (E). Start Rev B copies the product's latest model and electronics into products/<product>/rev-b/ and opens the revision workbench:

  • The latest model, board and fit check on the left, with the open questions from the last revision's notes. + CAD, + Electronics and + Code add a question to that track's feedback.
  • Goals and guest for this revision, then a card per track: CAD, Electronics, Code (firmware, usually done off air in VS Code with PlatformIO) and Showcase. Type feedback and the card writes the Claude Code prompt; Copy prompt and paste it into Claude Code. Mark done when a track is finished.
  • Hero render: each revision gets its own photoreal render, made the same way as in stage 4 but from the revision's new iso.png, with the previous revision's hero as the style reference so the look stays consistent. Generate render, or Copy prompt into Gemini and drag the result onto the workbench. Mark one Use as hero and the revision's showcase page and the gallery card use it.
  • Publish Rev B to the site commits and pushes the revision. The gallery card then shows the latest revision and links every revision's page.

The episode itself stays as aired (Rev A). Revisions go B, C, D… and Start Rev C asks for a second click so you don't start one by accident.

Episode folders

text
episodes/001-plant-whisperer/
  episode.json     roll, brief, prompts, favorites, decision (written by the console)
  2-concept/       3-layout/       4-model/       5-electronics/       6-showcase/

Licence

Everything here is open, and you're free to build, change, share and sell it, products included:

  • Hardware designs (KiCad projects, CAD models, BOMs): CERN-OHL-P v2, the permissive CERN Open Hardware Licence.
  • Writing, images and pages (concept art, renders, notes, showcase pages): CC BY 4.0.
  • Software (the console, the KiCad kit, scripts): MIT.

All three ask you to keep the credit and licence notices. Credit line for reuse: Based on Product Speedrun episode NNN by Donald Bell and <guest>, https://donaldbell.github.io/productspeedrun/. Each episode's guest is a co-creator, credited on its showcase page and in CREDITS.md.

The name "Product Speedrun" isn't licensed: sell what you like based on these designs, but please don't present it as an official Product Speedrun product.

A request, not a requirement: if you build or sell something based on these designs, we'd love a credit and a link back, and we'd love to hear about it.

LICENSE has the details, including a note on AI-generated concept art.

Public site

In stage 7, Publish to the site commits the episode's folder and pushes it to GitHub using your own git setup, so the decision and any last changes reach the public site. You can also commit and push by hand.

Every push to main builds a gallery of all episodes with links to each showcase page, and publishes it to GitHub Pages. In the repo's Settings → Pages, set the source to GitHub Actions once. To preview locally: npm run build:site, then open _site/index.html.

Parts

55
QtyValueFootprintReferences
4100kResistor_SMD:R_0603_1608MetricR9, R11, R16, R17
4100nFCapacitor_SMD:C_0603_1608MetricC4, C6, C10, C11
410kResistor_SMD:R_0603_1608MetricR5, R6, R7, R8
410uFCapacitor_SMD:C_0805_2012MetricC1, C5, C8, C9
4M2MountingHole:MountingHole_2.2mm_M2H1, H2, H3, H4
31MResistor_SMD:R_0603_1608MetricR1, R3, R4
3FiducialFiducial:Fiducial_1mm_Mask2mmFID1, FID2, FID3
2100Resistor_SMD:R_0603_1608MetricR10, R18
222uFCapacitor_SMD:C_0805_2012MetricC2, C3
247Resistor_SMD:R_0603_1608MetricR14, R15
247uFCapacitor_SMD:C_1206_3216MetricC12, C13
2AO3401APackage_TO_SOT_SMD:SOT-23Q1, Q3
2WhiteLED_SMD:LED_0603_1608MetricD1, D2
11uFCapacitor_SMD:C_0603_1608MetricC7
11uHInductor_SMD:L_Changjiang_FXL0624L1
1220kResistor_SMD:R_0603_1608MetricR2
12xAAA leadsConnector_Wire:SolderWire-0.25sqmm_1x02_P4.2mm_D0.65mm_OD1.7mmJ1
13V3TestPoint:TestPoint_Pad_D1.5mmTP2
1AO3400APackage_TO_SOT_SMD:SOT-23Q2
1ESP32-C3-WROOM-02-N4RF_Module:ESP32-C3-WROOM-02U2
1GNDTestPoint:TestPoint_Pad_D1.5mmTP3
1MAX98357AETE+TPackage_DFN_QFN:TQFN-16-1EP_3x3mm_P0.5mm_EP1.23x1.23mm_ThermalViasU3
1PIR leadsConnector_Wire:SolderWire-0.25sqmm_1x03_P4.2mm_D0.65mm_OD1.7mmJ4
1POWERButton_Switch_THT:SW_Slide_SPDT_Angled_CK_OS102011MA1QSW2
1PROG (TC2030)Connector:Tag-Connect_TC2030-IDC-NL_2x03_P1.27mm_VerticalJ2
1SILENCEButton_Switch_THT:SW_PUSH-12mmSW1
1SpeakerConnector_Wire:SolderWire-0.25sqmm_1x02_P4.2mm_D0.65mm_OD1.7mmJ3
1TPS61023DRLRPackage_TO_SOT_SMD:SOT-563U1
1VBATTestPoint:TestPoint_Pad_D1.5mmTP1
1WS2812B-2020LED_SMD:LED_WS2812B-2020_PLCC4_2.0x2.0mmLED1

More from donaldbell/productspeedrun

4
  • 2 layers70 × 45 mmBackpack defender, the printed circuit board in 3D

    Backpack defender

    donaldbell/productspeedrun

    Let's see how quickly we can get a product idea off the ground.

    43 parts
  • 2 layers54 × 31 mmGamer companion, the printed circuit board in 3D

    Gamer companion

    donaldbell/productspeedrun

    Let's see how quickly we can get a product idea off the ground.

    41 parts
  • 2 layers30 × 30 mmBmm receiver, the printed circuit board in 3D

    Bmm receiver

    donaldbell/productspeedrun

    Let's see how quickly we can get a product idea off the ground.

    33 parts
  • 2 layers52 × 24 mmBmm sensor, the printed circuit board in 3D

    Bmm sensor

    donaldbell/productspeedrun

    Let's see how quickly we can get a product idea off the ground.

    32 parts

Similar boards

  • 4 layers88.1 × 59.4 mmChromapi motherboard v1, the printed circuit board in 3D

    Chromapi motherboard v1

    Mowibox/chromapi_motherboard

    Raspberry Pi control HAT dedicated to the quadruped robot Chromapi.

    139 parts2Apache-2.0
  • 4 layers118 × 76 mmSmart led badge, the printed circuit board in 3D

    Smart led badge

    zgeez/Pixel-Badge

    Wearable 32x32 LED badge with Zephyr firmware, BLE control, passive NFC, and a Flutter Android app, built around a custom nRF52840 PCB.

    1,236 partsMIT
  • 2 layers45 × 100 mmWalkiepcb, the printed circuit board in 3D

    Walkiepcb

    houseofthe051010/ESP32-Walkie-Talkie-V2

    This ESP32 Walkie Talkie is redesigned with a SX1262 radio, a PCB, and a full case redesign.

    93 parts1
  • 4 layers128 × 51.4 mmQuack face, the printed circuit board in 3D

    Quack face

    HeyPCB/quack-face

    Face board for the Open Duck Mini's head: eye LEDs, projector driver, I2S amp and mic, antenna servos, shaped to the head. 4-layer KiCad 10 board plus printed standoffs, fit-checked in the head CAD.

    55 partsCERN-OHL-S-2.0
  • 4 layers90 × 50 mmCryobelt, the printed circuit board in 3D

    Cryobelt

    michael201110/cryobelt

    100 parts1
  • 4 layers65 × 56 mmSensor HAT, the printed circuit board in 3D

    Sensor HAT

    Eniemooo/Sensor-HAT

    Open-hardware indoor air sensor (CO2, VOC/NOx, T/RH, light, sound): HAT for Raspberry Pi or standalone with Seeed XIAO + ESPHome. KiCad 10.

    112 parts
  • 2 layers58 × 42 mmAquarium mine ctrl, the printed circuit board in 3D

    Aquarium mine ctrl

    develmusa/Thermomine

    Thermomine is a 3D-printed naval mine that sits on the gravel of your tank. A sealed LED inside glows blue when the water is too cold, green when it's just right, and red when it's too warm.

    25 parts
  • 2 layers110.1 × 110.4 mmMini, the printed circuit board in 3D

    Mini

    makerspet/oomwoo-esp32s3-cm

    Pi CM4/CM5-compatible Compute Module using ESP32-S3 instead of CPU

    116 parts1Apache-2.0

Questions

How big is the Backpack defender PCB?

It measures 70 × 45 mm and has 2 copper layers, 1.6 mm thick.

What parts does the Backpack defender use?

55 parts, built around the ESP32-C3-WROOM-02-N4, MAX98357AETE+T, CC0603KRX7R9BB104 and CL21A106KAYNNNE. The full list of its parts is on this page, with links to each part's symbol and footprint where PCBKit's library has them.

Where can I download the Backpack defender KiCad files?

From the donaldbell/productspeedrun repository on GitHub, at the commit this page was made from: the board is products/backpack-defender/rev-b/5-electronics/backpack-defender.kicad_pcb and its schematic episodes/001-demo-1/5-electronics/backpack-defender.kicad_sch. PCBKit opens the board in the browser, with nothing to install.

Can I use the Backpack defender design in my own project?

Its repository states no licence, so its author keeps all rights: ask donaldbell before reusing the design.