Skip to main content
ClaudeWave
Skill853 estrellas del repoactualizado yesterday

uk-business-english

This Claude Code skill applies British English conventions to professional business writing, including EN-GB spelling rules (colour, organise, centre), noun-verb distinctions (licence/license, practice/practise), and appropriate formality levels for different contexts. Use it when drafting or refining business communications for British audiences, such as client emails, proposals, internal messages, or web copy, to ensure polished, measured tone and correct regional spelling standards.

Instalar en Claude Code
Copiar
git clone --depth 1 https://github.com/jezweb/claude-skills /tmp/uk-business-english && cp -r /tmp/uk-business-english/plugins/writing/skills/uk-business-english ~/.claude/skills/uk-business-english
Después abre una sesión nueva de Claude Code; el skill carga automáticamente.

SKILL.md

# 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
cloudflare-apiSkill

Hit 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-builderSkill

Scaffold 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.

d1-drizzle-schemaSkill

Generate 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-migrationSkill

Cloudflare 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.

db-seedSkill

Generate database seed scripts with realistic sample data. Reads Drizzle schemas or SQL migrations, respects foreign key ordering, produces idempotent TypeScript or SQL seed files. Handles D1 batch limits, unique constraints, and domain-appropriate data. Use when populating dev/demo/test databases. Triggers: 'seed database', 'seed data', 'sample data', 'populate database', 'db seed', 'test data', 'demo data', 'generate fixtures'.

hono-api-scaffolderSkill

Scaffold Hono API routes for Cloudflare Workers. Produces route files, middleware, typed bindings, Zod validation, error handling, and API_ENDPOINTS.md documentation. Use after a project is set up with cloudflare-worker-builder or vite-flare-starter, when you need to add API routes, create endpoints, or generate API documentation.

tanstack-startSkill

Build a full-stack TanStack Start app on Cloudflare Workers from scratch — SSR, file-based routing, server functions, D1+Drizzle, better-auth, Tailwind v4+shadcn/ui. Use whenever the user mentions TanStack Start, asks to scaffold a full-stack Cloudflare app with SSR, wants an SSR dashboard, or asks for a React 19 + Cloudflare Workers app with file-based routing and server functions — even if they don't name TanStack Start specifically. No template repo — Claude generates every file fresh per project.

vite-flare-starterSkill

Scaffold a full-stack Cloudflare app from the vite-flare-starter template — React 19 + Hono + D1+Drizzle + better-auth + Tailwind v4+shadcn/ui + TanStack Query + R2 + Workers AI. Run setup.sh to clone, configure, and deploy. Use whenever the user wants a batteries-included Cloudflare full-stack app, vite-flare-starter scaffold, or a React + Cloudflare app with auth + database + Workers AI ready to go.