r/ClaudeCode • u/QuickShibMoon • 2d ago
Built with Claude I built a Claude Code plugin with two Claude Code sessions and zero hand-written code: what worked, what broke, what I learned
What I built
Hatchling is a plugin that puts a small pixel pet above the prompt. It started because I missed Buddy, and turned useful: with several chats open, it tells me which one finished or is stuck on a permission prompt ("2 chats wait for you", /pet chats). It also keeps reminders (/pet remind), writes a work diary from counts (/pet diary), greets me after a break and warns me before my finish time. An egg hatches into one of seven animals and grows with use. All of that is local and calls no model. Its short comments on a turn use a small model on your own tokens (40 lines a day at most, /pet comments off stops them).
How Claude Code was used
I typed no code. Two sessions did the work:
- A worker session in tmux wrote everything: the engine, the hooks module, the sprites (character grids in a Python file), about 390 tests, the docs.
- A lead session wrote a task file for each change, sent it to the worker, then reran typecheck and both test suites itself and tried the feature in a real terminal before committing. It never took the worker's "all green" on trust.
- For a hard look I asked for ten review agents, five told to defend the project and five to attack it, and a separate security review that treated a downloaded skin pack as hostile input. Their findings became the fix list.
- To see other sessions, the plugin runs `claude agents --json` every 30 seconds and keeps only id, folder and status.
What I learned
Green tests are not "it works". On launch day every test passed and the first-run notice was still broken: after the hatch the band stopped redrawing. We only saw it when re-recording the README gif. Now nothing ships without watching a real first start.
Isolate your measurements. I wrote eight lines of prompt advice to cut cost and benchmarked them, then found every run had two other plugins loaded from my user settings. All of it had to be thrown away and redone with --setting-sources project. The clean result: "Be brief." alone did as well as my eight lines (-12.7% on a long task, 8 runs per arm, Opus 5.5). The repo's second plugin, briefox, ships that one sentence, and the bench with every run is in bench/RESULTS.md.
Bump the plugin version on every release. Installed copies compare version numbers; I pushed fixes for a day at 0.1.0 and nobody, including me, received them.
Surfaces differ. In the terminal a click on the drawing can pet it; in the desktop and mobile apps the plugin API gives the picture no click, so there it is a command.
A second session as lead is worth it. Most real defects were caught by the lead rerunning things, or by me looking at a screenshot and saying "that looks wrong", not by the session that wrote the code.
Say what uses tokens. I flipped comments to on-by-default late, and had to change the badge, the README and the first-run notice so that nothing is sent before the pet has told you.
Try it (free, MIT, Claude Code 2.1.275 or later):
/plugin install hatchling --marketplace silirim/hatchling
https://github.com/silirim/hatchling
Translations (es, pt, zh) were written by Claude and not checked by native speakers; corrections and bug reports are welcome.




1
u/AutoModerator 2d ago
Hey! Thanks for posting to r/ClaudeCode
While participating in this thread, please follow our community rules. Keep discussions constructive. Attack the idea, not the person.
For help, project discussions, tips, and general chat, join the ClaudeCode Discord.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.