nz-business-english
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.
What this skill does
# 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
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.