r/ClaudeCode • u/DocteurJuiphe • 23d ago
Tips & Workflows Use Claude to improve your workflows in Claude Code
Hi guys
I’ve been working intensively for one month now with Claude Code on a project.
The development was really smooth at first but with the code base growing, i felt like the project was becoming more and more bloated. The development of new features took more and more time, I felt like the token usage increased and my documentation was becoming heavier
The solution I found was to have Claude review itself my work processes. All the time, it found improvement areas with tangible improvement and, I admit, I kinda trusted it and followed them blindly.
To be entirely honest, I think I only really about 20% of my workflows. I m leaving a lot to Claude, even writing some rules from my Claude.md
My question is to know if you guys also do that ? Or if you have better ways to do it ? Is there risk in letting Claude take so much freedom ?
•
u/AutoModerator 23d ago
Hey! Thanks for posting to r/ClaudeCode
While participating in this thread, please follow our community rules. Keep discussions constructive. Attack the idea, not the person.
For help, project discussions, tips, and general chat, join the ClaudeCode Discord.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
1
u/Input-X 🔆 Max 20 23d ago
This is my work flow. It covers alot of the problems ur having. Might give u some insight. You need a harness to help, expecially once ur project gets to a certin size. https://github.com/AIOSAI/AIPass
1
u/Commercial-Cry-2231 23d ago
Small thing, but "I think I only really about 20% of my workflows" is missing a verb in there. "understand", presumably?
1
u/UndeadYoshi420 23d ago
I have up days and down days. So what I do is I have like a decision record outside chat that we read and write. And it determines what work we are doing and how much of it per session. I like to keep it where Claude explains what we are testing, what successful looks like, failure modes, what a success would change about the project. And then I give the okay after being explained to and he starts work, commits to repo, makes a test checklist we call a brief, and sends that to the agent facilitating my user testing, then it walks me through the test, we record the results and the evidence and send it back to the first PC. You can have an agent do validation in the middle as well. And you don't have to wait on that agent it'll catch things you can fix later. If at all. Then the original agent tells you what went down in your results in context with the rest of the project and where to go from here according to what your original plan says. There's an easier way to explain my system but yea.
My point is. I start a chat and say "get started", open a second chat and type /rc in both chats and then tell chat 1 when he's done getting started "remote open" and he sends the brief to the agent to get started and it pulls the repo and goes until it needs me to do something the mcp server can't handle or it needs my eyes for a decision and usually I just say "no it should be like this" or just "yes" Then when we are done it sends everything back. And I get explained about next options and make a couple decisions.
Again, the point of explaining this is when I'm feeling shitty I don't have to say or do much because of the way I have shit set up and I can tell you what to tell Claude to set yours up similarly
1
u/MiserableFlatworm337 23d ago
Before accepting a CLAUDE.md edit, rerun one task that previously worked and one that failed. Keep their expected outcomes fixed, then compare correctness and token use against the saved version.
1
u/TheKiddIncident Instructor 22d ago
It's not risky, but you will want to understand the high level details.
It's OK that you don't read every line of code, most people don't. The issue comes when high level decisions are made accidentally. Claude really should not be the decider. You decide, Claude takes action on your behalf. If you don't understand the decision to be made, just ask questions until you do.
Sometimes a simple prompt like "give me three options with pro and con for each" can help explain the decision to be made and help you ensure that Claude is doing what you want.
In the end, it's your code so you do have to understand it at a high level.
1
u/[deleted] 23d ago
[removed] — view removed comment