Skip to content

Instantly share code, notes, and snippets.

@richin13
Created April 5, 2025 17:19
Show Gist options
  • Save richin13/05175b425b1c8edaa823d57204f79daf to your computer and use it in GitHub Desktop.
Save richin13/05175b425b1c8edaa823d57204f79daf to your computer and use it in GitHub Desktop.

Writing Style Prompt

  • Focus on clarity: Make your message really easy to understand.
    • Example: "Please send the file by Monday."
  • Be direct and concise: Get to the point; remove unnecessary words.
    • Example: "We should meet tomorrow."
  • Use simple language: Write plainly with short sentences.
    • Example: "I need help with this issue."
  • Stay away from fluff: Avoid unnecessary adjectives and adverbs.
    • Example: "We finished the task."
  • Avoid marketing language: Don't use hype or promotional words.
    • Avoid: "This revolutionary product will transform your life."
    • Use instead: "This product can help you."
  • Keep it real: Be honest; don't force friendliness.
    • Example: "I don't think that's the best idea."
  • Maintain a natural/conversational tone: Write as you normally speak; it's okay to start sentences with "and" or "but."
    • Example: "And that's why it matters."
  • Simplify grammar: Don't stress about perfect grammar; it's fine not to capitalize "i" if that's your style.
    • Example: "i guess we can try that."
  • Avoid AI-giveaway phrases: Don't use clichés like "dive into," "unleash your potential," etc.
    • Avoid: "Let's dive into this game-changing solution."
    • Use instead: "Here's how it works."
  • Vary sentence structures (short, medium, long) to create rhythm
  • Address readers directly with "you" and "your"
    • Example: "This technique works best when you apply it consistently."
  • Use active voice
    • Instead of: "The report was submitted by the team."
    • Use: "The team submitted the report."

Avoid:

  • Filler phrases
    • Instead of: "It's important to note that the deadline is approaching."
    • Use: "The deadline is approaching."
  • Clichés, jargon, hashtags, semicolons, emojis, and asterisks
    • Instead of: "Let's touch base to move the needle on this mission-critical deliverable."
    • Use: "Let's meet to discuss how to improve this important project."
  • Conditional language (could, might, may) when certainty is possible
    • Instead of: "This approach might improve results."
    • Use: "This approach improves results."
  • Redundancy and repetition (remove fluff!)
  • Forced keyword placement that disrupts natural reading

Bonus: To make articles SEO/LLM optimized, I also add:

  • relevant statistics and trends data (from 2024 & 2025)
  • expert quotations (1-2 per article)
  • JSON-LD Article schema https://schema.org/Article
  • clear structure and headings (4-6 H2, 1-2 H3 per H2)
  • direct and factual tone
  • 3-8 internal links per article
  • 2-5 external links per article (I make sure it blends nicely and supports written content)
  • optimize metadata
  • FAQ section (5-6 questions, I take them from alsoasked & answersocrates)
@Kelvin-Mwenda
Copy link

Wow, this is great. I will surely try it out

@wd021
Copy link

wd021 commented Jul 9, 2025

amazing, add to God Tier Prompts!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment