I’ve been using Claude Code daily for months now (I’m a senior full-stack dev). Here’s the workflow that’s made me genuinely productive after a lot of trial and error. The basics that changed how I work: Use “plan” mode for anything complex. Before Claude writes a single line, I let it lay out its approach. This saves me a lot of back-and-forth. Only ask for the first step. If you say “implement the whole feature”, it will go off the rails. That’s why I usually just ask for step one and review it before asking for step two. Tedious but worth it. Use the preview. Sounds obvious but a lot of people skip it. Don’t fix bugs yourself, let Claude fix them. I know it’s tempting to just patch it quickly, but if you fix it yourself, Claude doesn’t learn the context. I let Claude correct its own mistakes so it builds a better mental model of my codebase. Run /simplify before doing a review. Claude tends to over-engineer. That’s why I let it clean up first. Do a retro at the end of each session. I regularly ask Claude “what did you learn during this session?” and save the output. It’s a great way to build up institutional knowledge. What are your Claude Code workflows? submitted by /u/Marmelab
Originally posted by u/Marmelab on r/ClaudeCode
You must log in or # to comment.