Every new chat: who you are, what Wix is, what tone — again.
Forty minutes renaming files, reformatting a sheet — work Claude could have taken.
The task needed six steps, you got one, and did it yourself.
Quick things, one exchange, done.
A prepared environment. The real work goes here.
A blank canvas, for codebases.
Think, delegate, build. That's the whole session.
Most of this room is living in the first column. The work belongs in the second.
The mistake: doing real work in Chat because it's the tab already open.
Cowork now runs on web and mobile too, and shares Projects and Artifacts with Chat.
Start a project in Cowork and it creates the project folder for you.
Role, what do you do, who you write for, top priorities, what outcomes are you looking for?
How YOU sound — words you use, words you'd never use, two real writing samples.
Read the files first, ask before executing, output defaults, what never to do.
The always-on layer. Loads every session, in every project.
Today's gift: you don't write these from scratch.
Every type of work gets a folder — the folders are the answer to “what do I actually do all week?”
If you decide not to use Claude Code, it doesn't mean you have a skill gap — you're just choosing the smarter environment for the work you're doing.
Install “Claude for Chrome” from the Chrome Web Store.
Pin it and sign in with your Wix work account.
Open it on a page and grant access per site — only where you want it.
Wix already runs single sign-on, admin audit logs and retention limits. The guardrails exist — you're not the last line of defence.
It was never Claude “learning” your secrets. It's typing a password or a key into any tool that keeps a log — Claude, Slack, a doc, a ticket. Same rule everywhere.
| Tools | When should I use? | Not for | The mistake people make |
|---|---|---|---|
| Claude.ai Chat | Quick things — one exchange, done | Real work: multi-step, real files, recurring | Doing real work here because it's the tab already open |
| Cowork | The real work — outcomes, files, anything recurring | A one-line question | Dumping 200 files in. Five good ones beat fifty messy ones. |
| Claude Code | Working inside a codebase | Anything that isn't code | Assuming it's the “advanced” one you graduate to |
| Chrome | Live pages behind your login | Bulk or repeatable work | Leaving it on where a wrong click costs money |
| Connectors | Pulling from Slack, Drive, Gmail on demand | Live monitoring | Expecting them to watch your tools 24/7 — they fetch when asked |
| Projects | Recurring work that shares context | One-off questions | One mega-project for everything, instead of one per stream of work |
| Artifacts | Something you'll reopen and reuse | A one-time answer | Treating them as demos rather than the deliverable |
Don't start in a blank chat. Enter the Cowork project for that stream of work, or spin up a new one and let it build the folder.
Eight questions. It writes all three context files for you: about-me, voice, style.
Pick the thing you did by hand last week and hand that one to Cowork.
Everything you need for the five moves on slide 5, done for you.
A skill that interviews you. Eight questions, then it writes about-me, personal-voice and working-style for you.
Or the three templates. Same files with the prompts already inside — fill in and save.
Open card →A skill you run once your files exist — it grades what Claude still doesn't know.
What's missing. The gaps in your context files, named line by line.
Evidence, not self-report. With your permission it looks at your real work first — so it catches what the files claim versus what you actually do.
Open card →