Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
paulocastellano merged 5 commits into from
Jul 3, 2026
Merged

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

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
3a9ed2d
feat(prompts): make 'no em/en dashes' an explicit rule in the content…
dantaspaulo Jul 1, 2026
1d693e3
refactor(prompts): drop redundant em-dash checklist item in humanizer
paulocastellano Jul 2, 2026
d96113a
prompts(humanizer): enforce the no-dash rule with a final-check outpu…
paulocastellano Jul 2, 2026
2b845f8
Merge branch 'main' into fix/prompts-no-em-dash
paulocastellano Jul 2, 2026
66b7ef6
Merge branch 'main' into fix/prompts-no-em-dash
paulocastellano Jul 3, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions resources/views/prompts/post_content/generator.blade.php
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,6 +22,7 @@
- Avoid AI-clichés (testament, pivotal moment, emojis on every line, "Let's dive in").
- Keep paragraphs short. Vary sentence rhythm.
- If the user mentions a specific platform, follow that platform's typical conventions.
- NEVER use em dashes or en dashes (— or –). They read as AI-written. Rewrite with a comma, parentheses, a colon, or two separate sentences. Regular hyphens in compound words (e.g. "e-mail") are fine.
@if(!empty($target_chars))

CRITICAL — length for {{ $platform_label ?? 'the target platform' }}:
Expand Down
6 changes: 4 additions & 2 deletions resources/views/prompts/post_content/humanizer.blade.php
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -48,8 +48,8 @@
**False ranges:**
"from X to Y" where X and Y aren't on a meaningful scale — just list them.

**Em dashes (—):**
LLMs overuse them. Most can be commas, periods, or parentheses.
**Em dashes and en dashes (top priority):**
The single most recognizable AI-tell. Remove EVERY one. Rewrite with a comma, parentheses, a colon, or split into two sentences. Regular hyphens in compound words (e.g. "e-mail") are fine. The final output must contain zero — and – characters.

**Curly quotes:**
Replace " " ' ' with straight " " ' '.
Expand Down Expand Up @@ -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.
1 change: 1 addition & 0 deletions resources/views/prompts/post_content/reviewer.blade.php
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,4 +16,5 @@
- Each `reason` is a 1-line explanation in the output language.
- If the text is fine, return an empty `suggestions` array.
- Do NOT propose stylistic changes. ONLY grammar, spelling, and clarity.
- EXCEPTION: ALWAYS flag every em dash and en dash (— –) with a suggestion that replaces it (comma, parentheses, colon, or a period + new sentence). Removing em/en dashes is a hard rule, not optional style.
- Maximum 8 suggestions per request. Prioritize the most important ones.
Loading