# Norriq Writing

> Writing guide for NORRIQ content. Kills AI tells, enforces plain language in Danish and English. Use for any customer-facing text, internal docs, PR descriptions, emails, or posts.

- Skill: `saturate/norriq-writing` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add saturate/norriq-writing`
- Raw SKILL.md: https://api.skillmd.com/api/skills/saturate/norriq-writing/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: Saturate (https://skillmd.com/u/saturate)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/saturate/norriq-writing

---


# NORRIQ Writing Guide

Write like a person who knows the subject and respects the reader's time. NORRIQ's voice is direct, plain, and outcome-focused. "Your Business - Simplified" is the tagline; the writing should match it.

## Voice

- **Direct.** Say what you mean in the fewest words that are still clear.
- **Outcome-focused.** Talk about what the customer gets, not what the product does.
- **Plain.** If a simpler word works, use it. "Use" not "utilize." "Help" not "facilitate."
- **Confident without bragging.** State what we do. Skip superlatives.

## Banned AI patterns

These are the patterns that make text read as machine-generated. Remove all of them.

### Banned punctuation
- **Em dash (-)** is banned. Use a comma, semicolon, period, or rewrite.

### Banned words

Replace with plain equivalents or cut entirely.

| Avoid | Use instead |
|---|---|
| delve, leverage, utilize | explore, use, use |
| foster, bolster, underscore | support, strengthen, highlight |
| streamline, enhance, facilitate | simplify, improve, help |
| robust, comprehensive, pivotal | strong, complete, key |
| seamless, cutting-edge, innovative | smooth, modern, new |
| transformative, holistic, multifaceted | significant, complete, complex |
| furthermore, moreover, indeed | also, and, (just cut it) |
| notwithstanding, that being said | despite, but, however |
| it's important to note that | (cut it, just state the thing) |
| in today's fast-paced world | (cut the whole phrase) |
| in the ever-changing landscape of | in |

### Banned constructions

- **"Not only... but also..."** Just state both things.
- **"Whether you're a [X], [Y], or [Z]..."** Never.
- **"It's not X, it's Y"** State your point directly.
- **"Here's the thing:"** / **"The bottom line:"** Just say it.
- **Rhetorical questions answered immediately.** "The fix? Simple." Ask a real question or make the statement.
- **Rule of three.** "Fast, efficient, and reliable." Two items or four. Three is the AI default.
- **Staccato fragments.** "That's the problem. The real problem." Once in a long piece, maybe. Otherwise no.
- **Exclamation marks.** State facts. No cheerleading.

### Banned openers and closers

- "In today's..." / "In an era of..." / "In the realm of..."
- "Let's dive in" / "Let's explore"
- "In conclusion..." / "To sum up..." / "At the end of the day..."
- "By [doing X], you can [achieve Y]..."

### Hedging

AI hedges 4-7x more than humans. Watch for:
- "may potentially", "might be able to", "could possibly"
- "it seems", "it appears that", "one could argue"

Either it happens or it doesn't. If genuinely uncertain, say "we don't know yet" once and move on.

## Danish-specific rules

These apply when writing in Danish.

- **Use common Danish, not consultant-Danish.** "Hjælper virksomheder" not "faciliterer virksomheders digitale transformation."
- **Avoid direct anglicism when a Danish word works.** "Forbedre" not "optimere" when you mean improve. "Gennemgang" not "review" when writing Danish prose.
- **Keep sentences short.** Danish business writing already tends toward long compound sentences. Break them up.
- **"Vi hjælper"** is the NORRIQ pattern. We help. Not "vi muliggør", not "vi driver", not "vi accelererer."

## English-specific rules

- **Use active voice.** "We built the integration" not "The integration was built."
- **No academic phrasing.** "Before" not "prior to." "About" not "pertaining to." "Because" not "in light of."
- **Short paragraphs.** Three to five sentences max. One-sentence paragraphs are fine.

## Slides and presentations

The same rules apply to PowerPoint, Google Slides, and any presentation format. Extra rules:

- **One idea per slide.** If you need "and" in the slide title, split it.
- **Slide titles are statements, not topics.** "Migration cut downtime by 40%" not "Migration Results."
- **No walls of text.** Bullet points max 8 words each. If you need a paragraph, it belongs in the speaker notes.
- **Same banned words apply.** "Comprehensive solution" on a slide is worse than in prose because it's the only thing on screen.

## Self-review checklist

Run this before sending any text, slide deck, or document.

1. Search for em dash. Remove every one.
2. Scan for banned words from the table above. Replace with plain equivalents.
3. Scan for banned constructions and openers/closers. Cut them.
4. Count hedging words per paragraph. More than two in one paragraph is too many.
5. Check every sentence: does it end on something concrete, or just assert importance?
6. Read it aloud. If it sounds like a press release, rewrite it to sound like a person.
7. Is every paragraph roughly the same length? Vary them.
8. Check for exclamation marks. Remove them.
9. Would your colleague skim past this? If yes, it's too long. Cut.
10. Run steps 1-9 again. Banned words creep back in.

## Sources

For deeper reading on why these rules exist: [references/sources.md](references/sources.md)