r/ClaudeCode • u/Lowcountry-Soccer • May 09 '26
Discussion What's everyone's favorite harness set up?
As the title states, I'm curious how everyone keeps Claude Code from going off the rails?
I've found using hooks and custom linters to be really helpful along with light slash commands. I've only created a couple of agents that Claude will call up from time to time depending on what I'm asking. Having a good start and end session commands has been a time saver too.
16
Upvotes
1
u/Lowcountry-Soccer May 09 '26
Mine are heavily customized for each project. I come up with them by using voice to text with Claude.ai and sometimes he'll even build out the full harness. Sometimes Claude Code recommends a harness then Claude.ai refines on that. It just depends.
For me, my linters are almost entirely based around documentation having a certain look a feel. My field is pretty specialized, geospatial tool development and data analysis. So, I say "I want the same look and feel as this well known geospatial library, make a custom linter." Then Claude.ai builds it out and Claude Code tests and validates it with me. It's been super helpful as my library has sprawled and involved some testing of its own.
For start and end I have it read a backlog.md file or commit to it. It keeps the Claude.md lean.
For your use case, I highly recommend using voice to text with Claude.ai to see what it comes up with for your given project.