Build a repeatable workspace for recurring project work
They used Claude Cowork to separate instructions, notes, and logs so the same non-coding process could be reused across projects.
- What they did
- The poster described a setup in Claude Cowork that already included Context, Projects, Outputs, and Templates, with guidance split between account-wide, Cowork-wide, and project-level settings. In the discussion, experienced users recommended keeping general preferences in the broadest settings, putting the main operating rules in an HQ-level CLAUDE.md, adding extra CLAUDE.md files only where a project or workstation needs them, and using MEMORY.md or local folders for conversation history, current status, and working files. One commenter added that beginners can start with Cowork’s built-in instruction areas and move to files later.
- How it went
- The thread frames this as a workable way to run repeated non-coding jobs while keeping each area of work separated. No metrics were shared, and the main drawback raised was that the system can get confusing if it grows into too many folders, files, and layers of rules.
- Tips
- Start with the smallest setup that covers your needs, then add layers only when a project truly requires them. Another user keeps a separate backup folder for artifacts, schedules, and skills so the system can be reused or transferred later.
Try it yourself with Claude Cowork
Help me design a reusable setup for [type of non-coding project] that I can use again across multiple jobs. Recommend a folder structure, one main instruction file, optional project-specific instruction files, a place for notes and status updates, and a run log that records what changed each time. Before you delete, overwrite, submit, or send anything, pause and ask for my approval. Then explain how I should launch the next project from this setup and how to keep everything organized.
Fill in the [brackets]. Agents can make mistakes, so review anything before it is sent, paid or deleted.
Get 3 agent uses like this every morning
With the day's top AI news. Free, and one click to unsubscribe.
Related agent uses
Use Claude Cowork to grade papers and plan lessons
A teacher used Claude Cowork to speed up lesson planning, marking, slide creation, and grade analysis across several classes.
Check a task by comparing it with another Claude chat
Claude Cowork can verify work from a separate Claude conversation before you hand it off.
Reconcile statements and invoices with Claude Cowork
They used Claude Cowork to line up bank transactions with invoices and export the results into Excel.
Sort PDF batches into folders by their text
They used Claude Cowork to read hundreds of PDFs in one folder and move them into subfolders based on text matches.
Hand off a stack of routine tasks to Cowork
An architect used Claude Cowork to clean up files, draft a recurring metrics report, and turn rough notes into a structured document.
Use Cowork to tidy folders and turn notes into docs
A commenter gives Claude Cowork folder access so it can reorganize files, draft documents from notes, and move screenshot details into a spreadsheet.