Claude Code

I use Claude Code as a powerful tool to automate complex tasks ranging from hardware programming and 3D design to software development and data integration.

Categories:AI3D printingIOT3D

A topic page: a summary of what my posts say, with each claim quoted from the post it came from. The posts are the authority. Last checked 2026-11-06.

← Back to Posts

Summary. I use Claude Code as a powerful tool to automate complex tasks ranging from hardware programming and 3D design to software development and data integration. It assists me in navigating technical hurdles, such as toolchain configurations and complex system integrations, while I compare its capabilities against other specialized AI tools.

What the posts say

I used Claude Code to automate the creation of beatmaps and the integration of timed lyrics.

“It runs in a VR headset's web browser with nothing to install, and its code is published under the MIT licence.” — SingSaber

I used Claude Code to program a bare ATtiny85 through a USB programmer.

“It asked me to choose, and it recommended trusting the osx-cross/avr tap.” — ATtiny85 (Part 1)

I designed 3D printed parts with Claude Code based on measurements from a photo.

“The bar has no hole in the middle.” — 3D Printing (Part 3)

I connect Claude Code to the built-in Model Context Protocol server in Business Central.

“Business Central now ships its own Model Context Protocol (MCP) server, built directly into the product.” — Model Context Protocol (Part 4)

My custom skill is better for offline work than the official Dataverse plugin.

“My instructions have a long numbered list of rules about exactly those failures, and I learned every one of them the hard way.” — Claude Code (Part 16)

The official plugin adds a significant amount of tokens to every turn.

“A: The plugin adds about 1.1k tokens to every turn, even when I am not working on Dataverse.” — Claude Code (Part 16)

Claude Code uses a project-scoped .mcp.json file for specific configurations.

“Claude Desktop reads its MCP servers from claude_desktop_config.json; Claude Code reads them from a project-scoped .mcp.json file instead, the same file my earlier RAG series used for a local MCP server.” — Model Context Protocol (Part 4)

The daemon prevents the Arduino from resetting every time a new message arrives.

“The daemon opens it once and waits 2.5 seconds for the board to finish restarting.” — Claude Code (Part 17)

The posts behind this page

  • Claude Code (Part 17) — Asking Claude Code to find an Arduino Uno and a 2.6/2.8 inch TFT LCD shield, install the toolchain, fix an Apple Silicon compiler error, upload a test sketch that identified the ILI9341 display controller, and turn the screen into a Claude Code status light, then design and print a case for it
  • SingSaber — Turning songs from my iTunes music library into a WebXR rhythm game with synced karaoke lyrics, mashed up with Claude Code
  • 3D Printing (Part 3) — Two 3D printed versions of the back half of a rear light, one that fits the gap behind a mudguard and one that lets the cable leave through the side, designed with Claude Code and measured from a photo
  • Claude Code (Part 16) — Installing Microsoft's official Dataverse plugin from the Claude marketplace, connecting it to a Dataverse environment, and reading and writing records in plain English
  • ATtiny85 (Part 1) — Using Claude Code to program a bare ATtiny85-20PU through a USB Tiny AVR Programmer on an Apple Silicon Mac, after simulating the same circuit in Tinkercad
  • Spec-Driven AI Tools (Part 3) — Running BMAD's spec-build-review cycle twice on the same calculator and requests OpenSpec and Spec-Kit got: it's the only tool that asked instead of silently deciding, and its automatic three-layer review caught four real bugs before I saw them
  • Spec-Driven AI Tools (Part 4) — The comparison: what OpenSpec, Spec-Kit, and BMAD each did with the identical calculator and the identical two feature requests — where they genuinely agreed, where they quietly built different products, what it cost, and where the source article held up against running all three myself
  • Spec-Driven AI Tools (Part 1) — Running OpenSpec's full propose-apply-sync-archive cycle twice, for a Programmer Mode and a Statistics Mode on a plain-JS calculator, to see whether its delta specs really do become a living, accurate source of truth
  • Spec-Driven AI Tools (Part 2) — Running Spec-Kit's constitution-specify-plan-tasks-implement-converge cycle twice on the same calculator and requests OpenSpec got, including a caught integer-truncation bug and a caught math error in its own spec
  • Model Context Protocol (Part 4) — Connecting Claude Code to Business Central's built-in MCP server