From 3a9ed2dfb3984b17ff80293216af14666f848c96 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Paulo=20S=C3=A9rgio=20Dantas?= Date: Wed, 1 Jul 2026 13:06:18 -0300 Subject: [PATCH] feat(prompts): make 'no em/en dashes' an explicit rule in the content prompts MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Em and en dashes (— –) are the most recognizable AI-tell in generated text. The generator had no rule against them, and the humanizer only mentioned them weakly. - generator: explicit rule to never use them (rewrite with a comma, parentheses, a colon, or two sentences; regular hyphens stay fine). - humanizer: strengthen the existing em-dash note into a top-priority removal rule and add it to the numbered rewrite checklist. - reviewer: always flag every em/en dash with a concrete replacement suggestion, as a hard rule rather than optional style. --- resources/views/prompts/post_content/generator.blade.php | 1 + resources/views/prompts/post_content/humanizer.blade.php | 5 +++-- resources/views/prompts/post_content/reviewer.blade.php | 1 + 3 files changed, 5 insertions(+), 2 deletions(-) diff --git a/resources/views/prompts/post_content/generator.blade.php b/resources/views/prompts/post_content/generator.blade.php index 0f1a2c8e..ec709199 100644 --- a/resources/views/prompts/post_content/generator.blade.php +++ b/resources/views/prompts/post_content/generator.blade.php @@ -22,6 +22,7 @@ - Avoid AI-clichés (testament, pivotal moment, emojis on every line, "Let's dive in"). - Keep paragraphs short. Vary sentence rhythm. - If the user mentions a specific platform, follow that platform's typical conventions. +- NEVER use em dashes or en dashes (— or –). They read as AI-written. Rewrite with a comma, parentheses, a colon, or two separate sentences. Regular hyphens in compound words (e.g. "e-mail") are fine. @if(!empty($target_chars)) CRITICAL — length for {{ $platform_label ?? 'the target platform' }}: diff --git a/resources/views/prompts/post_content/humanizer.blade.php b/resources/views/prompts/post_content/humanizer.blade.php index 68f063b1..8b4c7877 100644 --- a/resources/views/prompts/post_content/humanizer.blade.php +++ b/resources/views/prompts/post_content/humanizer.blade.php @@ -48,8 +48,8 @@ **False ranges:** "from X to Y" where X and Y aren't on a meaningful scale — just list them. -**Em dashes (—):** -LLMs overuse them. Most can be commas, periods, or parentheses. +**Em dashes and en dashes (top priority):** +The single most recognizable AI-tell. Remove EVERY one. Rewrite with a comma, parentheses, a colon, or split into two sentences. Regular hyphens in compound words (e.g. "e-mail") are fine. The final output must contain zero — and – characters. **Curly quotes:** Replace " " ' ' with straight " " ' '. @@ -85,6 +85,7 @@ 6. **Match the brand voice.** If brand voice traits were provided, mirror their rhythm and word choices. 7. **Preserve meaning.** The core message and any specific facts/numbers/claims stay intact. 8. **Match the original length roughly.** Don't dramatically expand or shrink the input — humanize, don't rewrite into a different post. +9. **Never leave em dashes or en dashes (— or –).** They are the most recognizable AI-tell. Remove them; rewrite with a comma, parentheses, a colon, or two separate sentences. Regular hyphens in compound words (e.g. "e-mail") are fine. ## Input you'll receive diff --git a/resources/views/prompts/post_content/reviewer.blade.php b/resources/views/prompts/post_content/reviewer.blade.php index efd28416..e270d708 100644 --- a/resources/views/prompts/post_content/reviewer.blade.php +++ b/resources/views/prompts/post_content/reviewer.blade.php @@ -16,4 +16,5 @@ - Each `reason` is a 1-line explanation in the output language. - If the text is fine, return an empty `suggestions` array. - Do NOT propose stylistic changes. ONLY grammar, spelling, and clarity. +- EXCEPTION: ALWAYS flag every em dash and en dash (— –) with a suggestion that replaces it (comma, parentheses, colon, or a period + new sentence). Removing em/en dashes is a hard rule, not optional style. - Maximum 8 suggestions per request. Prioritize the most important ones.