Company Context Files

AI Business OS

The company context files tell Claude about your organisation. There are six of them in .claude/company/, one for each subject. Claude reads the relevant file before it writes content, communications or documents for you. A proposal therefore sounds like your business and names the right people.

The files belong to you. Engine updates never change them, and they stay out of the engine manifest’s list of files that /update maintains.

The Six Files

File	What it holds
`overview.md`	Your organisation’s name, industry, location and website, a short description, your products and services, pricing notes, competitors and market position
`team.md`	Key contacts with name, role, email and notes, and who approves which kinds of content or decision
`audiences.md`	Your primary audience, with what they need and how you serve them, and any secondary audiences
`voice.md`	Tone, formality, key traits, the English variant, how to treat jargon and acronyms, and what to avoid
`brand.md`	Colours, fonts, logo usage, taglines and signature phrases, and where your branded document templates live
`industry.md`	Industry terms with their meanings, the regulations and compliance requirements that affect your content, and the document types you produce

Each file opens with a setup prompt, the question Claude asks to fill it in. For example, voice.md asks how Claude should write on behalf of your organisation. The prompt stays at the top of the file after you answer, so Claude can ask it again later.

How the Files Are Filled In

/setup works through the six files in the order of the table above. For each one, Claude asks you the setup prompt and writes your answer into the file. If you answer “skip” or “not applicable”, Claude leaves the placeholder text and moves on.

Placeholder text appears in square brackets, such as [ORGANISATION_NAME] or [Description of primary customer or client]. A file that still holds placeholders works, but Claude has less to go on. Some skills say so directly. The documenting-workflows skill, for example, writes generic procedures and asks you for role names when team.md still holds its placeholders.

How Claude Uses Them

The master .claude/CLAUDE.md tells Claude to consult the relevant company file before it creates any content, communication or document. Claude reads a file only when a task needs it, which keeps the conversation short.

Several of the built-in skills name the files they read.

Skill	Files it reads
drafting-documents	`voice.md`, `brand.md`, `audiences.md` and `industry.md`
documenting-workflows	`industry.md` for compliance requirements and `team.md` for role names
meeting-notes	`team.md` and `industry.md`, to identify attendees
client-setup	`overview.md` and `industry.md`
status-report	`overview.md` for the report header and `team.md` for distribution

The content defaults rule, .claude/rules/content-defaults.md, also points Claude to industry.md for consistent terminology. Any skill you add can read the same files. The new skill checklist in .claude/FRAMEWORK.md tells a new skill to refer to voice.md instead of repeating its contents.

Keeping Them Current

Ask Claude to update a file whenever something changes, for example “add our new operations manager to team.md”. You can also edit the files yourself in VS Code, because they are plain markdown.

The English variant appears in two places. voice.md records it for content, and .claude/rules/content-defaults.md records it as a rule that Claude loads in every session. /setup sets both. If you change the variant later, ask Claude to update both files.

Workspaces From Version 1

Versions of AI Business OS before 2.0 kept all this information in a single file, .claude/CLIENT_PROFILE.md. If your workspace still has one, run /migrate-company. It splits the old profile into the six files and asks you about any thin areas. /setup also checks for the old file first and moves its content into the six files when it finds one.