Use when writing German-language prose longer than one sentence for Jira tickets, internal German wiki/spec docs, or team-chat to German-speaking colleagues (Slack, Matrix, Teams). Invoke BEFORE composing, not after. Enforces natural German technical register by catching English→German anglicisms (brechen, gefangen, returnen, triggern, failen, die Test, hit, end up) and substituting canonical verbs (werfen, abfangen, zurückgeben, auslösen, fehlschlagen, der Test, auf … stoßen, landen). Also enforces present-indicative tense, impersonal voice, and Denglisch-loanword lexicon (der Commit, die Pipeline, der Branch, die Exception). Skip for commit messages, MR/PR descriptions, release notes (English by team convention), conversational chat replies, internal reasoning, single-line acknowledgments ('Ok', 'Danke'), or English artifacts containing German identifiers. If you catch yourself thinking 'my German is probably fine here' for anything longer than a sentence — invoke this skill.
How this skill is triggered — by the user, by Claude, or both
Slash command
/german-technical-writing:german-technical-writingThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Natural German technical register for German-audience artifacts. Prevents English-first composition plus phrase-by-phrase translation, which produces grammatically correct German that reads as DeepL-output to native readers.
Natural German technical register for German-audience artifacts. Prevents English-first composition plus phrase-by-phrase translation, which produces grammatically correct German that reads as DeepL-output to native readers.
references/anti-patterns.md.references/lexicon.md.references/register.md.| ❌ | ✅ |
|---|---|
| code bricht | schlägt fehl / wirft Exception |
| gefangen | erkannt / abgefangen |
| null returnen | null zurückgeben |
| Test failt | schlägt fehl / fällt durch |
| Fehler triggern | Fehler auslösen |
| auf Fehler hitten | auf Fehler stoßen |
Full ~60-entry catalogue plus pseudo-anglicisms and idiom calques in references/anti-patterns.md. Worked pair-examples in references/examples.md.
Two failure modes — over-applying one drives you into the other:
anti-patterns.md target this.anti-patterns.md ("Compound-noun calques") and lexicon.md ("Debugging / Postmortem / Analysis").Decision rule for nouns: if a native German developer would say the term verbatim in a code review or stand-up, keep it English. The litmus test isn't "does a German equivalent exist?" — it's "do German engineers actually use it in everyday speech?" A German form that sounds like a textbook chapter title is a calque.
Absorbing "use German verbs" without "keep loanword nouns" produces DeepL-grade output. Apply both simultaneously.
Commit messages, MR/PR descriptions, release notes and internal IT-project tickets (Netresearch: NRS, NRT, SRV*, IO*, LIC) are English — skip them. This skill governs how to write German, never whether German is the right choice.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Applies a firm's KYC/AML rules grid to parsed onboarding records: assigns risk rating, checks required documents, outputs rule outcomes with citations, and routes for escalation.
Generates daily or weekly digests of activity from connected sources (chat, email, docs, tasks, CRM), highlighting action items, decisions, mentions, and project updates.
npx claudepluginhub netresearch/claude-code-marketplace --plugin german-technical-writing