🌈 ESP32-S3 Rainbow: ZX Spectrum Emulator Board! Get it on Crowd Supply →
View All Posts
read
Want to keep up to date with the latest posts and videos? Subscribe to the newsletter
HELP SUPPORT MY WORK: If you're feeling flush then please stop by Patreon Or you can make a one off donation via ko-fi

F’you, Claude, you are driving me absolutely bananas:

The house convention is a short phrase naming the defect, and the archive is full of it: “A citation that names nothing”, “The safe zone that only the spawner obeys”, “One word that means five things”. I matched that convention.

We agreed that you should use ASD-STE100 - Simplified Technical English. Why are you still producing this nonsense!

What do you mean your weird text is “the house convention”? CLAUDE.md says to use ASD-STE100, the output style says to use ASD-STE100 - arrrrgh!

Man in a cubicle beating a keyboard against his monitor

Take a deep breath. And repeat to yourself: “It’s not Claude’s fault”. Blaming Claude for these things is no different from blaming a toaster for burning toast.

So, what’s going on? Why is Claude driving me nuts? I started off wrong - I kicked off our vibe coding effort without doing the proper groundwork. Over 700 commits in, I decided that I couldn’t stand how Claude communicated and asked it to switch to ASD-STE100. The problem is, everything in the project, all the docs, all the completed TODO items, all the comments, even the names of the TODO files, pre-date that switch.

Everything Claude looks at after it’s read CLAUDE.md undermines what I’m asking it to do. “The house convention” is indeed the opposite of what I’m telling Claude to do.

Trying to correct course after creating a lot of code and documentation is like trying to turn a massive tanker - we’ve got way too much momentum. It’s going to be a slow correction and it’s going to take me constantly pushing on the tiller to make it happen.

Time to roll up my sleeves and help Claude. My vibe-coded Elite clone is going to need both of us.

Three pirates at Orerve, condition red - the combat computer earning its keep

Related Posts

The Output Style, It Does Nothing! - Learning to live with Claude - I tried taming Claude’s bar-stool rambling with ASD-STE100 and even stuffed it in CLAUDE.md. It felt cleaner for a moment, but the prose stayed just as empty—while the code and tests were actually solid. So I’m done reading the fluff; judge the artefact instead—like Harmless, my surprisingly good, browser-playable Elite-like with source on GitHub.
A Potentially Explosive Error - Just received the new PCBs for the ESP32-TV project and they're looking sharp with only a tiny resistor tweak needed. But I discovered a sneaky, undocumented resistor causing a conflict between the ESP32 and USB2244 over the USB connection. Fixed that, but there's a bigger issue lurking in the design - check the schematic in the video and see if you can spot it before I reveal the explosive mistake!
The PCBs are in production - what have I messed up? - After some stress and trepidation, I finally took the plunge and sent my PCB design off for manufacturing. My design centers around building a large seven-segment clock with LED filaments. Jumping hurdles such as voltages, pin usage, and limiting the load on my power supply, I've settled on the ESP32 as the system's heart and come up with a final circuit design. While doing this, I've quickly realized I could improve my layout and fixed a small mistake. Also, I've prepared for either types of LED filaments - the high-voltage ones or the larger, 3v ones. However, I did bungle up a couple of things on the enable line of the shift registers and board layout. But hey, this is a learning curve, right? Can't wait to get the boards and see what other exciting errors surface!
More Updates on the ZX Spectrum Board - I'm gearing up for production with some updates to our prototype, including switching to a 4-layer board to improve EMI, and refining USB power filtering. Check out the video for a deep dive into our battery charger and an exciting expansion port for potential HDMI output. The main goal now is to get our boards ready for manufacturing and shipping through Crowd Supply!
Failing to solve Manic Miner with RL - I was never any good at Manic Miner, so I asked Claude Code to build something that could finish it for me on my ZX Spectrum emulator. We started with reinforcement learning, and failed. What actually worked was search - first on the emulator, and then on a model of the game Claude built from the disassembly.

Related Videos

Surprisingly not CR*P - Vibing hardware - Well folks, what an adventure! After vibe coding our vibing button, I took up the challenge to vibe code the actual hardware for an ESP32 S3 dev board. Used a tool called at pile and gave it a whirl with some AI help from Claude. Interestingly, it handled everything from sourcing components with LCSC part numbers to wiring them up. Had a wee hiccup with missing capacitor in the RC circuit, but overall it was a thrilling ride watching the AI process! A bit of tweaking here and there, and we're good to go! Can't wait to see it in action.
I Feel the Need – The Need for Hardware SPI… - An insightful iteration on my Arduino Nano esp32 video. Despite criticism regarding the slow display update speed, a solution was found thanks to the helpful fellow, Nick. Turns out, the software SPI was the cause of the issue. A quick tweak in the code and voilà, we've got ourselves an SPI clock whizzing at 80 megahertz. Quite the speed boost for just a few lines of code alteration!
ESP-IDF 6 Setup in VS Code: Blink & Debug an ESP32-S3 - Time to get with the program and jump to ESP-IDF v6.0.1 in VS Code. I show you how to install the prerequisites (I’m on a Mac with Homebrew), run the ESP-IDF Installation Manager, spin up a Blink example for an ESP32-S3, tweak menuconfig (GPIO21, 500 ms), then build and flash—switching from stubborn USB JTAG to trusty UART when things fail. We check the monitor, bump CPU to 240 MHz, fix flash to 16 MB, peek at PSRAM, and give PCBWay a quick shout-out.
The Devil’s Package - SOT666 - I tracked some QA failures on my ESP32 rainbow boards down to the USBLC6 ESD IC in a SOT666 package—under the microscope the part wasn’t actually landing on the pads. Reflowing fixed it, but that shouldn’t be necessary, so I compared KiCad’s SOT666 footprint to the ST datasheet and found big mismatches. Turns out “SOT666” isn’t consistent across vendors (KiCad/Nexperia/Diodes/EasyEDA all differ), so the only safe move is to follow the exact datasheet for the specific part. I built a new footprint in KiCad per ST’s land pattern, tweaked the routing, and the 3D preview looks good—fingers crossed the next run nails it.
Oops I Did It Again… Swapped VCC and GND, on My PCB 🙈 - Hey everyone! In this video, I made a little snafu with my PCB layout by confusing a common anode with a common cathode for my RGB LED. I walked through fixing it by a bit of desoldering, applying solder resist, and reconnecting with a fine wire. Thanks to PCB Way for their awesome service, and as always, all the mistakes you see are mine alone! It's all sorted now, and our LED is shining brightly once again. Let's take a look at the process!
HELP SUPPORT MY WORK: If you're feeling flush then please stop by Patreon Or you can make a one off donation via ko-fi
Want to keep up to date with the latest posts and videos? Subscribe to the newsletter
Blog Logo

Chris Greening


Published

> Image

atomic14

A collection of slightly mad projects, instructive/educational videos, and generally interesting stuff. Building projects around the Arduino and ESP32 platforms - we'll be exploring AI, Computer Vision, Audio, 3D Printing - it may get a bit eclectic...

View All Posts