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,…
American business English writing style for professional communications — direct, action-oriented, EN-US spelling (color, organize, center). Use whenever the user is writing for an American audience: emails, chat messages, proposals, client communications, blog posts, web copy,
$ npx -y skills add jezweb/claude-skills --skill us-business-english --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/us-business-englishContext preview
The summary Claude sees to decide when to auto-load this skill.
American business English writing style for professional communications — direct, action-oriented, EN-US spelling (color, organize, center). Use whenever the user is writing for an American audience: emails, chat messages, proposals, client communications, blog posts, web copy,
name: us-business-english description: "American business English writing style for professional communications — direct, action-oriented, EN-US spelling (color, organize, center). Use whenever the user is writing for an American 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 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.
| 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.
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).
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).
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" |
Avoid in written professional comms:
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.
**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]
**Too stiff:
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…