Best practices for working with Corey

Corey works from a folder on your computer. Everything it creates lives in that folder as plain files you can read, edit, or move at any time. Your business profile, running projects, task logs, and the knowledge Corey builds up over time all live there.

This matters for two reasons:

• Context travels with you. Because Corey’s memory is files in your folder, the same context is available every time you open a new chat in your Claude Project. You do not have to re-explain your business each time.
• You own the output. There is nothing locked inside a platform. If you want to review, export, or change anything Corey has created, you open the file.

When you set up a Claude Project, you point it at your Corey folder. That folder becomes the persistent workspace. Keep it in one place and let Corey maintain it.

Corey creates and maintains several types of files:

• Business profile - your goals, audience, tone of voice, and key context
• Project files - plans, drafts, and notes for each active project
• Task logs - a record of what Corey has done and when
• Knowledge files - anything Corey has learned about your business that will be useful later

You can add your own files too. Drop in a brief, a spreadsheet, a list of customer quotes, or a competitor’s pricing page. Corey will use what is there.

Start a fresh chat for each distinct piece of work. If you are writing a homepage and then asking Corey to prepare an invoice, those should be two separate conversations.

Long chats accumulate context from different tasks. That unrelated context competes for attention and the quality of outputs drops. A focused chat on a single task produces sharper work.

A good rule: if you find yourself saying “ignore what we talked about earlier”, start a new chat.

The more Corey knows about what you are doing and why, the better the work it produces. When you start a task, tell it:

• What the output is for (who will read it, where it will be used)
• Any relevant background (your pricing, your tone, your past decisions on this topic)
• What good looks like for you (examples help)
• Any constraints (word count, format, things to avoid)

You do not have to repeat your business profile each time - that is what the folder is for. But the task-specific details help Corey calibrate.

When you first set up Corey, run onboard. This builds your business profile from a short conversation. The more thorough you are in that session, the better positioned Corey is from day one.

As your business evolves, keep Corey updated. Tell it about new products, new customers, pricing changes, or anything else that shapes the work it does for you.

Corey proposes; you approve. This is not a limitation - it is the point. You keep the judgement calls; Corey handles the effort between you and them.

Before Corey acts on anything in these categories, it will pause and confirm:

• Anything public - copy for customers, social posts, emails, web pages
• Anything involving money - invoices, payments, contracts, financial commitments
• Anything irreversible - deletes, sends, submissions

Everything else - drafting, researching, planning, organising - Corey can do without stopping to ask.

How to review well:

• Read the full output before approving, not just the headline
• Check that the tone matches your voice before anything goes to customers
• Verify any figures or facts before they go on an invoice or proposal
• If something is almost right, give Corey a specific note and ask it to revise - “tighten the second paragraph” beats “rewrite this”

A quick review before publication saves a longer conversation afterwards.

A Claude Project is a container that remembers your folder and instructions across every chat. Using one means you do not have to re-point Cowork at your folder or re-add the Corey connector each time.

Set up a dedicated project for Corey work:

1. In Claude Desktop’s left sidebar, click +, choose Use an existing folder, and pick your Corey folder.
2. Add instructions to the project:

Use the Corey connector for everything in this project.
British English, £, DD/MM/YYYY, no em dashes.

Within your project, you can use Claude’s built-in conversation management to keep topics separate - one thread for marketing tasks, another for finance, and so on. Corey’s context from your folder is available in all of them.

When you start a project that will run over days or weeks - a product launch, a website, a campaign - ask Corey to open a project file in your folder for it. Corey keeps a running plan and notes there, so any chat in the project can pick up where the last one left off without you having to recap.