Learn how to maintain your Claude workspace. Weekly reviews, /close command, growing your template library, and when to regenerate.
Your workspace isn't a one-time download. It's a collection of files that should grow and change as your work does. New projects, new tools, new team members, new processes. Your workspace should reflect all of it.
Weekly: review your CLAUDE.md for accuracy. Did you add a new tool? Change a process? Update a naming convention? Five minutes catches most drift.
The /close command is designed for end-of-session maintenance. When you finish a work session, run /close. It reviews what you worked on, identifies decisions that should be documented, and suggests updates to your workspace files.
As you work with Claude, you'll develop new patterns. A particular way you like research structured. A format for weekly reports. A process for onboarding customers.
Edit when: you're making small updates. New tools, updated processes, additional skills.
About 5 minutes per week if you run /close at the end of sessions. Monthly reviews take 15-20 minutes.
Yes. Claude can suggest updates, identify stale content, and generate new skills or commands based on your recent work.
Start fresh. Regenerate from The Froject with your current role and tools. Then copy over the custom skills and context that still apply.
Only if you overwrite them. Best practice: regenerate into a new folder and merge what you want to keep.