Claude tips
10 September 2026 (Updated 17 September 2026)
- Work in small iterations instead of trying to one-shot things. For example, ask Claude to implement a create record form without actually handling the submission. Once it’s done that, review the code and make changes if necessary. If all is good, ask it to create the submission logic. Keep working in small steps.
- Treat Claude as a senior colleague who you’re pair-programming with. Talk to it like a human. Don’t feel like you always have to tell it what to do. Ask it for its opinion on how to do things when you’re unsure.
- You can redirect Claude at any point without waiting for it to finish its current action by pressing
Esc. - Use
/rewindto go back to an earlier point in your conversation. - Use
/doctorto get Claude to check your Claude setup and suggest improvements (e.g., suggest how you can trim yourCLAUDE.mdfile).
TODO
- Add a /commit skill that writes a descriptive commit of the current changes. Ask Claude to create the skill
Tagged:
Claude Code