How to Set Up Claude Cowork for Repeatable Work

TL;DR

Claude Cowork becomes more useful when you give it a central folder containing your working files, a CLAUDE.md file with standing instructions, and task-specific skills for repeated workflows. It can read and create files directly in that folder, follow your preferences automatically, navigate a documented folder structure, and save outputs where you specify.

Transcript

Claude Co-work is undoubtedly an incredibly powerful tool, but the first time that I opened it up, I really didn't understand how it was different from using regular Claude chat. And the power of Co-work didn't really click for me until I learned the three things I'm about to show you in this video. So first, I will show you the uniquely powerful f... Read More

Key Insights

• Claude Cowork can access files and folders directly on a computer when the user grants it access to a selected folder. Regular Claude chat instead requires the relevant files to be attached to the conversation before Claude can analyze them.
• Claude Cowork can create files directly inside the local folder where the user is already working. Those files can then be edited manually or revised through Cowork without repeatedly downloading, relocating, and uploading them for each new task.
• A central Cowork hub is a folder that contains the files, subfolders, instructions, and outputs used across tasks. Placing it inside iCloud Drive is presented as one option for keeping the folder backed up while making it consistently available to Cowork.
• The exam-analysis workflow shows that Cowork can inspect multiple graded exams, calculate the average and median grades, identify subjects or question types that students consistently missed, and produce an HTML report from a single prompt in a few minutes.
• A CLAUDE.md file is a plain-text instruction manual that Cowork reads automatically when it begins a task in the associated folder. It can define who the user is, how Claude should behave, how the folder is organized, and where outputs belong.
• Human oversight is an explicit part of the recommended instruction system. The teacher example tells Cowork that grading suggestions are not final grades, while additional rules prohibit file deletion and require permission before Cowork makes significant changes.
• Skills are task-specific instructions for workflows that the user performs repeatedly. Unlike CLAUDE.md, which contains information Cowork should always know, a skill provides the step-by-step process for a particular task and is loaded only when that workflow is needed.
• Persistent folder instructions reduce repetitive prompting because operational details live in CLAUDE.md instead of each request. A short prompt such as "Analyze the new exams" can work when the file already specifies where to look, what to create, how to format it, and where to save it.

Questions & Answers

Q: How is Claude Cowork different from regular Claude chat?

Claude Cowork can access files and folders directly on a computer after the user selects and authorizes a folder. It can also create and revise files inside that local workspace. Regular Claude chat requires users to attach source files, then download generated files and move them to the desired location. Cowork therefore operates where the files already reside.

Q: How do you create a central workspace for Claude Cowork?

Open the Claude desktop app, switch from chat to Cowork, and use the folder selector in the prompt area. Choose where the workspace should live, create a new folder, name it, and open it. The example uses a folder called Cowork OS inside iCloud Drive, then selects "always allow" so Cowork can access it whenever it is chosen.

Q: What should a CLAUDE.md file contain for Claude Cowork?

A CLAUDE.md file can describe the user, the work being performed, the behavior expected from Cowork, and the organization of the workspace. It can also specify output formats and destinations, identify available task-specific skills, and establish safety rules such as never deleting files, requesting approval before major changes, and keeping summaries short.

Q: Why is CLAUDE.md important in Claude Cowork?

CLAUDE.md provides standing instructions that Cowork reads automatically whenever it starts a task in the folder. Without that system, each new task begins fresh and the user must repeatedly explain their identity, preferences, workflows, and desired outputs. With the file in place, those instructions remain transparent, editable, and available across tasks performed in the workspace.

Q: What is the difference between CLAUDE.md and a skill?

CLAUDE.md contains information and rules that Cowork should know for every task in a folder, including user context, behavior preferences, folder organization, and safety requirements. A skill contains detailed instructions for one repeated workflow, such as analyzing exams or drafting a parent update email. Cowork loads the relevant skill only when that particular task is requested.

Q: How can Claude Cowork analyze a folder of graded exams?

Place the graded exams in a subfolder inside the authorized Cowork workspace, then ask Cowork to inspect them. The example prompt requests the average grade, median grade, recurring subject or question difficulties, and an HTML report. Cowork analyzes the files without individual uploads and saves the resulting report inside the local workspace for later use.

Q: How does a folder structure help Claude Cowork complete tasks?

A documented folder structure tells Cowork what each subfolder contains and where it should search for inputs or place outputs. This guidance becomes increasingly useful as the workspace grows. In the example, CLAUDE.md maps the available subfolders and instructs Cowork to save generated outputs in a reports folder as HTML files, making future tasks easier to navigate.

Q: How can users keep control while automating work with Claude Cowork?

Users can place explicit boundaries in CLAUDE.md and remain responsible for consequential decisions. The teacher example states that grading output is only a suggestion and that the teacher assigns the final grade. Other rules tell Cowork never to delete files and to ask before making major changes. These instructions position Cowork as a helpful colleague rather than an autonomous replacement.

Summary & Key Takeaways

• Claude Cowork differs from regular Claude chat because it can access files and folders directly on a computer. It can also create or revise local files in the selected folder, removing the need to upload every source file, download each result, and manually move outputs into the correct working location.

• A central Cowork hub can hold source materials, reports, standing instructions, and task-specific workflows. In the teacher example, Cowork examines graded exams, calculates the average and median grades, identifies recurring areas of difficulty, and creates a visual HTML report that remains available inside the designated local folder.

• A CLAUDE.md file gives Cowork persistent instructions for every task performed within its folder. It can describe the user, preferred communication style, folder structure, output rules, safety boundaries, and available skills. This setup reduces repetitive prompting while keeping instructions readable, editable, and controlled by the user.