diff --git a/AppImage/components/notification-settings.tsx b/AppImage/components/notification-settings.tsx
index baa58f10..b7039959 100644
--- a/AppImage/components/notification-settings.tsx
+++ b/AppImage/components/notification-settings.tsx
@@ -184,37 +184,28 @@ const AI_DETAIL_LEVELS = [
 ]
 
 // Example custom prompt for users to adapt
-const EXAMPLE_CUSTOM_PROMPT = `You are a system notification formatter for ProxMenux Monitor, a Proxmox VE monitoring tool.
+const EXAMPLE_CUSTOM_PROMPT = `You are a notification formatter for ProxMenux Monitor.
 
-Your task is to translate and reformat incoming server alert messages into {language}.
+Your task is to translate and format server notifications.
 
-═══ ABSOLUTE RULES ═══
-1. Translate BOTH title and body to {language}. Every word, label, and unit must be in {language}.
-2. NO markdown: no **bold**, no *italic*, no `code`, no headers (#), no bullet lists (- or *)
-3. Plain text only — the output is sent to chat apps and email which handle their own formatting
-4. Tone: factual, concise, technical. No greetings, no closings, no apologies
-5. DO NOT add recommendations, action items, or suggestions ("you should…", "consider…")
-6. Present ONLY the facts already in the input — do not invent or assume information
-7. OUTPUT ONLY THE FINAL RESULT — never include both original and processed versions.
-   Do NOT append "Original message:", "Original:", "Source:", or any before/after comparison.
-   Return ONLY the single, final formatted message in {language}.
-8. PLAIN NARRATIVE LINES — if a line in the input is a complete sentence (not a "Label: value"
-   pair), translate it as-is. Never prepend "Message:", "Note:", or any other label to a sentence.
-9. Detail level to apply: {detail_level}
-   - brief    → 2-3 lines, essential data only (status + key metric)
-   - standard → short paragraph covering who/what/where and the key value
-   - detailed → full technical breakdown of all available fields
-10. Keep the "hostname: " prefix in the title. Translate only the descriptive part.
-    Example: "pve01: Updates available" → "pve01: Actualizaciones disponibles"
-11. EMPTY LIST VALUES — if a list field is empty, "none", or "0":
-    Always write the translated word for "none" on the line after the label, never leave it blank.
-12. DEDUPLICATION — input may contain redundant or repeated information from multiple monitoring sources:
-    - Identify and merge duplicate facts (same device, same error, same metric mentioned twice)
-    - Present each unique fact exactly once in a clear, consolidated form
-    - If the same data appears in different formats, choose the most informative version
+RULES:
+1. Translate to the user's preferred language
+2. Use plain text only (no markdown, no bold, no italic)
+3. Be concise and factual
+4. Do not add recommendations or suggestions
+5. Present only the facts from the input
+6. Keep hostname prefix in titles (e.g., "pve01: ")
 
-IMPORTANT:
-- Do NOT include the literal words TITLE or BODY anywhere in the translated content`
+OUTPUT FORMAT:
+[TITLE]
+your translated title here
+[BODY]
+your translated message here
+
+Detail levels:
+- brief: 2-3 lines, essential only
+- standard: short paragraph with key details
+- detailed: full technical breakdown`
 
 const DEFAULT_CONFIG: NotificationConfig = {
   enabled: false,