Skip to main content
ClaudeWave
Skill853 repo starsupdated yesterday

us-business-english

The us-business-english skill applies American professional communication standards to business writing, including EN-US spelling conventions (color, organize, center), appropriate tone calibration based on context, and proper formatting for dates and sign-offs. Use this skill when drafting or editing emails, proposals, chat messages, and other professional communications intended for American audiences to ensure clarity, directness, and cultural appropriateness.

Install in Claude Code
Copy
git clone --depth 1 https://github.com/jezweb/claude-skills /tmp/us-business-english && cp -r /tmp/us-business-english/plugins/writing/skills/us-business-english ~/.claude/skills/us-business-english
Then start a new Claude Code session; the skill loads automatically.

SKILL.md

# US Business English

Professional and direct. Confident without being pushy. Friendly without being sloppy. Write like a competent American professional who gets things done -- not like a Silicon Valley bro, not like a Wall Street memo, and not like a corporate buzzword machine.

## Spelling (EN-US)

| Pattern | American | Not |
|---------|----------|-----|
| -or | color, favor, honor, behavior | colour, favour |
| -ize | organize, realize, specialize, recognize | organise, realise |
| -er | center, fiber, meter, theater | centre, fibre |
| -ense | license (noun and verb), defense, offense | licence (noun), defence |
| Single L | traveling, canceling, modeling | travelling, cancelling |
| -og | catalog, dialog, analog | catalogue, dialogue |
| -ment | judgment, acknowledgment | judgement, acknowledgement |

**Noun/verb note:** Unlike British/Australian English, American English uses "license" and "practice" for both noun and verb forms. No split needed.

**Common traps:** inquiry (standard, not enquiry), curb (road edge), tire (wheel), program (all contexts), check (not cheque), gray (not grey).

**Date format:** Month Day, Year -- January 15, 2026. Use this in all written communications unless matching a specific system format.

## Tone Ladder

Match formality to context. Default to "professional friendly" -- clear and personable.

| Context | Formality | Greeting | Sign-off |
|---------|-----------|----------|----------|
| Slack/Teams (internal) | Casual | "Hey" / first name | None needed |
| Email to existing client | Professional friendly | "Hi [Name]" | "Best" / "Thanks" |
| Email to new client | Professional | "Hi [Name]" | "Best" / "Thanks" |
| Proposal or quote | Professional | "Hi [Name]" | "Best regards" / "Best" |
| Follow-up after meeting | Professional friendly | "Hi [Name]" | "Thanks" / "Talk soon" |
| Cold outreach | Warm professional | "Hi [Name]" | "Best" / "Thanks" |
| Formal letter or legal | Formal | "Dear [Name]" | "Sincerely" |

**Never use:** "Dear Sir/Madam" (unless truly unknown recipient in legal context), "Warmest regards", "Respectfully yours" (reserve for military/government), "Cheers" (reads as affected British).

## Sign-off Ranking

From most to least common in US SME context:

1. **Best** -- default, works almost everywhere
2. **Thanks** -- when you're asking for something or appreciating effort
3. **Best regards** -- one step more formal, good for proposals
4. **Regards** -- neutral, slightly cooler
5. **Talk soon** -- casual, signals ongoing relationship

**Avoid:** "Cheers" (sounds British/Australian to American ears), "Kind regards" (slightly stiff), "Warm regards" (overdone), "Respectfully" (government/military tone).

## Avoid List

### Corporate Buzzwords

Replace these reflexively:

| Instead of | Write |
|-----------|-------|
| "synergy" / "synergize" | "working together" / "combined effort" |
| "leverage" (verb) | "use" / "take advantage of" |
| "circle back" | "follow up" / "come back to this" |
| "touch base" | "check in" / "connect" |
| "loop in" | "include" / "bring in" |
| "bandwidth" (for time) | "time" / "capacity" |
| "actionable insights" | "useful information" / "what we found" |
| "move the needle" | "make a difference" / "improve" |
| "deep dive" | "closer look" / "detailed review" |
| "pivot" | "change direction" / "adjust" |
| "align on" | "agree on" / "get on the same page" |
| "unpack" (an idea) | "look at" / "go through" |
| "cadence" | "schedule" / "frequency" |
| "deliverables" | "what we'll provide" / "the work" |

### Foreign-isms and Overcorrections

Avoid in written professional comms:

- **"Whilst", "amongst"** -- use "while", "among"
- **"Shall"** -- use "will" or "should"
- **"Keen"** -- use "interested" or "excited about"
- **"Brilliant" / "lovely"** -- sounds British, use "great" / "sounds good"
- **"Dude", "awesome", "totally"** in formal emails -- fine on Slack, not in proposals
- **Forced casualness** -- "Hey buddy!" to a new client is too much

## Writing Principles

1. **Lead with the point.** First sentence answers the question or states the purpose. Context comes after, not before.

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

3. **Natural contractions.** "We've", "I'll", "that's", "won't" -- reads human. Ease off slightly in proposals, but emails should sound like a person wrote them.

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

5. **Specific over vague.** "I'll have this to you by Thursday" not "I'll get back to you soon."

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

7. **Match their energy.** Short email from client? Short reply. Detailed brief? Detailed response. Don't write five paragraphs when two lines will do.

## Examples

### Status update to existing client

**Too corporate:**
> Dear Mr. Thompson, I am writing to provide you with a comprehensive update regarding the current status of your website redesign project. Please find below a summary of the deliverables completed to date and the anticipated timeline for remaining action items moving forward.

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

### Delivering a quote

**Too stiff:**
> Dear Client, Please find attached our formal quotation for the proposed scope of work as discussed. We trust this meets your requirements and look forward to your favorable 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. The short version: $4,500 for t
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.