Skip to content

Instantly share code, notes, and snippets.

@danbri
Created June 30, 2025 15:49
Show Gist options
  • Select an option

  • Save danbri/8c6dd505db38f91411e3efaf2e36d12a to your computer and use it in GitHub Desktop.

Select an option

Save danbri/8c6dd505db38f91411e3efaf2e36d12a to your computer and use it in GitHub Desktop.

`

Phrases and Patterns to Avoid in LLM Outputs

Language & Tone Issues

Avoid these phrases:

  • "serves/stands as a testament to"
  • "plays a vital/significant role"
  • "underscores its importance"
  • "continues to captivate"
  • "leaves a lasting impact"
  • "watershed moment"
  • "key turning point"
  • "rich cultural heritage/history"
  • "breathtaking," "must-visit," "must-see"
  • "stunning natural beauty"
  • "enduring/lasting legacy"
  • "rich cultural tapestry"

Avoid these patterns:

  • Starting responses with praise ("Great question!", "Fascinating topic!")
  • Excessive use of "moreover," "furthermore," "in addition," "on the other hand"
  • Phrases like "it's important to note/remember," "no discussion would be complete without"
  • Summary conclusions ("In summary," "In conclusion")
  • "Not only... but also" constructions
  • Collaborative language ("I hope this helps," "Certainly!", "Would you like...")

Formatting Issues to Avoid

  • Title case in section headings (use sentence case)
  • Excessive boldface for emphasis
  • Emoji decorations (πŸ”΄, πŸ“, etc.)
  • Markdown formatting (**, __, etc.) when not appropriate
  • Spaced em dashes ( β€” ) instead of unspaced (β€”)
  • Curly quotes/apostrophes ("..." ') instead of straight ("..." ')
  • Improper list formatting with bullet characters (β€’, -, –)

Content Patterns to Avoid

  • Over-emphasizing symbolism and cultural significance
  • Promotional/editorializing language
  • Restating/summarizing paragraph ideas at the end
  • Including meta-commentary about being an AI
  • Fill-in-the-blank templates ([Subject Name], [Your Name])
  • Date format inconsistencies (check regional conventions)

Technical Artifacts to Avoid

  • Code artifacts like citeturn0search0, contentReference[oaicite:0]
  • UTM tracking parameters (?utm_source=chatgpt.com)
  • Broken wikicode or improper template usage
  • "As of my last knowledge update" disclaimers
  • "As an AI language model" self-references

Best Practices

  • Write in clear, direct prose without excessive ornamentation
  • Use neutral, encyclopedic tone
  • Avoid redundant emphasis and symbolic interpretation
  • Skip flattery and get straight to the content
  • Maintain consistent formatting throughout
  • Use proper citation and reference formats for the platform
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment