I have a similar setup at home, I’m sure you heard this before but I must +1 the Infuse app on Apple devices. It’s a much better client than Jellyfin’s but can connect to Jellyfin server no problem. No plex needed.
Yes! Where it gets really interesting is the scenario in which every developer has their own unique review skill/workflow, so the reviews end up being different than you running it yourself, but nobody is reading them still.
Yes this is the path I’m taking. Experiment, build your own toolbox whether it’s hand rolled skills or particular skills you pull out from other public repos. Then maintain your own set.
You do not want to log in one day to find your favorite workflow has changed via updates.
Then again this is all personal preference as well.
I find it useful to make Claude track the debugging session with a markdown file. It’s like a persistent memory for a long session over many context windows.
Or make a subagent do the debugging and let the main agent orchestrate it over many subagent sessions.
I was doing the same, but recently I noticed that Claude now writes its plans to a markdown file somewhere nested in the ~/.claude/plans directory. It will carry a reference to it through compaction. Basically mimicking my own workflow!
This can be customized via a shell env variable that I cannot remember ATM.
The downside (upside?) is that the plan will not end up in your repo. Which sometimes I want. I love the native plan mode though.
Sometimes, it takes some effort to get to the rewarding part of an activity. A little pressure is not bad when it's helping you reach your goals. Millions of people force themselves to go to the gym.
People enjoy making things with their hands. They love conveying their emotions and adding their flair. If the masters did not deter people from picking up a paintbrush, why would AI slop?
reply