aussie-business-english
The aussie-business-english Claude Code skill applies Australian professional communication standards to business writing, including EN-AU spelling conventions (colour, organise, centre), appropriate tone calibration from casual to formal based on context, and culturally aligned greetings and sign-offs. Use this skill when drafting or editing emails, proposals, web copy, or any professional communication intended for Australian audiences.
git clone --depth 1 https://github.com/jezweb/claude-skills /tmp/aussie-business-english && cp -r /tmp/aussie-business-english/plugins/writing/skills/aussie-business-english ~/.claude/skills/aussie-business-englishSKILL.md
# Aussie Business English
Write like a competent professional who happens to be Australian: professional but not corporate, warm but not forced, direct but not blunt. Say it once, plainly, and stop.
## Non-negotiables
- **Australian spelling**: colour, organise, centre, travelling, defence. Noun/verb pairs: licence/license, practice/practise.
- **No filler words.** Cut "actually", "really", "basically", "simply", "essentially" and "just" wherever deleting them changes nothing. Headings especially: "How a toilet works", never "How a toilet actually works".
- **No AI tells.** Avoid em dashes, "delve", "seamless", "robust", "it's worth noting", "not just X, but Y", and exclamation marks in business copy.
- **Lead with the point.** First sentence carries the answer or the ask. Short paragraphs, active voice, natural contractions. Be specific: "by Thursday", not "soon".
## Tone
Default is friendly professional. Open with "Hi [Name]". Close with "Cheers" (or "Thanks" when asking for something, "Kind regards" for new clients and formal documents). Keep "Dear [Name]" and "Yours sincerely" for formal or legal letters only. Never "Dear Sir/Madam", "Best", or "Warm regards".
Match the reader: short message in, short reply out. For corporate clients, go one notch more formal and keep the warmth, but don't mirror their jargon back.
Bad news: direct and kind, one "sorry" at most, then the path forward. Saying no: brief reason, offer an alternative if you have one. Prices: state them plainly ("The cost is $4,500"), no hedging.
## Swap list
| Not this | This |
|---|---|
| reach out | get in touch |
| circle back / touch base | follow up / catch up |
| leverage | use |
| deep dive | closer look |
| bandwidth | time, capacity |
| deliverables | the work, what we'll provide |
| moving forward | (drop it) |
No forced Australianisms in writing: no "G'day", "fair dinkum" or "crikey"; "mate" once at most; "no worries" only for small acknowledgements, never for serious problems.
## The tone, in one example
> Hi Sarah,
>
> Thanks for the chat yesterday. I've put together a quote based on what we discussed: $4,500 for the full site including the booking system, covering design, development and launch.
>
> Happy to jump on a call if you've got any questions.
>
> Cheers,
> JeremyHit 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'.
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.
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.
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.
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'.
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.
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.
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.