uk-business-english

$npx mdskill add jezweb/claude-skills/uk-business-english

Apply polished British business English to professional communications.

  • Ensures EN-GB spelling, tone, and style in business writing.
  • Relies on built-in language rules and style guidelines.
  • Selects British spelling and phrasing based on context and audience.
  • Outputs revised text with British conventions applied directly.

SKILL.md

.github/skills/uk-business-englishView on GitHub ↗
---
name: uk-business-english
description: "British business English writing style for professional communications — polished, understated, EN-GB spelling (colour, organise, centre). Use whenever the user is writing for a British audience: emails, chat messages, proposals, client communications, blog posts, web copy, or any business writing. Apply to drafting, editing, and tone-checking professional text."
---

# UK Business English

Professional and measured. Polite without being obsequious. Direct without being abrupt. Naturally British without being a caricature. Write like a competent professional who happens to be British -- not like a Dickens character, not like an American tech startup, and not like someone who just discovered the word "whilst".

## Spelling (EN-GB)

| Pattern | British | Not |
|---------|---------|-----|
| -our | colour, favour, honour, behaviour | color, favor |
| -ise | organise, realise, specialise, recognise | organize, realize |
| -re | centre, fibre, metre, theatre | center, fiber |
| -ence | licence (noun), defence, offence | license (noun), defense |
| -ise/-ize | Both accepted in GB; prefer -ise for consistency | — |
| Double L | travelling, cancelling, modelling | traveling, canceling |
| -ogue | catalogue, dialogue, analogue | catalog, dialog |
| -ement | judgement, acknowledgement | judgment (legal only) |

**Noun/verb splits:**

| Noun | Verb |
|------|------|
| licence | license |
| practice | practise |
| advice | advise |

**Common traps:** enquiry (general), inquiry (formal/legal), kerb (road edge), tyre (wheel), programme (general), program (computing), cheque (payment), grey (not gray).

**Date format:** Day Month Year, no comma -- 15 January 2026. Abbreviated: 15 Jan 2026. Never Month/Day/Year.

## Tone Ladder

Match formality to context. Default to "polite professional" -- a step more formal than Australian or American baseline, but still warm.

| Context | Formality | Greeting | Sign-off |
|---------|-----------|----------|----------|
| Slack/Teams (internal) | Casual | "Hi" / first name | None needed |
| Email to existing client | Polite professional | "Hi [Name]" | "Kind regards" / "Thanks" |
| Email to new client | Professional | "Dear [Name]" / "Hi [Name]" | "Kind regards" |
| Proposal or quote | Professional | "Dear [Name]" | "Kind regards" / "Yours sincerely" |
| Follow-up after meeting | Polite professional | "Hi [Name]" | "Kind regards" / "Thanks" |
| Cold outreach | Professional | "Dear [Name]" / "Hi [Name]" | "Kind regards" |
| Formal letter or legal | Formal | "Dear [Name]" / "Dear Sir or Madam" | "Yours sincerely" / "Yours faithfully" |

**Rule:** "Yours sincerely" when you know their name. "Yours faithfully" when you don't (Dear Sir or Madam). Getting this wrong marks you as careless.

**Never use:** "Hey" in first contact, "To Whom It May Concern" (use "Dear Sir or Madam"), "Warmest regards", "Respectfully yours".

## Sign-off Ranking

From most to least common in UK SME context:

1. **Kind regards** -- default, works almost everywhere
2. **Thanks** / **Many thanks** -- when appreciating effort or asking for something
3. **Best wishes** -- warm, slightly less formal than Kind regards
4. **Regards** -- neutral, slightly cooler
5. **Yours sincerely** -- formal letters, proposals to new clients

**Avoid:** "Best" on its own (reads as American), "Cheers" in first contact (fine once rapport is established), "Warm regards" (overdone), "Ta" (too informal for anything written).

## Avoid List

### Americanisms

Replace these reflexively:

| Instead of | Write |
|-----------|-------|
| "reach out" | "get in touch" / "contact" |
| "touch base" | "catch up" / "check in" |
| "circle back" | "come back to" / "follow up" |
| "leverage" (verb) | "use" / "make the most of" |
| "moving forward" | "going forward" / "from here" (or drop it) |
| "actionable insights" | "useful findings" / "what we found" |
| "deep dive" | "closer look" / "detailed review" |
| "bandwidth" (for time) | "time" / "capacity" |
| "gotten" | "got" |
| "could care less" | "couldn't care less" |
| "loop in" | "include" / "copy in" |
| "deliverables" | "what we'll provide" / "the work" |
| "Monday through Friday" | "Monday to Friday" |
| "on the team" | "in the team" |

### Forced Britishisms

Avoid in written professional comms:

- **"Cheerio", "pip pip", "tally-ho"** -- never in professional writing
- **"Bloody", "blimey", "crikey"** -- spoken register only, and even then sparingly
- **Overuse of "rather" and "quite"** -- one per email is plenty
- **"I dare say"** -- sounds like a period drama
- **"Awfully good"** -- ironic understatement has limits in business writing
- **"Old chap", "old boy"** -- not this century

## Writing Principles

1. **Lead with the point.** First sentence answers the question or states the purpose. Context comes after, not before. British politeness doesn't mean burying the lead.

2. **Short paragraphs.** Two to three sentences max. One idea per paragraph. White space is your friend.

3. **Measured contractions.** "We've", "I'll", "that's" are fine in emails. Use fewer in proposals and formal letters. The goal is human, not robotic -- but the baseline is slightly more formal than American or Australian English.

4. **Active voice.** "We'll send the report on Monday" not "The report will be dispatched on Monday."

5. **Specific over vague.** "I'll have this to you by Thursday" not "I'll revert at my earliest convenience."

6. **One ask per email.** Multiple requests? Number them. Don't bury the second ask in paragraph four.

7. **Understate rather than overstate.** "That's quite a good result" lands better than "That's an absolutely incredible, game-changing result!" Restraint signals confidence.

## Examples

### Status update to existing client

**Too corporate:**
> Dear Mr Thompson, I write to apprise you of the current status of your website redesign project. Please find herewith a summary of deliverables completed to date and the projected timeline for the remaining programme of work.

**Right tone:**
> Hi David,
>
> Quick update on the website -- we've finished the homepage and the three main service pages. Coming together nicely.
>
> Next up is the contact form and booking system, which we'll have ready by the end of next week. I'll send through a preview link once it's on the staging site.
>
> Kind regards,
> [Your name]

### Delivering a quote

**Too stiff:**
> Dear Client, Please find enclosed our formal quotation for the proposed scope of works as discussed. We trust this meets with your approval and look forward to receiving your favourable response at your earliest convenience.

**Right tone:**
> Hi Sarah,
>
> Thanks for the call yesterday -- good to get a clear picture of what you need.
>
> I've put together a quote based on what we discussed. In short: GBP 3,500 for the full site, including the booking system. That covers design, development, and getting it live on your domain.
>
> Happy to arrange a call if you have any questions.
>
> Kind regards,
> [Your name]

### Saying no to a request

**Too blunt:**
> We can't do that.

**Too soft:**
> Whilst we greatly appreciate your most kind enquiry and would very much welcome the opportunity to explore this avenue further, regrettably it would not be possible for us to accommodate this particular request at the present time.

**Right tone:**
> Hi Mark,
>
> Thanks for thinking of us for this. Unfortunately it's not something we're able to take on at the moment -- we're fully committed through March.
>
> If timing works, we'd be happy to look at it in April. Otherwise, I can suggest a couple of firms who might be able to help sooner.
>
> Kind regards,
> [Your name]

## Context Rules

**Corporate clients:** Match their formality but keep your clarity. "Dear [Name]" and "Yours sincerely" if they use it. Never mirror their jargon -- if they say "key learnings going forward", you say "what we've found".

**Delivering bad news:** Be direct but considerate. State the issue, explain briefly, offer the path forward. British politeness means framing matters, but don't wrap bad news in so many qualifiers that the message gets lost. One "apologies" is sufficient.

**Quoting prices:** Clear and confident. "The cost for this is GBP X" not "We would wish to propose a fee of GBP X for your kind consideration." Include what's covered. State VAT position (inclusive/exclusive) explicitly.

**Saying no:** Polite and brief. "Unfortunately" does the work -- you don't need three sentences of preamble. Give the reason, offer an alternative if possible.

**Following up:** Purposeful but not pushy. "Just checking in on this" works. "I trust this finds you well" is filler -- drop it. "Wanted to bring this back to the top of your inbox" is fine.

More from jezweb/claude-skills

SkillDescription
ai-image-generatorGenerate AI images using Gemini or GPT APIs directly. Covers model selection (Gemini for scenes; GPT Image 2 for text rendering, batch variations, multi-reference compositing; GPT Image 1.5 for transparent icons), the 5-part prompting framework, API calling patterns, multi-turn editing, and quality assurance. Produces photorealistic scenes, icons, illustrations, OG images, posters, infographics, and product shots. Use when building websites that need images, creating marketing assets, or generating visual content. Triggers: 'generate image', 'ai image', 'create hero image', 'make an icon', 'generate illustration', 'create og image', 'poster', 'infographic', 'image variations', 'gpt-image-2', 'ai art', 'image generation'.
app-docsGenerate complete user documentation for a web app with screenshots. Browses the app via browser automation, screenshots every screen, and produces a structured user guide with step-by-step instructions, annotated screenshots, workflow diagrams, and reference tables. Supports quick (key screens), standard (all pages), thorough (every state and flow), and exhaustive (publishable documentation suite). Triggers: 'document the app', 'user guide', 'app documentation', 'screenshot docs', 'generate user docs', 'help docs', 'how-to guide', 'write the docs'.
aussie-business-englishAustralian business English for professional writing — warm, direct, EN-AU spelling (colour, organise, centre), no filler words. Use whenever the user is writing for an Australian audience: emails, chat messages, proposals, client communications, blog posts, web copy, or any business writing. Apply to drafting, editing, and tone-checking professional text.
award-applicationWrite compelling award submissions, grant applications, and competition entries. Maps achievements to selection criteria using evidence-based narratives. Use whenever the user is applying for a business award (Telstra, chamber of commerce, industry awards), a grant, a competition, or any submission demonstrating merit against defined criteria.
cloudflare-apiHit the Cloudflare REST API directly for operations that wrangler and MCP can't handle well. Bulk DNS, custom hostnames, email routing, cache purge, WAF rules, redirect rules, zone settings, Worker routes, D1 cross-database queries, R2 bulk operations, KV bulk read/write, Vectorize queries, Queues, and fleet-wide resource audits. Produces curl commands or scripts. Triggers: 'cloudflare api', 'bulk dns', 'custom hostname', 'email routing', 'cache purge', 'waf rule', 'd1 query', 'r2 bucket', 'kv bulk', 'vectorize query', 'audit resources', 'fleet operation'.
cloudflare-worker-builderScaffold and deploy Cloudflare Workers with Hono routing, Vite plugin, and Static Assets. Describe project, scaffold structure, configure bindings, deploy. Use whenever the user wants to create a Worker project, set up Hono on Cloudflare, configure D1 / R2 / KV / Queues bindings, or troubleshoot Worker export syntax, API route conflicts, HMR issues, or deployment failures.
codex-reviewRun an independent code review using the OpenAI Codex CLI in headless mode. Gets a second opinion from a different model family (the current Codex models) on recent changes, a PR, a commit, or the whole app — covering bugs, regressions, security, data consistency, UX/state bugs, performance risks, and testing gaps. Saves a severity-prioritised report to .jez/reviews/. Triggers: 'codex review', 'review with codex', 'independent code review', 'what does codex think', 'get codex to review'.
color-paletteGenerate complete, accessible colour palettes from a single brand hex. Produces 11-shade scale (50-950), semantic tokens, dark mode variants, Tailwind v4 CSS output, WCAG contrast checks. Use whenever the user supplies a brand hex and asks for a palette, mentions setting up a design system, wants Tailwind theme colours from a brand colour, or asks to check colour accessibility / contrast.
d1-drizzle-schemaGenerate Drizzle ORM schemas for Cloudflare D1 databases with correct D1-specific patterns. Produces schema files, migration commands, type exports, and DATABASE_SCHEMA.md documentation. Handles D1 quirks: foreign keys always enforced, no native BOOLEAN/DATETIME types, 100 bound parameter limit, JSON stored as TEXT. Use when creating a new database, adding tables, or scaffolding a D1 data layer.
d1-migrationCloudflare D1 migration workflow: generate with Drizzle, inspect SQL for gotchas, apply to local and remote, fix stuck migrations, handle partial failures. Use when running migrations, fixing migration errors, or setting up D1 schemas.