prompts(humanizer): enforce the no-dash rule with a final-check output gate
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.
This commit is contained in:
parent
1d693e3227
commit
d96113a466
1 changed files with 2 additions and 0 deletions
|
|
@ -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.
|
||||
|
|
|
|||
Loading…
Reference in a new issue