From d96113a4668c4c996b390bd8d1b57798c4c57dfd Mon Sep 17 00:00:00 2001 From: Paulo Castellano Date: Thu, 2 Jul 2026 19:50:20 -0300 Subject: [PATCH] prompts(humanizer): enforce the no-dash rule with a final-check output gate MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Reinforcement kept, but placed where it bites: a self-verification gate right before the JSON output ('scan for — and –, rewrite until zero remain') instead of restating the rule as a checklist step among general rewrite techniques. The strengthened catalog entry stays as the diagnostic 'what to remove' source. --- resources/views/prompts/post_content/humanizer.blade.php | 2 ++ 1 file changed, 2 insertions(+) diff --git a/resources/views/prompts/post_content/humanizer.blade.php b/resources/views/prompts/post_content/humanizer.blade.php index f9943f41..38cf8d2f 100644 --- a/resources/views/prompts/post_content/humanizer.blade.php +++ b/resources/views/prompts/post_content/humanizer.blade.php @@ -96,4 +96,6 @@ For single-post input: humanize the `content` field. @endif +FINAL CHECK before replying: scan every text field of your JSON output for em dash (—) and en dash (–) characters. If even one remains, rewrite that sentence using a comma, parentheses, a colon, or two separate sentences, until none are left. A response that still contains a — or – is a failed response. Return your answer only after zero remain. + Reply with the JSON object only, no preamble.