🌈 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 Public GitHub Repo != A Support Contract - As a developer frequently publishing code snippets on GitHub, I'm finding an increasing amount of my time being demanded for support and fixes. The reality is, I don't always have the time or resources to provide the help that each user deserves. 'Cloners beware' has become my motto as I try to remind others that using a public GitHub repo does not come with guarantees or warranties. Please remember, I'm a human with my own responsibilities and projects too.
Vibing a PCB - surprisingly good - In my latest adventure, I challenged AI to design a working ESP32-S3 development board from scratch using Atopile and Claude. The idea was as simple as vibe-coding actual hardware without diving into the code. It was a chaotic yet fascinating journey, with some misses like unwired components and a forgotten capacitor. After a few prompts, the AI delivered a surprisingly functional board featuring USB-C, an AMS1117 regulator, and status LEDs. While not yet perfect, vibe-coding feels like a glimpse into the future of hardware design.

Related Videos

Even more AliExpress gadgets - Another shamelessly overstuffed mailbag—cheers to PCBWay for fueling the bench carnage. I poked UV sensor cards with a curing lamp (they go purple then fade), sifted through robot gears, and lit some fragile LED filament letters (~2.7 V, happy around 100 mA). A USB photocatalytic mosquito trap spins at 0.02 A (teardown later), an OV7670 cam joins the ESP32/UVC experiments, and a chunky COB strip looks like a 12 V amp-gobbler. Bonus: surprisingly decent keyring torches with ‘police’ flash, a hilarious translation on a temp/humidity doodad, and watch oiler wands that are perfect for painting on solder resist—projects incoming.
I Asked AI to Design 12 ESP32 Dev Boards. It Said No. - I got bored of making one ESP32 dev board at a time, so I scripted the whole lot. After my favourite AI monkey told me to automate the repetitive bits, I built a pipeline that generates fully laid-out USB-native ESP32 dev boards for a dozen modules—schematics, placement, routing, silkscreen, and Gerbers—automatically. It uses a module database to choose safe pins, LED and boot pins, lays everything out in a standard USB-C two-layer format with differential USB pairs and ground pours, and publishes releases via GitHub Actions. You can fab them right away (thanks PCBWay), but treat them like open hardware: trust, verify, and tell me which ones to build.
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.
Tearing Down a Bistable Cholesteric Display - So, I finally tried out this bistable cholesteric display from my AliExpress stash after seeing Big Clive's teardown. It's super cool to play with, and I mean, it just clears up with a button press after you scribble on it. Gave it a whirl to understand the voltage involved and even ended up sparking it with some reverse polarity action (not the smartest move, I know). I might've broken it, but hey, it still sort of works manually. Check out Big Clive for a deeper dive into its reverse engineering, and remember to like and subscribe!
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.
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