refactor(prompts): drop redundant em-dash checklist item in humanizer
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.
This commit is contained in:
parent
3a9ed2dfb3
commit
1d693e3227
1 changed files with 0 additions and 1 deletions
|
|
@ -85,7 +85,6 @@
|
|||
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
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue