I find myself reaching for tools like it-tools.tech or other random sites every now and then during development or debugging. So, I built a toolkit with a sane and simple CLI interface for most of those tools.
For the curious and lazy, at the moment, ut has tools for,
- Encoding: base64 (encode, decode), url (encode, decode)
- Hashing: md5, sha1, sha224, sha256, sha384, sha512
- Data Generation: uuid (v1, v3, v4, v5), token, lorem, random
- Text Processing: case (lower, upper, camel, title, constant, header, sentence, snake), pretty-print, diff
- Development Tools: calc, json (builder), regex, datetime
- Web & Network: http (status), serve, qr
- Color & Design: color (convert)
- Reference: unicode
For full disclosure, parts of the toolkit were built with Claude Code (I wanted to use this as an opportunity to play with it more). Feel free to open feature requests and/or contribute.
Although philosophically I prefer the unix approach of "do one thing and do it well", I really admire this tool. I think it might be the fact that the one thing this does well is curating a set of functions for a particular profile of developer. My story is someone doing web focused full stack development?
It might be worth doing a survey of your users to see what they use ut for and what areas you should focus on next.
The important part is that the user controls the entry points. It's more Unixy to allow someone to decode audio from one pipe to another than to only allow them to play a file to a speaker.
Consider that Debian "does" lots of things because it has a kernel, hardware abstractions, a userland, a package manager, and often a GUI and web browser. But it also "does" none of those because it's just a convenient and useful wrapper to publish all the other tools, which you can still call upon individually