Claude Team Projects Setup

Claude Team Projects are the centralized knowledge store for client-specific context at Asymmetric. Each project holds a client profile, writing guidance, and past work — so anyone drafting content starts from a consistent, accurate foundation rather than relying on general AI knowledge that may hallucinate facts or miss brand rules.

This setup is a core part of the ^[1].

Why Team Projects (Not Personal Projects)

Claude has two project scopes: personal and team. Personal projects are only visible to the creator. Always work in the Team scope so that all content contributors share the same context.

To confirm you're in the right place:

1. Log into Claude using your @asymmetric.pro account.
2. Check the bottom-left corner — it should show a building icon, indicating the Team plan is active (not your personal plan).
3. Navigate to Projects → Team in the sidebar.

If you've been building projects under your personal scope, those need to be recreated or migrated under Team.

What Goes in Each Client Project

Every client project should contain two core documents:

1. Client Profile

A factual reference about the business. Covers:
- What the company does and their business model
- Who their primary customers are
- Key competitors
- Any industry-specific facts that are commonly misunderstood or misrepresented

Example: Bluepoint's reverse ATM model — operators don't receive a placement fee; revenue comes from what flows through the machine. This distinction was missed in early blog drafts because it wasn't documented anywhere Claude could access.

2. Writing Guidance

A living document of brand and style rules. Covers:
- Forbidden words or phrases (e.g., for Citrus America: never say "peel oil"; say "squeeze" not "crush")
- Preferred terminology and approved language
- Tone and voice notes
- Any recurring corrections that have come back from the client

When a client flags an error, add the correction to this document immediately. That mistake should never recur.

Setting Up a New Project

1. Go to Projects → Team and click New Project.
2. Name it after the client (e.g., "Citrus America").
3. Open Project Instructions and add a brief summary of what this project is for (e.g., "Blog content for Citrus America. Always review the client profile and writing guidance before drafting.").
4. Upload the Client Profile and Writing Guidance documents using the file attachment area.
5. Optionally upload past approved blog posts as reference examples.

Claude will read all attached files at the start of each new chat in the project. To make sure it has loaded everything, open a new chat and type:

Review all project files and confirm you're ready to assist with content for this client.

Using the Project for Blog Drafts

Once the project is configured, the workflow is:

1. Open the client's Team Project.
2. Start a new chat and paste in the blog brief.
3. Prompt Claude to draft the post using the project files as its guide.
4. Claude's output will be informed by the client profile and writing rules — reducing hallucinations and brand misalignment from the first draft.

For the full end-to-end process including Surfer optimization and final delivery, see ^[1].

Project Memory

After several chats, Claude will begin building Project Memory — a running summary of patterns, preferences, and decisions made within that project. This compounds over time: the more you work inside a project, the more context Claude carries forward automatically.

You can also prompt it explicitly at the start of a session:

Review the project files and summarize any relevant previous chats before we begin.

Current Status by Client

Access & Permissions

• Who needs access: Anyone writing or reviewing blog content (currently Gavin, Karly, Melissa, Avokerie).
• How to get access: Mark sends an invite to your @asymmetric.pro email. Accept the invite, then confirm you're on the Team plan (building icon in the bottom-left).
• Sharing: Projects created under Team are visible to all team members. Projects created under your personal scope are not — double-check before adding documents.

Related

• ^[1]
• ^[2]