Skip to content

feat(prompts): make 'no em/en dashes' an explicit rule in the content prompts#145

Open
dantaspaulo wants to merge 1 commit into
trypostit:mainfrom
dantaspaulo:fix/prompts-no-em-dash
Open

feat(prompts): make 'no em/en dashes' an explicit rule in the content prompts#145
dantaspaulo wants to merge 1 commit into
trypostit:mainfrom
dantaspaulo:fix/prompts-no-em-dash

Conversation

@dantaspaulo

Copy link
Copy Markdown

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

  • generator — explicit rule to never use em/en dashes: rewrite with a comma,
    parentheses, a colon, or two separate sentences. Regular hyphens in compound
    words (e.g. "e-mail") stay fine.
  • humanizer — strengthen the existing em-dash note into a top-priority
    removal rule (also covering en dashes) 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.

… 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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant