uk-business-english
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.
What this skill does
# 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/exclus
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.