/write-natural-swedish

Presets for Contemporary and Tech-Company Swedish

Use these presets when the user asks for modern Swedish, technology-company writing, developer-facing text, product copy, or workplace communication in a tech context.

Contemporary

Goal: sound current without sounding forced.

• Prefer words that are already normal in Swedish usage: app, mejl, sajt, webbplats, chattbott, AI, molntjänst, plattform, integration, data, funktion.
• Use new words only when they genuinely name the thing. AI-agent, digital suveränitet, and vibbkodning can be right in current tech contexts; they should not be sprinkled into ordinary copy for freshness.
• Keep English terms when they are product names, protocol/API names, command names, UI strings, or the established term in the target company.
• Translate concepts, not vibes. vibe coding may become vibbkodning in trend/reporting contexts, but AI-stödd programmering or programmering med AI may be clearer in enterprise or customer copy.
• Avoid faux-modern filler: superladda, disrupta, gamechanger, next-gen, sömlös as a reflex, and English adjective order copied into Swedish.

Tech Company

Goal: sound like a credible Swedish tech company.

• Be concrete before enthusiastic: say what the product does, who it helps, and what changes for the user.
• Use calm confidence. Swedish business tech copy often works better with evidence and clarity than with big claims.
• Prefer du for product UI, support, documentation, and most SaaS copy. Use ni only for the customer organization when the text clearly addresses a company as a group.
• Prefer verbs over abstractions: automatisera, skydda, samla, analysera, prioritera, publicera, felsöka, integrera.
• Keep English product and engineering terms when Swedish alternatives sound unnatural to the audience, but explain them when writing for mixed technical/business readers.
• Use Swedish compounds carefully: molnkostnader, säkerhetsgranskning, driftstatus, kunddata, produktteam, lanseringskandidat, API-integration.
• Avoid literal English business phrasing: driva värde, på skala, ta action, låsa upp potential, flytta nålen.

Developer Docs

Goal: make Swedish technical instructions easy to follow.

• Use direct instructions: Skapa en ny nyckel, Kör kommandot, Lägg till variabeln.
• Put conditions before actions: Om bygget misslyckas, kör...
• Keep code, CLI flags, env vars, HTTP methods, endpoint paths, UI labels, and product names unchanged.
• Use consistent terms across the page. Do not alternate between driftsätta, deploya, and publicera unless the distinction matters.
• Prefer present tense and active voice: API:t returnerar..., Tjänsten skapar...
• Avoid unnecessary politeness in steps. Use Klicka på Spara, not Vänligen klicka på Spara.
• Explain acronyms on first use for mixed audiences: rollbaserad åtkomstkontroll (RBAC).

Product Marketing

Goal: Swedish product copy that is persuasive without sounding imported.

• Lead with the user outcome, then the mechanism.
• Make claims testable: minskar manuell handpåläggning, samlar kostnadsdata, visar avvikelser i realtid.
• Prefer Swedish benefit verbs over English launch language: kom igång, få överblick, upptäck risker, prioritera åtgärder.
• Use smart, enkel, snabb, and säker only when the surrounding sentence proves the claim.
• Avoid exclamation marks, inflated adjectives, and generic framtidens... unless the requested tone is explicitly campaign-like.

Startup Internal

Goal: natural workplace Swedish inside a product/engineering team.

• Keep it direct and warm: Kan du skicka testresultaten i dag?
• Use a little shared tech vocabulary if the team would: release, PR, deploy, rollback, feature flag.
• Keep Swedish grammar around English terms: deployen, PR:en, feature flaggen only in informal team contexts; use clearer rephrasing in external copy.
• Prefer risker som återstår, blockerar lanseringen, behöver verifieras, nästa steg over literal English project phrasing.

Term Choice Heuristics