Currently working on a philosophy paper (and a major app deploy) on this sort of feeling of tools being shaped by us as we use them. Things I've noticed: 1) I've got my own fork of someone's fork of superpowers, and every time the process displeases me, I edit the process. I've managed to do a fairly chunky enterprise app released to 800 active students in... 6 weeks. (Happy to link you to it, but I won't drop links by default here. Github: denubis-plugins is my fork of a fork). The point of this is not "ooo, look at these nice things" but -- I can customise how I think through and work through specifications and UATs to standards that I wish teams I spent 25k/fortnight on were held to.

One specific tweak to bring to your attention is: have Claude have a start of session hook to change your terminal background based on your branch and repo. It makes context switching so much easier.

Another tweak is "disable tools you don't use." -- be mindful of what skills and what lives in your context, as each token you don't use is a reset. I've got a fish plugin to disable the jupyter notebook tool, the planning mode tool (my much higher formalism skills suit my needs more effectively) and others based on your own use case.

A third is *consider* things like rtk-ai. (I've had to tweak the shell script significantly), as tool output is an utter waste of input tokens. Don't just autoinclude it.

Happy to discuss any of these further.
-Brian