DFIR software developer
Currently: VP of Aon Cyber, Q Branch of Stroz Friedberg. Try not to break it, 007...
https://codeslack.blogspot.com
https://www.linkedin.com/in/jon-stewart-42b2b83/
DFIR software developer
Currently: VP of Aon Cyber, Q Branch of Stroz Friedberg. Try not to break it, 007...
https://codeslack.blogspot.com
https://www.linkedin.com/in/jon-stewart-42b2b83/
@dkegel Recommend playing with the "Superpowers" skills for Claude: https://github.com/obra/superpowers
Opus 4.5 with "brainstorming" and "write-plan" seems to lead to better outcomes when having Sonnet 4.5 execute the plan.
These aren't magic, but they do a nice job of managing context and reinforcing desired habits.
@geofflangdale A few weeks ago I installed a plugin to Claude Code (Jesse Vincent's "Superpowers" skills) and since then I've had my first real success creating a new CLI tool... until two days ago when I tried to add a new feature and it's gone horribly off the rails since then. The skills seemed to let it get some useful work done, on greenfield, but it could only forestall the shitting of the bed. Once things get to a certain level of complexity—and not very—they have a hard time.
I am finding them useful at debugging, creating plans forward when I'm too bogged down in analysis paralysis/procrastination, and as a research aide. But I feel like I'd have to give them a formal spec in order for them to write useful code, and so I might as well do most of the coding.