Ask HN: What are tools you have made for yourself since the advent of AI?

Go: A server and client for managing webhooks in development environments: https://github.com/onebusaway/hooks

Ruby on Rails: A volunteer 'jobs' board for OSS projects (ironically): https://ossvolunteers.com

JavaScript (client side+Cloudflare Worker): A map showing stop-level usage of OneBusAway across the Puget Sound region, updated daily: https://opentransitsoftwarefoundation.org/onebusaway/visuali...

Swift/iOS: An app that helps me track how much time I spend in the five heart rate zones, so that I can better focus my workouts. I'm working on version 2 right now, which will take advantage of some new features in iOS 27 and has an all new UI. https://www.zone2.app

nowplaying.cjlm.ca - CFUV radio station song identification, basically shazaming every few minutes from a fly.io instance

I made a streak/goal tracker that tracks the things I want to work on like being more grateful, working out more, and learning.

Not the author, but I had a good vibe coding go at it: https://force.nuts.services

Code: https://github.com/kordless/force-news

I built https://beachcomber.sh after one day getting huge lag and asking claude to investigate found that one of the factors was thousands of resources purely for giving my prompt, tmux statusline, nvim statusline, claude statusline the same identical information.

I probably would not have bothered to allocate time to this pre ai, the juice wasnt really worth the squeeze. But I approached it with an initial amusing naivete about it being 'super simple'. As is almost always the case with software theres a reasonable amount of hidden complexity. But I have been using it as a sort of learning proving ground for how to work with agentic development. For example I got to a point where claude wouldnt implement properly and would argue with me about changes because it would read the current/old docs in the repo and get confused about reality. So right now I'm experimenting with 'canonical specs' that can only be changed modally with gates and a defined cascade from canon, to code, to docs in that order. Otherwise you end up in a weird thrash about the docs and the code disagree and which one will the agent decide to change for consistency?

Anyway, its been interesting and its v0.6 and at a point where Ive not hit a sharp edge dogfooding for a while and some beta testers would be valuable. Right now you have to manually wire it into your stack, once some others have kicked the tyres hard enough I will make some pr's to the popular tools to consider integrating it.