Skip to main content
ClaudeWave
EN, English
Skill1.1k repo starsupdated 20d ago

nz-business-english

This Claude Code skill applies New Zealand business English conventions to professional communications, enforcing EN-NZ spelling (colour, organise, centre), warm collaborative tone, and appropriate use of Te Reo Maori phrases like "Kia ora" and "Nga mihi." Use it when drafting or editing emails, proposals, web copy, or client communications intended for New Zealand audiences to ensure culturally appropriate and linguistically correct business writing.

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

SKILL.md

# 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
ai-image-generatorSkill

Generate 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-docsSkill

Generate 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-englishSkill

Australian 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-applicationSkill

Write 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.

brains-trustSkill

Get a second opinion from leading AI models on code, architecture, strategy, prompting, or anything. Queries models via OpenRouter, Gemini, or OpenAI APIs. Supports single opinion, multi-model consensus, and devil's advocate patterns. Use whenever the user says 'brains trust', 'second opinion', 'ask gemini', 'ask gpt', 'peer review', 'consult another model', 'challenge this', or 'devil's advocate'.

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.

codex-reviewSkill

Run 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'.