AI agents

My posts explore the capabilities of AI agents in executing complex tasks, from building games and hardware integrations to automating legal documentation.

Categories:AIIOT

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.

Summary. My posts explore the capabilities of AI agents in executing complex tasks, from building games and hardware integrations to automating legal documentation. I examine how different agentic frameworks and tools handle ambiguity, verification, and the integration of local versus hosted models.

What the posts say

The agent successfully built the game, verified its own work through logic and headless-browser tests, and produced a fully functional product.

β€œDeepSeek Harness is a developer-preview tool where everything is a plugin β€” models, tools, sandboxes, storage, even the whole UI can be swapped or recomposed.” β€” DeepSeek Harness (Part 1)

The agent performed 96 Node logic checks to verify the game mechanics.

β€œ96 Node logic checks covering spawn, movement, collisions, shield erosion, respawn and invulnerability, UFO scoring, wave transitions, the ground-line game-over, and restart.” β€” DeepSeek Harness (Part 1)

The agent automatically installed the required toolchain and libraries when it found them missing.

β€œClaude created the project folder, discovered arduino-cli was not installed, and worked out the toolchain from scratch: checking serial devices, installing arduino-cli via Homebrew, then the arduino:avr core and LiquidCrystal library.” β€” Claude Code (Part 15)

The agent created a local wiki to store knowledge about the hardware quirks.

β€œAlong the way Claude also stood up a small .llmwiki in the project β€” its own notes on the board's real wiring and the sketch's design β€” so the next session starts from what was actually learned here rather than rediscovering the D12-is-really-D11 quirk from scratch.” β€” Claude Code (Part 15)

BMAD is the only tool that proactively asks for clarification on ambiguities.

β€œIt is the only tool that actually asked. Every ambiguity I tracked across this series β€” bitwise/word-size scope, negative-number representation, sample-vs-population standard deviation β€” BMAD stopped and asked me directly, as real choices, rather than silently deciding (OpenSpec) or silently deciding with written rationale (Spec-Kit).” β€” Spec-Driven AI Tools (Part 3)

The three-layer review process caught several bugs before I saw them.

β€œIts three-layer review found real defects and correctly rejected several false findings.” β€” Spec-Driven AI Tools (Part 3)

The local model required more detail because a specification for a cloud model is too loose for a 30-billion-parameter model.

β€œA specification good enough for a frontier cloud model can be far too loose for a 30-billion-parameter local model.” β€” DeepSeek Harness (Part 2)

The hybrid model works if the tasks are small and clearly defined.

β€œThe short answer: it works, provided the pieces are small and written down exactly.” β€” DeepSeek Harness (Part 3)

The posts behind this page

  • DeepSeek Harness (Part 3) β€” A hosted DeepSeek V4 Pro model builds Space Invaders and hands 15 small functions to qwen3-coder:30b subagents running on my Mac: every piece written locally, a playable game in 25 minutes for $0.40, and the two limits I found along the way
  • 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
  • DeepSeek Harness (Part 2) β€” Checking whether DeepSeek Harness's everything-is-a-plugin claim extends to the model itself: pointing it at a local Ollama-served model through a custom OpenAI-compatible provider, with no DeepSeek API key at all
  • Claude Code (Part 15) β€” Using Claude Code to detect, program, and debug a Arduino TinkerKit LCD Module
  • DeepSeek Harness (Part 1) β€” Giving DeepSeek Harness a product requirements document and a product design document for a faithful browser recreation of the 1978 Taito Space Invaders, and watching it build the game and then verify its own work
  • Claude Code (Part 14) β€” Using the page-line-summary skill in Claude Code to generate a deposition summary from a transcript PDF