Lesson 2.3 of the Free Claude Cowork Course · 25 minutes
Overview
Here’s where this course goes beyond solo use. When five people each use Cowork alone, you get five styles of output and five sets of habits. A team context folder fixes that: one shared location holding your templates, terminology, standards, and examples of “good” — so everyone’s Cowork starts from the same knowledge. It’s the single highest-leverage team move in this entire course.
What You’ll Do
- Build a team context folder structure from the included starter kit
- Write the top-level context file that describes your team in plain language
- Test it: run the same brief with and without the context folder and compare
The Lesson
Say “start lesson 2.3”. The starter kit gives you the skeleton: a top-level context file, plus subfolders for templates, reference documents, and worked examples. The heart of the lesson is writing the context file — who your team is, what you make, the terms and abbreviations you use, and your formatting standards, all in ordinary prose. Then comes the proof: you run a brief from Module 1 twice, once cold and once with the context folder attached, and see the second output arrive already sounding like your team.
The lesson closes with the maintenance question — who owns this folder and how it stays current — because an unowned context folder quietly rots.
Try It Now
Draft the context file for your real team, even in rough form: five sentences about who you are, your three most-used templates, and ten terms an outsider wouldn’t know. Rough and real beats polished and hypothetical.
What’s Next
← Previous: 2.2 Plugins and Skills
Next: 2.4 Shared Workflows →
New here? Download the full course free on GitHub.
Rolling this out for a whole team? See our live team training.