Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
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 that reads as DeepL-output to natives.
Natural German technical register for German-audience artifacts. Prevents English-first composition plus phrase-by-phrase translation that reads as DeepL-output to natives.
references/anti-patterns.md.references/lexicon.md.references/register.md.references/no-editorializing.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.
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 review or stand-up, keep it English. The test isn't "does a German equivalent exist?" but "do German engineers actually say it?" A German form that sounds like a textbook title is a calque.
"German verbs" without "keep loanword nouns" produces DeepL-grade output. Apply both.
Commit messages, MR/PR descriptions, release notes and internal IT-project tickets (NRS, NRT, SRV*, IO*, LIC) are English — skip them. This skill governs how to write German, never whether German is the right choice.
Runs an interview-style session to sharpen a plan or design, producing ADRs and a glossary as you go.
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.
npx claudepluginhub netresearch/claude-code-marketplace --plugin german-technical-writing