Open Org Workspace
Docs/Open Org AI/Writing & formatting rules

Writing & formatting rules

Paste these into Writing & formatting rules in the AI Personality sidebar (chat) or Account Settings. They apply to every reply and to documents and decks the AI creates or updates — not just chat tone.

Pick one example as a starting point, edit for your org, then save. After saving, ask the AI to apply your rules to an existing deck if you need a refresh (e.g. "Update the active deck to match my saved formatting rules").

Essentials (start here)

Short rules that improve every reply and document. Good default if you are not sure what to add.

474 characters · under 2,000 limit

WRITING
- Sentence case for all headings, slide titles, and doc titles (capitalize only the first word and proper nouns).
- Be direct: short sentences, active voice, plain English. No filler ("leverage", "synergy", "circle back").
- Never use em dashes. Use a comma, period, colon, or hyphen instead.
- Use exact numbers from uploaded files. Never invent metrics.

DECKS & DOCS
- These rules apply to chat and to any Word doc, deck, or spreadsheet the AI creates or updates.

Townhall & all-hands decks

Structure, density, and speaker notes for executive-facing slide decks.

824 characters · under 2,000 limit

DECKS (pptx)
- Default layout: titleAndContent. Use twoColumn only for compare/contrast — always with :::left and :::right.
- Max 5 bullets per content slide; one main idea or one key stat per slide. Split long lists across slides; use " (cont.)" in the title.
- dataSlide tables: max 10 data rows per slide; repeat the header row on continuation slides.
- Structure: title slide → executive summary (3 bullets) → sectionHeader between topics → close with "What we're doing next".
- On-slide text = headlines only. Put detail, context, and talking points in :::notes.
- Slide titles: sentence case, no full stops.

TOWNHALL NARRATIVE
- Lead with wins and strong scores, then gaps, then actions. Name the audience (all-hands, not board pack).
- Use real figures from source files; label benchmarks or prior period when shown.

Policies & Word documents

For handbooks, frameworks, manager guides, and long-form HR content.

497 characters · under 2,000 limit

DOCUMENTS (docx)
- Use # for document title, ## for major sections, ### for subsections.
- One idea per paragraph. Prefer bullets for lists of obligations, steps, or criteria.
- Callouts: start a line with **Important:** or **Note:** for must-read guidance.
- UK English spelling unless I specify US.
- Include an opening "At a glance" section with 3–5 bullets before detailed content.

TONE
- Professional but human. Suitable for managers and employees, not legal boilerplate unless I ask for it.

Startup brand + theme

Combines org voice with deck colours and fonts for consistent artefacts.

489 characters · under 2,000 limit

VOICE
- Startup tone: bold, clear, slightly informal. No corporate jargon or passive voice.
- Write like a smart people lead briefing the company, not a consultant deck.

DECKS
- Theme when creating or updating: primary #1E2C51, accent #5B6CF5, background #FFFFFF, fonts Segoe UI.
- Max 5 bullets per slide; more slides beats dense slides.
- sectionHeader between major topics. Speaker notes in :::notes only.

WRITING
- Sentence case titles. No em dashes. Exact metrics from uploads only.

Full stack (chat + decks + docs + data)

Everything in one block — best if you use the AI heavily across deliverable types.

883 characters · under 2,000 limit

WRITING
- Sentence case for all titles and headings.
- Direct, plain English. No em dashes. Exact figures from files only — never invent data.

DECKS (pptx)
- titleAndContent default; twoColumn with :::left / :::right for comparisons.
- ≤5 bullets per slide; one stat or claim per slide when presenting results.
- Tables ≤10 rows per slide; continue on next slide with repeated header.
- Flow: title → 3-bullet summary → sections (sectionHeader) → actions slide.
- Detail in :::notes; slides stay scannable.

DOCUMENTS (docx)
- ## sections, bullets for lists, **Important:** / **Note:** callouts.
- Open with "At a glance" (3–5 bullets) on long docs.

SPREADSHEETS / DATA
- When summarising data in chat, show the headline number first, then breakdown.
- Chart titles in sentence case; label axes clearly.

These rules apply to chat and to all create_artifact / update_artifact work.
Tip: Shorter rules are followed more reliably. Combine sections only if you regularly need all of them — otherwise start with Essentials and add a deck or doc block when needed.

Need more help?

Can't find what you're looking for? Chat directly with the founders.