nz-business-english

$npx mdskill add jezweb/claude-skills/nz-business-english

Write professional New Zealand English with warm, inclusive tone and EN-NZ spelling.

  • Drafts or edits business communications for a New Zealand audience.
  • Depends on built-in language model and spelling rules for EN-NZ.
  • Applies EN-NZ spelling, inclusive tone, and Te Reo Māori where appropriate.
  • Returns rewritten text with corrected spelling, tone, and regional style.

SKILL.md

.github/skills/nz-business-englishView on GitHub ↗
---
name: nz-business-english
description: "New Zealand business English writing style for professional communications — warm, inclusive, EN-NZ spelling (colour, organise, centre). Use whenever the user is writing for a New Zealand audience: emails, chat messages, proposals, client communications, blog posts, web copy, or any business writing. Apply to drafting, editing, and tone-checking professional text."
---

# NZ Business English

Professional but approachable. Warm without being over-the-top. Inclusive by default. Write like a competent Kiwi professional -- not like an Australian pretending to be from New Zealand, not like someone who just discovered Te Reo, and not like a corporate drone.

NZ English is close to Australian English in spelling and register, but softer in tone, more collaborative in framing, and increasingly incorporates Te Reo Maori in everyday business use.

## Spelling (EN-NZ)

EN-NZ follows the same conventions as EN-AU:

| Pattern | New Zealand | 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 |
| Double L | travelling, cancelling, modelling | traveling, canceling |

**Noun/verb splits:**

| Noun | Verb |
|------|------|
| licence | license |
| practice | practise |
| advice | advise |

**NZ-specific vocabulary:**

| NZ term | AU/US equivalent |
|---------|-----------------|
| diary | calendar / schedule |
| ring | call / phone |
| fortnight | two weeks (uncommon in US) |
| bach (North Island) / crib (South Island) | holiday house |
| whanau | family / team (Te Reo, widely understood) |

**Date format:** Day Month Year, no comma -- 15 January 2026. Same as UK/AU convention.

## Te Reo Maori in Business

Te Reo greetings and phrases are increasingly standard in NZ business, especially in government, education, and community-facing organisations. Use them naturally, not performatively.

| Phrase | Use |
|--------|-----|
| Kia ora | General greeting -- equivalent to "Hi". Safe default for any context. |
| Kia ora [Name] | Personal greeting. Widely used in emails. |
| Nga mihi | "With thanks / regards" -- common sign-off |
| Nga mihi nui | "With great thanks" -- warmer, for appreciative contexts |
| Morena | "Good morning" -- informal, internal comms |
| Ka pai | "Good / well done" -- informal acknowledgement |

**When to use:** Match the organisation's culture. Government and iwi organisations expect it. Corporate clients may or may not use it -- follow their lead. When in doubt, "Kia ora" as a greeting is universally appropriate in NZ.

**When not to use:** Don't sprinkle random Te Reo words through otherwise English text for decoration. Use complete phrases that you understand the meaning of.

## Tone Ladder

Match formality to context. Default to "warm professional" -- a touch softer and more collaborative than Australian.

| Context | Formality | Greeting | Sign-off |
|---------|-----------|----------|----------|
| Slack/Teams (internal) | Casual | "Hey" / "Kia ora" | None needed |
| Email to existing client | Warm professional | "Kia ora [Name]" / "Hi [Name]" | "Cheers" / "Nga mihi" |
| Email to new client | Professional | "Kia ora [Name]" / "Hi [Name]" | "Kind regards" / "Nga mihi" |
| Proposal or quote | Professional | "Kia ora [Name]" | "Kind regards" / "Nga mihi" |
| Follow-up after meeting | Warm professional | "Hi [Name]" | "Cheers" / "Thanks" |
| Cold outreach | Warm professional | "Kia ora [Name]" / "Hi [Name]" | "Kind regards" |
| Formal letter or legal | Formal | "Dear [Name]" | "Yours sincerely" / "Nga mihi" |

**Never use:** "Dear Sir/Madam" (unless legal/unknown), "Warmest regards", "Respectfully yours".

## Sign-off Ranking

From most to least common in NZ SME context:

1. **Cheers** -- default, works almost everywhere
2. **Nga mihi** -- warm, culturally appropriate, increasingly standard
3. **Thanks** -- when asking for something or appreciating effort
4. **Kind regards** -- one step more formal, good for new clients
5. **Regards** -- neutral, slightly cooler

**Avoid:** "Best" (reads as American), "Warm regards" (overdone), "Ta" (too casual for written comms).

## Avoid List

### Foreign Corporate-isms

Replace these reflexively:

| Instead of | Write |
|-----------|-------|
| "reach out" | "get in touch" / "contact" |
| "circle back" | "follow up" / "come back to" |
| "touch base" | "check in" / "catch up" |
| "leverage" (verb) | "use" / "make the most of" |
| "moving forward" | "from here" / "going forward" (or drop it) |
| "actionable insights" | "useful information" / "what we found" |
| "deep dive" | "closer look" / "detailed review" |
| "bandwidth" (for time) | "time" / "capacity" |
| "deliverables" | "what we'll provide" / "the work" |
| "align on" | "agree on" / "sort out" |

### Forced Kiwi-isms

Avoid in written professional comms:

- **"Sweet as", "choice", "mean as"** -- spoken slang, not business writing
- **"Bro" / "cuz"** -- casual spoken, inappropriate in professional writing
- **"She'll be right"** -- fine spoken, dismissive in writing about real issues
- **"Chur"** -- very informal, not for business emails
- **Overuse of Te Reo for decoration** -- use phrases you understand, not random words
- **"No worries" for serious issues** -- fine for acknowledgements, wrong for "Your site has been offline for two days"

### Australian-isms That Don't Apply

- **"Arvo", "brekkie", "barbie"** -- Australian slang, not NZ
- **"G'day"** -- distinctly Australian, not Kiwi
- **"Fair dinkum"** -- Australian, not used in NZ

## 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 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. **Collaborative framing.** NZ business culture skews collaborative. "We could look at this together" rather than "I'll handle this". "What do you think?" is a natural closer.

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 an update regarding the progress of your website redesign project. Please find below a summary of the deliverables completed to date and the anticipated timeline for remaining action items.

**Right tone:**
> Kia ora David,
>
> Quick update on the website -- we've finished the homepage and the three main service pages. Looking good so far.
>
> Next up is the contact form and booking system, which we'll have sorted by end of next week. I'll send through a preview link once it's live on the staging site.
>
> Cheers,
> [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 favourable response at your earliest convenience.

**Right tone:**
> Kia ora Sarah,
>
> Thanks for the chat 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 the full site, including the booking system. That covers design, development, and getting it live on your domain.
>
> Happy to jump on a call if you've got any questions.
>
> Nga mihi,
> [Your name]

### Saying no to a request

**Too blunt:**
> We can't do that.

**Too soft:**
> While we certainly appreciate your suggestion and would love to explore this further, unfortunately at this current juncture it may not be feasible for us to accommodate this particular request.

**Right tone:**
> Kia ora Mark,
>
> Thanks for thinking of us for this. Unfortunately it's not something we can take on right now -- we're at capacity through March.
>
> If timing works, we'd be happy to look at it in April. Otherwise, I can put you in touch with a couple of people who might be able to help sooner.
>
> Cheers,
> [Your name]

## Context Rules

**Corporate clients:** Match their formality up one notch but keep the warmth. "Kind regards" instead of "Cheers", but still "Kia ora [Name]" or "Hi [Name]" not "Dear Mr Smith". Never mirror their jargon back.

**Delivering bad news:** Be direct but kind. State the issue, explain why briefly, offer the path forward. No waffle, no excessive apologies. One "sorry" is enough.

**Quoting prices:** Direct and confident. "The cost for this is $X" not "We would like to propose a fee of $X for your consideration." Include what's covered. State GST position (inclusive/exclusive) explicitly -- NZ GST is 15%.

**Saying no:** Respectful and brief. Give the reason (one sentence), offer an alternative if possible. Don't over-explain or apologise excessively. "Put you in touch with" is more Kiwi than "recommend".

**Following up:** Casual but purposeful. "Just checking in on this" is fine. "I trust this email finds you well" is not.

More from jezweb/claude-skills

SkillDescription
ai-image-generatorGenerate AI images using Gemini or GPT APIs directly. Covers model selection (Gemini for scenes; GPT Image 2 for text rendering, batch variations, multi-reference compositing; GPT Image 1.5 for transparent icons), the 5-part prompting framework, API calling patterns, multi-turn editing, and quality assurance. Produces photorealistic scenes, icons, illustrations, OG images, posters, infographics, and product shots. Use when building websites that need images, creating marketing assets, or generating visual content. Triggers: 'generate image', 'ai image', 'create hero image', 'make an icon', 'generate illustration', 'create og image', 'poster', 'infographic', 'image variations', 'gpt-image-2', 'ai art', 'image generation'.
app-docsGenerate complete user documentation for a web app with screenshots. Browses the app via browser automation, screenshots every screen, and produces a structured user guide with step-by-step instructions, annotated screenshots, workflow diagrams, and reference tables. Supports quick (key screens), standard (all pages), thorough (every state and flow), and exhaustive (publishable documentation suite). Triggers: 'document the app', 'user guide', 'app documentation', 'screenshot docs', 'generate user docs', 'help docs', 'how-to guide', 'write the docs'.
aussie-business-englishAustralian business English for professional writing — warm, direct, EN-AU spelling (colour, organise, centre), no filler words. Use whenever the user is writing for an Australian audience: emails, chat messages, proposals, client communications, blog posts, web copy, or any business writing. Apply to drafting, editing, and tone-checking professional text.
award-applicationWrite compelling award submissions, grant applications, and competition entries. Maps achievements to selection criteria using evidence-based narratives. Use whenever the user is applying for a business award (Telstra, chamber of commerce, industry awards), a grant, a competition, or any submission demonstrating merit against defined criteria.
cloudflare-apiHit 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-builderScaffold 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.
codex-reviewRun an independent code review using the OpenAI Codex CLI in headless mode. Gets a second opinion from a different model family (the current Codex models) on recent changes, a PR, a commit, or the whole app — covering bugs, regressions, security, data consistency, UX/state bugs, performance risks, and testing gaps. Saves a severity-prioritised report to .jez/reviews/. Triggers: 'codex review', 'review with codex', 'independent code review', 'what does codex think', 'get codex to review'.
color-paletteGenerate complete, accessible colour palettes from a single brand hex. Produces 11-shade scale (50-950), semantic tokens, dark mode variants, Tailwind v4 CSS output, WCAG contrast checks. Use whenever the user supplies a brand hex and asks for a palette, mentions setting up a design system, wants Tailwind theme colours from a brand colour, or asks to check colour accessibility / contrast.
d1-drizzle-schemaGenerate 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-migrationCloudflare 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.