Read the engine's mind
You will write a spec BY HAND in the Studio's JSON editor — no palette — and deliberately break it four ways to hear every validator you have met. Then you will fix it and prove your repair with arithmetic before the engine confirms it.
- Hand-write a "Night Light" spec, 100mm x 80mm:
ldr_divideron GP26,led_5mm(red) on GP15,pushbuttonon GP14 (internal pull-up, active low),slide_switchon GP16. Include every required field from Lesson 2's table. Do NOT generate yet. - Predict components and traces with per-part arithmetic before touching Generate. (Check yourself afterwards: components 1 + 2 + 2 + 1 + 1 = 7; traces 2 + 4 + 3 + 2 + 3 = 14.)
- Generate. If the numbers differ from your prediction, find the arithmetic error — the engine is the referee.
- Break it four ways, one at a time, reading each message aloud: misspell
led_5mmasled5mm(V6); deletedivider_resistor(V7); move the LDR to GP15 (V8 — and a V5 message as well, because GP15 now has two claimants: one edit, two refusals, exactly as Lesson 3 warned); put the slide switch on GP14 (V5). Restore after each. - Delete the entire
peripheralsarray (not just its contents). Quote the message. Restore. - Save the working design as "PS-1 Night Light", then download the Gerbers and open the zip: count the files (11) and find the drill file — the bridge to PS-2, where this board gets a real layout review.