Running Setup

/setup is a wizard that personalises a new workspace by asking about your organisation one question at a time. It writes your answers into the files that Claude reads at the start of every session. The wizard says it takes about five minutes, though the company files take longer if you write a lot. You run it once, straight after installing.

Note

If you installed PRIMA Project Management, its own version of /setup replaces this one. It adds a choice of project numbering format, and PRIMA Project Management Setup describes the differences.

Start the Wizard

1. Open your workspace folder in VS Code.
2. Open the Claude Code panel.
3. Type /setup and send it.
4. Answer each question when Claude asks it.

The Questions

Claude asks these questions in order and waits for each answer before the next.

Question	What it is used for
Company name	Written into .claude/CLAUDE.md, the workspace record and the integrations file
Industry	Written into .claude/CLAUDE.md
Workspace ID	Claude builds it from your company name, for example example-consulting-biz-os, and asks you to confirm it
Repository address	The address of your own remote git repository, or none if you do not use one. /sync stops without pushing if the workspace remote does not match this address
Cloud storage	Where you keep large files (Google Drive, OneDrive, Dropbox, iCloud Drive or local only), then the full path to that folder
Language variant	UK English or US English
Calendar	Whether you use Google Calendar, Outlook or Apple Calendar, and the names of the calendars to include in your daily briefing
Your name	The name Claude uses when it addresses you
Project numbering	Claude tells you that projects are numbered P001, P002, P003 and so on. This format is fixed in AI Business OS

The Company Files

Next, Claude works through the six files in .claude/company/, each of which starts with a setup prompt. Claude asks you that prompt and writes your answer into the file.

File	What it holds
overview.md	Your organisation’s name, industry, location, website, description, products and competitors
team.md	Key contacts, their roles and how approvals work
audiences.md	Who you serve, what they need and how you serve them
voice.md	Tone, formality, language preferences and things to avoid
brand.md	Colours, fonts, logo use, taglines and where your templates are
industry.md	Terminology, regulations, compliance and common document types

Claude reads the relevant file before it writes content, messages or documents for you, so the more you put in, the closer the first drafts come to your own style. If a file does not apply to you, say “skip” and Claude leaves it as it is. You can fill it in later by editing the file yourself or by asking Claude to update it. Company Context Files explains each file in more detail.

What Setup Writes

File	What changes
.claude/CLAUDE.md	Company name, industry, workspace ID, repository address, cloud storage path and the date of setup
.claude/company/	The six company files
.claude/config/integrations.json	Company name, setup date, calendar and storage settings, and which features are switched on
.claude/state/state.json	Workspace name, ID, type and repository address, and the calendars for your briefing
.claude/rules/content-defaults.md	Your language variant

Claude Code asks you to approve the calendar tools the first time Claude uses them, and records your approval in .claude/settings.json.

Updates never change .claude/CLAUDE.md, the company files, state.json or integrations.json, because these are your files. Configuration covers the settings in more detail.

The Summary and First Commit

When it finishes, Claude shows a summary of what it configured and which files it changed. It then suggests next steps and asks whether to commit the setup to git. If you say yes, Claude runs /sync to commit the changes and push them to your remote repository.

Running Setup Again

If you run /setup a second time, Claude warns you that it will overwrite your current configuration. It continues only after you confirm, and it keeps every existing project ID as it is.

Caution

A second run rewrites the files listed above with your new answers. Before you start it, commit any edits you made by hand to .claude/CLAUDE.md or the company files with /sync, so that you can recover anything the second run replaces.

Workspaces From Before Version 2.0

Very early workspaces kept company details in a single CLIENT_PROFILE.md file. If /setup finds that file, it moves the content into the six company files instead of asking the questions. It archives the old file to .claude/engine-backups/company-migration/ and then offers to continue with the rest of the setup. /migrate-company does the same conversion with a walkthrough for any thin areas.

Next Step

Run /day next for your first daily briefing, and follow Your First Day as you go.