AI PROJECT · CURRENTLY WORKING ON

Claude Setup Wizard — Per-Person CLAUDE.md & Folder Builder

A guided wizard that interviews a teammate for eight minutes and hands back their own Claude folder — CLAUDE.md, instruction files, glossary, and a projects-and-skills plan built for their MM team.

⏱ Est. 10 hours (Claude estimate — the draft below is working; the rest is team testing and iterations) Company-widePriority: HIGHUpdated August 9, 2026

What & why

Everyone on the team is starting from the same cold start: Claude does not know they work at a jewelry company in Los Angeles, that wholesale lives in NuORDER, or that nobody here wants to read the phrase 'effortlessly chic'. Today the fix is that each person re-explains it, badly, in every new chat — or does not, and gets generic answers they quietly stop trusting. This wizard writes it down once. Pick your MM team and it pre-loads the right connectors, the guardrails that matter for that job, starter projects, skill candidates and glossary terms; answer seven more short screens and it produces a folder of about twenty-one plain-English markdown files you drop on your machine and connect in Cowork. The design goal is not completeness, it is restraint: CLAUDE.md is read on every task so it is held to one page, and everything else is a side file Claude opens only when the job calls for it.

The plan — step by step

✅ DONE — v1: the file bundle and folder structure (CLAUDE.md, instructions, reference, projects, skills, prompts) with a live preview and one-click zip
✅ DONE — v2: ten MM role presets (Marketing, E-comm, CS, Wholesale, Ops, Design, Finance, Creator, Tools, Leadership) pre-filling connectors, guardrails, projects, skills and glossary terms; jewelry glossary; MM sources-of-truth table; brand voice and never-write-like-this files
✅ DONE — v3: rebuilt as a guided one-question-at-a-time flow with an explainer up front, animated transitions, auto-advance, keyboard navigation, a collapsible preview drawer and a one-question express path
NOW — team testing (4h): five people from different teams run it end to end; watch where they hesitate, and treat every wrong default as a bug in the wizard
NEXT — fill the blanks that only we can fill (2h): the sources-of-truth rows left deliberately empty (stock counts, product naming, creator earnings) need a decision from the people who own those numbers, not a guess from the wizard
NEXT — shared vs personal split (2h): move the four company-level files (safety, brand voice, never-write-like-this, glossary, sources of truth) into one Drive or Box folder everyone pulls from, so house rules stop drifting per person
LATER — make it a skill (2h): wrap the same interview as /mm-onboard-claude so a teammate can run it inside Claude instead of on a web page, and so it can update an existing folder rather than only creating a new one

Reasoning & trade-offs

The wizard deliberately disagrees with the loudest current advice. Ruben Hassid's July Cowork guide reverses his own earlier position and says drop connected folders entirely in favour of Skills and Projects. His complaint is real — stale outputs sitting in a connected folder get read as current — but the cause is outputs, not instructions. So this bundle has no outputs folder, no archive and no working folder, and says so out loud, while keeping the one-page always-read file his own token maths argues for.

Creative mode is in there for the opposite reason. Every other file makes Claude more consistent, and consistency is exactly wrong for a launch concept — loaded with enough context about how we usually do things, Claude reliably produces what we usually do. Saying 'creative mode' drops the glossary, the brand voice and the tone rules until you say you are done. A switch instead of a compromise.

Session hygiene is written as instructions rather than a lecture: fresh chat every twenty to thirty turns, edit the prompt instead of replying that it is wrong, turn connectors off when a task does not need them. Claude re-reads the whole conversation on every turn, so this is the difference between sharp and expensive.

It also carries the Skills-versus-Projects test, because getting that wrong at team scale is how you end up with fifty skills that should have been three projects and nobody able to find anything.

Built as a self-contained HTML page on purpose: no build step, no dependencies to maintain, and a teammate can be handed the file directly if they never reach this site.

Ten hours is a rolling estimate. The draft works today; what is left is the part that only happens with real people in front of it.

Related material

Open the wizard full screen · Hub — connect Claude to everything · Hub — Brand Knowledge (the voice the wizard writes into brand-voice.md) · Related — Team Enrollment Push

Try the draft — it works right now

Working draft · v2 Open full screen ↗

This is the live wizard, embedded. Answer the questions and it builds your folder in front of you — nothing is uploaded anywhere and nothing is saved until you press download. Give it eight minutes, or hit I am in a hurry and answer one question.

Feedback goes to David or #mm-claude. Every answer you disagree with is a bug in the wizard, not in you.

What it hands you

A folder of about twenty-one plain-English markdown files, sized so Claude reads the right one at the right time. The tree below is what a Wholesale & Sales teammate gets.

claude-mm/ ├─ instructions/ │ ├─ brand-voice.md │ ├─ creative-mode.md │ ├─ how-to-talk-to-me.md │ ├─ never-write-like-this.md │ ├─ safety-and-approvals.md │ ├─ session-hygiene.md │ └─ tools-and-connectors.md ├─ projects/ │ ├─ _TEMPLATE/CLAUDE.md │ ├─ key-accounts/CLAUDE.md │ └─ market-prep/CLAUDE.md ├─ reference/ │ ├─ glossary.md │ └─ sources-of-truth.md ├─ prompts/starter-prompts.md ├─ skills/README.md ├─ CLAUDE.md ├─ README-START-HERE.md ├─ SETUP-CHECKLIST.md └─ TEAM-ROLLOUT.md (finished work lives OUTSIDE this folder)

CLAUDE.mdRead at the start of every session, so it is held to about one page. Everything else is a pointer.

sources-of-truth.mdWhich MM system wins when two disagree — Shopify vs NuORDER vs ApparelMagic vs ShipHero. The contested rows are left blank on purpose.

glossary.mdAlready knows vermeil is not gold-filled is not plated, plus the words your team uses.

never-write-like-this.mdBanned words, AI tells, and jewelry filler. Plus the copy you paste in that you have actually rejected.

creative-mode.mdThe escape hatch. Say creative mode and Claude drops the rules that would otherwise make it produce what we always produce.

TEAM-ROLLOUT.mdWhich four files are company-level and get shared, and which stay personal to each person.

The one rule the folder is built around: finished work never goes inside it. There is deliberately no outputs folder, no archive, no working folder. Deliverables go to Drive. A connected folder full of old drafts is the fastest way to get a confident, current-sounding answer built on last quarter's numbers.

← Back to all projects