feat(prompts): make 'no em/en dashes' an explicit rule in the content prompts#145
Open
dantaspaulo wants to merge 4 commits into
Open
feat(prompts): make 'no em/en dashes' an explicit rule in the content prompts#145dantaspaulo wants to merge 4 commits into
dantaspaulo wants to merge 4 commits into
Conversation
… prompts 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.
The strengthened 'Em dashes and en dashes (top priority)' catalog entry is the single source of truth for the rule. The numbered 'How to rewrite' list holds general rewrite techniques, not specific tells, so restating the em-dash rule as item 9 duplicated the (stronger) catalog entry and broke the section's pattern.
…t 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.
paulocastellano
force-pushed
the
fix/prompts-no-em-dash
branch
from
c912041 to
d96113a
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Em and en dashes (— –) are the most recognizable AI-tell in generated text. The
generator prompt had no rule against them, and the humanizer only mentioned them
weakly ("LLMs overuse them. Most can be commas, periods, or parentheses.").
Change
parentheses, a colon, or two separate sentences. Regular hyphens in compound
words (e.g. "e-mail") stay fine.
removal rule (also covering en dashes) and add it to the numbered rewrite
checklist.
suggestion, as a hard rule rather than optional style.