cloudflare-api
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,…
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
$ npx -y skills add jezweb/claude-skills --skill uk-business-english --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/uk-business-englishContext preview
The summary Claude sees to decide when to auto-load this skill.
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
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."
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".
| 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.
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".
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).
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" |
Avoid in written professional comms:
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.
**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 t
Production workflow skills for Claude Code. Each skill guides Claude through a recipe to produce tangible output — scaffolded projects, generated assets, professional documents, deployed services. Ten plugins of practical, production-oriented skills.
Repo: jezweb/claude-skills
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,…
Scaffold and deploy Cloudflare Workers with Hono routing, Vite plugin, and Static Assets. Describe project, scaffold structure, configure bindings, deploy. Use…
Generate Drizzle ORM schemas for Cloudflare D1 databases with correct D1-specific patterns. Produces schema files, migration commands, type exports, and…
Cloudflare D1 migration workflow: generate with Drizzle, inspect SQL for gotchas, apply to local and remote, fix stuck migrations, handle partial failures. Use…
Generate database seed scripts with realistic sample data. Reads Drizzle schemas or SQL migrations, respects foreign key ordering, produces idempotent…
Scaffold Hono API routes for Cloudflare Workers. Produces route files, middleware, typed bindings, Zod validation, error handling, and API_ENDPOINTS.md…