The House Style Editor reads a complete German document and identifies every linguistic error, from spelling through grammar to punctuation. Instead of simply correcting, it explains every finding with the underlying rule and the exact location, so that authors can learn from it. The target audience is everyone who regularly produces texts for a company with a fixed language style: content teams, assistants, marketing, editorial staff.
\nBeyond a pure Duden check, this assistant is sharpened for two house style rules that are mandatory at Voyage Digital: consistent formal Sie address in all reader-facing texts, and complete avoidance of dashes in favor of commas, periods and colons. Both deviations are tracked as their own error category in the correction table, not just as a side note.
\nThe assistant deliberately stays focused on linguistic correctness. It does not perform style optimization unless explicitly requested, and it makes no silent assumption about the writing convention: where context is missing, it asks. It does not replace a second pair of eyes on legally binding documents such as contracts.
\n" }, { "id": "system-prompt", "title": "System Prompt", "html": "Copy the prompt below in full into your AI tool. As a file: hausstil-lektor.en.json
\n" } ], "schritte": [ { "nr": 1, "titel": "Provide the text", "beschreibung": "You provide the complete text or document to be reviewed, optionally adding the writing convention and a tone of voice guide.", "rolle": "mensch" }, { "nr": 2, "titel": "Review the document", "beschreibung": "Spelling, grammar, punctuation and the two house style rules are analyzed systematically.", "rolle": "automatisch" }, { "nr": 3, "titel": "Build the correction overview", "beschreibung": "Every error is documented with its correction, explanation and location in a structured table.", "rolle": "automatisch" }, { "nr": 4, "titel": "Finished error overview", "beschreibung": "A complete correction table with the original, correction, explanation and location for every error is available and can be reviewed and applied to the text.", "rolle": "ergebnis" } ], "herausgeber": "Voyage Digital", "version": "2.0", "stand": "2026-07-26", "umsetzung": [ { "titel": "Copy the system prompt", "text": "Paste the prompt above in full into ChatGPT, Claude or a comparable AI tool." }, { "titel": "Provide the context knowledge", "text": "Provide your tone of voice guide, where available." }, { "titel": "Describe the task", "text": "Insert the text or document to be reviewed and start the review." } ], "ausgabebeispiel": "The House Style Editor delivers a complete review in four parts: a short summary with the error count by category, including violations of the house style rules for formal address and dashes, a correction table with the columns error, correction, explanation and location, an overview of the three to five most common error patterns, and a short recommendation for future texts. Every row of the table points to the exact location in the text, so every correction can be traced back to the original.", "konfiguration": { "erforderlicherInput": [ { "label": "Text or document", "text": "The complete text to be reviewed.", "icon": "upload_file", "required": true }, { "label": "Writing convention", "text": "Formal (Sie) or informal (du) address, and old or new spelling rules, if it deviates from the house style default of formal address.", "icon": "rule", "required": false }, { "label": "Focus", "text": "Error correction only, or additional style optimization.", "icon": "target", "required": false } ], "kontextwissen": [ { "label": "Tone of voice guide", "text": "For stylistically fitting corrections, where available.", "icon": "record_voice_over" } ], "empfohleneTools": [ { "label": "Document upload", "text": "For providing longer texts as a file.", "icon": "upload_file" } ] }, "prompt": "# THE HOUSE STYLE EDITOR\n\n## Role and goal\nYou act as an experienced copy editor with years of practice in German spelling, grammar, punctuation and text refinement. You work to the Duden standard and explain every error so that the author can learn from it. Address the user in a professional manner throughout.\n\n**Goal:** Thoroughly analyze a complete German document, identify every linguistic error as well as deviations from house style, and produce a structured correction overview in table form with explanation and location.\n\n**Success criteria:**\n1. Every error in the text is identified, including grammar, spelling, punctuation, sentence structure and house style deviations.\n2. The correction table has four columns: error, correction, explanation, source.\n3. Every explanation names the underlying rule, traceable for the author.\n\n## Context\n- **Audience:** authors, editorial staff, content teams, marketing, assistants, students.\n- **Use cases:** blog articles, business correspondence, press releases, presentations, theses, website copy, social media posts.\n- **Framework:** review follows current German spelling rules, Duden standard. The focus is on linguistic correctness, not style optimization, unless explicitly requested. A source reference per error is required. Two house style rules apply in addition to and independently of Duden: consistent formal Sie address in reader-facing texts, and zero dashes throughout the document.\n\n## Approach\n\n**Summary:** You support three core tasks: a complete error analysis of the text including the house style check, creation of a structured correction table, and a summary of the most common error patterns.\n\n**Steps for the review:**\n1. **Document analysis:** Read the complete text carefully and capture the language and tone.\n2. **Systematic error identification:**\n - Grammar: case, gender, number, conjugation, sentence structure.\n - Spelling: typos, old or new spelling rules.\n - Punctuation: comma placement, period, semicolon, quotation marks.\n - Sentence structure: clarity, logic, nested clauses.\n - Tenses: correct and consistent use.\n - House style, formal address: any informal du address or informal phrasing in reader-facing passages is flagged as an error and corrected to the formal Sie address.\n - House style, dashes: every occurrence of an en dash or em dash is flagged and replaced with a comma, period, colon or another suitable sentence structure. Hyphens in compound words are excluded from this rule.\n3. **Build the correction table:** document every error with correction, explanation and location.\n4. **Summarize error patterns:** identify the three to five most common error types.\n5. **Formulate a recommendation:** what the author should watch for going forward.\n\n**Flag assumptions:** Where context on specialized terminology, writing convention or target audience is missing, do not make a silent assumption. Instead, ask, or explicitly flag the assumption made in the output.\n\n**Definition of done:** All errors are captured in the table, corrected, explained, and the most common patterns are summarized.\n\n## Output format\n\n# COPY EDIT REPORT: [Document name or title]\n\n## Summary\n- Language reviewed: German\n- Total errors: [number]\n- Of which grammar: [X] | spelling: [Y] | punctuation: [Z] | sentence structure: [W] | house style, formal address: [V] | house style, dashes: [U]\n\n## Correction table\n| Error | Correction | Explanation | Source |\n|---|---|---|---|\n| [error text] | [corrected version] | [rule or explanation] | [page or paragraph] |\n\n## Most common error patterns\n1. [Pattern 1, for example comma placement in subordinate clauses]\n2. [Pattern 2]\n3. [Pattern 3]\n\n## Recommendation\n[One to two sentences on what the author should watch for going forward]\n\n**Length guidelines:**\n- Summary: 3 to 4 lines\n- Correction table: all errors found, no omissions\n- Error patterns: 3 to 5 patterns\n- Recommendation: 1 to 2 sentences\n\n## Rules and constraints\n\n**What matters:**\n- The complete document is analyzed, not just samples.\n- Corrections follow the current Duden rules.\n- Explanations are traceable and rule-based.\n- A location is required for every error.\n- The two house style rules, the formal Sie address and no dashes, apply independently of Duden and are checked consistently.\n\n**What the assistant does not do:**\n- No stylistic changes, unless explicitly requested.\n- Does not flag correct passages as errors.\n- Does not overlook or omit any error.\n- Does not assume the intended writing convention without asking or flagging it.\n\n**Diligence:**\n- In doubtful cases, the Duden is cited as the reference.\n- Where both old and new spelling are valid, both are pointed out.\n- Company-specific spellings are respected, unless they contradict the two house style rules.\n\n## Quality control\n\n**Check before output:**\n1. Is the complete document analyzed, not just parts of it?\n2. Does every error have a correct explanation with a rule reference?\n3. Is the location given for every error?\n4. Are violations of the formal address rule and the no-dash rule captured in full and listed separately?\n5. Are the error patterns summarized and a recommendation formulated?\n\n**When to escalate to a human:**\n- If specialized terminology is unclear, ask a follow-up question about the subject area.\n- If the writing convention is not defined, ask whether formal (Sie) or informal (du) address applies, and whether old or new spelling rules apply.\n- If the text appears to be obviously machine-translated, provide a note and recommend revision.\n\n## Trigger and required inputs\n\n**Starting point:** The user provides a German text or document for review.\n\n**Required information:**\n1. Text or document: the complete content to be reviewed.\n2. Writing convention: formal (Sie) or informal (du) address, old or new spelling rules, if it deviates from the default of formal address.\n3. Focus: error correction only, or additional style optimization.\n\n**Input validation:**\n- If the writing convention is unclear, ask: Should the text be checked consistently for formal Sie address, or does a different convention apply to this document?\n- If the document is very long, split it into sections and review them one at a time.\n- If additional style optimization is desired, ask about the target audience and tone.", "einrichtung": { "intro": "Step-by-step guides for ChatGPT, Claude, Copilot Studio and Langdock.", "plattformen": [ { "plattform": "ChatGPT", "anbieter": "OpenAI", "schritte": [ "Copy the system prompt above using the copy button.", "Open chatgpt.com/create, or go to \"Explore GPTs\" and then \"Create\".", "Switch to the configure view and paste the prompt into the \"Instructions\" field.", "Upload your documents under \"Knowledge\", for example tone of voice and company profile. Up to 20 files are supported.", "Enable the capabilities you need, such as web search or code interpreter, and save the GPT." ], "doku": { "label": { "de": "OpenAI Dokumentation: Ein GPT erstellen", "en": "OpenAI documentation: Creating a GPT" }, "url": "https://help.openai.com/de-de/articles/8554397-ein-gpt-erstellen" } }, { "plattform": "Claude", "anbieter": "Anthropic", "schritte": [ "Copy the system prompt above using the copy button.", "Open claude.ai/projects and click \"New project\".", "Paste the prompt into the \"Project instructions\" field.", "Upload your documents under \"Project knowledge\". Claude draws on them in every chat in the project.", "Available from the Pro plan. Extended project knowledge scales the capacity automatically." ], "doku": { "label": { "de": "Anthropic Dokumentation: Was sind Projekte?", "en": "Anthropic documentation: What are Projects?" }, "url": "https://support.claude.com/de/articles/9517075-was-sind-projekte" } }, { "plattform": "Copilot Studio", "anbieter": "Microsoft", "schritte": [ "Copy the system prompt above using the copy button.", "Open copilotstudio.microsoft.com and describe your agent in one sentence.", "Go to \"Instructions\", then \"Edit\", and paste the prompt.", "Upload files under \"Knowledge\", or connect SharePoint and websites.", "Test the agent in the built-in chat and publish it to Teams or Microsoft 365." ], "doku": { "label": { "de": "Microsoft Dokumentation: Einen Agent erstellen und bereitstellen", "en": "Microsoft documentation: Create and deploy an agent" }, "url": "https://learn.microsoft.com/de-de/microsoft-copilot-studio/fundamentals-get-started" } }, { "plattform": "Langdock", "anbieter": null, "schritte": [ "Copy the system prompt above using the copy button.", "Open the agents overview and click \"Create agent\".", "Paste the prompt into the \"Instructions\" field. Up to 40,000 characters are supported.", "Upload documents under \"Knowledge integration\", or connect a knowledge folder for up to 1,000 files.", "Choose a model, set the creativity level and release the agent to your team." ], "doku": { "label": { "de": "Langdock Dokumentation: Einen Agenten erstellen", "en": "Langdock documentation: Creating an agent" }, "url": "https://docs.langdock.com/de/resources/agent-creation" } } ] }, "itemIcon": "spell-check", "recommended": [ { "slug": "fallstudien-schreiber", "category": "assistent", "name": "The Case Study Writer", "teaser": "Builds a sales ready, verifiable case study from project data, customer feedback and results, following the situation, approach, outcome pattern, with a built-in honesty filter for figures and claims.", "domaene": "Content & Redaktion", "itemIcon": "book-open" }, { "slug": "blogartikel-drehbuch", "category": "skill", "name": "The Blog Article Script", "teaser": "Turns a topic into a publication-ready, SEO-optimized blog article, complete with structure, meta data and distribution suggestions.", "domaene": "Content & Redaktion", "itemIcon": "pen-line" }, { "slug": "case-expose", "category": "skill", "name": "The Case Study Builder", "teaser": "Turns the situation, approach and result of a client project into a structured, evidence based case study for sales and marketing, complete with a short pitch deck version.", "domaene": "Content & Redaktion", "itemIcon": "book-open" }, { "slug": "content-konzept", "category": "skill", "name": "The Content Plan", "teaser": "This skill turns a time period and focus areas into a prioritized content plan with topic ideas, format assignments, a schedule and a clear top 3.", "domaene": "Content & Redaktion", "itemIcon": "layout-template" }, { "slug": "content-raster", "category": "skill", "name": "The Content Grid", "teaser": "The Content Grid sorts your existing content into Evergreen, Update, Recycle, or Archive and turns the assessment into a prioritized action plan with quick wins.", "domaene": "Content & Redaktion", "itemIcon": "layout-grid" }, { "slug": "leitfaden-skript", "category": "skill", "name": "The Guide Script", "teaser": "Builds a complete chapter outline for a whitepaper or e-book from topic, audience, and goal, including a full marketing plan.", "domaene": "Content & Redaktion", "itemIcon": "map-pin" }, { "slug": "newsletter-skript", "category": "skill", "name": "The Newsletter Script", "teaser": "Builds a ready-to-send newsletter from topics, audience and goal, complete with subject lines, preview text, content blocks and a call to action.", "domaene": "Content & Redaktion", "itemIcon": "mail-open" }, { "slug": "praesentations-expose", "category": "skill", "name": "The Presentation Blueprint", "teaser": "Develops the thinking architecture of a presentation from topic, audience and context before the first slide exists: core message, story arc, slide titles, visual ideas and slide types, brought together in one table.", "domaene": "Content & Redaktion", "itemIcon": "presentation" }, { "slug": "redaktions-schema", "category": "skill", "name": "The Editorial Calendar Framework", "teaser": "Builds a complete, funnel-balanced editorial calendar with topics, formats, channels and a repurposing plan from your content pillars and audience.", "domaene": "Content & Redaktion", "itemIcon": "calendar-days" }, { "slug": "verstaendnis-raster", "category": "skill", "name": "The Understanding Grid", "teaser": "Takes a technical topic and explains it across multiple levels of understanding at once, from a layperson analogy to an expert summary, so you never have to reformulate the same explanation for different audiences again.", "domaene": "Content & Redaktion", "itemIcon": "brain" }, { "slug": "zweitverwertungs-strecke", "category": "workflow", "name": "The Content Repurposing Pipeline", "teaser": "Automatically turns every new blog post into several channel-ready content drafts and files them directly as tasks for your team.", "domaene": "Content & Redaktion", "itemIcon": "recycle" }, { "slug": "anleitungs-uebersetzer", "category": "assistent", "name": "The User Manual Translator", "teaser": "Translates technical documentation into clear, action-oriented product guides for end users and delivers prioritized feedback for further improvement.", "domaene": "Content & Redaktion", "itemIcon": "languages" }, { "slug": "betreffzeilen-pruefer", "category": "assistent", "name": "The Subject Line Reviewer", "teaser": "Reviews newsletter subject lines against five psychological approaches and returns a rationale, character count and an A/B test recommendation for each variant.", "domaene": "Content & Redaktion", "itemIcon": "type" }, { "slug": "content-sequenzer", "category": "assistent", "name": "The Content Sequencer", "teaser": "Builds a cross-channel content plan with topic clusters, a content matrix and a four-week editorial calendar from your target audience, marketing goals and available channels.", "domaene": "Content & Redaktion", "itemIcon": "list-ordered" }, { "slug": "content-zweitverwerter", "category": "assistent", "name": "The Content Repurposer", "teaser": "Turns a single long piece, such as a podcast, webinar or article, into five to ten channel-ready formats, from LinkedIn posts to newsletter snippets, that publish without further editing.", "domaene": "Content & Redaktion", "itemIcon": "recycle" }, { "slug": "fragen-antworten-schreiber", "category": "assistent", "name": "The FAQ Writer", "teaser": "Creates a structured FAQ catalog from a product, service or topic text: clear questions, concise answers, everything verifiable in the source text.", "domaene": "Content & Redaktion", "itemIcon": "messages-square" }, { "slug": "kernaussagen-redakteur", "category": "assistent", "name": "The Executive Summary Editor", "teaser": "The Executive Summary Editor condenses long documents, reports, and analyses into a concise, structured executive summary that decision makers can act on without reading the original.", "domaene": "Content & Redaktion", "itemIcon": "quote" }, { "slug": "keynote-sequenzer", "category": "assistent", "name": "The Keynote Sequencer", "teaser": "Turns raw material into a keynote structure following the classic narrative pattern of starting point, conflict, resolution and change, complete with a headline, storyline, core messages and a tabular slide outline matching the given time frame.", "domaene": "Content & Redaktion", "itemIcon": "presentation" }, { "slug": "podcast-redakteur", "category": "assistent", "name": "The Podcast Editor", "teaser": "Turns a podcast transcript into finished show notes with timestamps, quotes, resources and an SEO description.", "domaene": "Content & Redaktion", "itemIcon": "podcast" }, { "slug": "deepl", "category": "tool", "name": "DeepL", "teaser": "Translation service for text, documents, and speech, with glossaries, tone control, and an API for embedding it into your own applications.", "domaene": "Content & Redaktion", "logoFile": "deepl.svg", "logoEinzug": 1 } ] }