zlacker

Cool stuff. The readme is pretty lengthy so it was a little hard to identify what is the core problem this tool is aiming to solve and how is it tackling it differently than the present solutions.

>>iddan+(OP)
A classic issue of AI generated READMEs. Never to the point, always repetitive and verbose

>>iddan+(OP)
This looks like a ticketing cli

>>mimisc+P6
And full of marketing hyperbole. When I have an AI produce a README I always have to ask it to tone it down and keep it factual.

>>mimisc+P6
I'm not saying it is or isn't written by an LLM, but, Yegge writes a lot and usually well. It somehow seems unlikely he'd outsource the front page to AI, even if he's a regular user of AI for coding and code docs.

>>mimisc+P6
Funnily, AI already knows what stereotypical AI sounds like, so when I tell Claude to write a README but "make it not sounds like AI, no buzzwords, to the point, no repetition, but also don't overdo it, keep it natural" it does a very decent job.

Actually drastically improves any kind of writing by AI, even if just for my own consumption.

>>zaphir+u7
That's exactly what this is, but it's one that's designed with coding agents in mind as its principle users.

>>iddan+(OP)
https://steve-yegge.medium.com/beads-best-practices-2db636b9...