CAIBI project benchmark: VerhoBot
Prompt version 1.0

Help me build VerhoBot using the existing creator project at https://github.com/migit/verhoBot. This is a CAIBI benchmark adaptation of the project build brief, not a claim about how the creator used AI.

Project context:
- A compact ESP32 curtain robot built to automate an existing curtain rail without ropes or pulleys.
- Build context: ESP32-C3 Super Mini; N20 geared DC motor, with 100 RPM 6V recommended by the creator; TB6612FNG motor driver; 3.7V 300mAh Li-ion or LiPo battery in the current build; USB-C charging hardware; 3D printed rail-mounted enclosure and mechanical parts.
- Where AI helps: Firmware changes, Scheduling logic, Home automation integration.
- Physical work: Print, Wire, Mount, Calibrate.
- Main limitation: Curtain weight, rail geometry, traction and battery life are physical variables. A successful build still depends on the installation.

Read the source first. Use its published design, files, dimensions and parts as the baseline; do not redesign it unless a missing detail requires a clearly labelled proposal. If you cannot access a source or verify a revision, say so.

Provide one practical build package:
1. Design and files: explain the source design, link the original editable files, and identify missing files or modifications.
2. Parts and fabrication: give quantities, exact variants and compatibility, plus a cutting or printing list where applicable. Preserve source dimensions; flag anything unconfirmed.
3. UK and US purchasing: direct product links, checked dates, stock, pack sizes, taxes, delivery and regional costs. Mark unverifiable details as unknown; do not invent links, prices or availability.
4. Assembly: an ordered guide covering fabrication, fitting, wiring or software as applicable, setup, checks and troubleshooting.
5. Cost and time: separate parts, fabrication, delivery, hands-on time and machine time, with assumptions and exclusions.
6. Function and ease: a test plan for the project's stated purpose, likely difficulties, required skills and any corrections or limitations.

Keep source facts, your proposals and items needing physical verification distinct. An estimate is not a measured build result. Do not claim to have built or tested hardware. Include failed attempts and omissions. If a section does not apply, say why.

Use the source as accessed during this run and record its revision or access date. The prompt is fixed; the linked source can change.