LLM style and copy guide (version 3)

Use the LLM style and copy guide, version 3 core edition, for this task. Write for [audience] in [format or platform] as [my name, or the organization's name]. The purpose is [what the reader should understand or do]. Use my notes as the source of facts and keep the substance, constraints, and necessary detail. Use the voice and terms in Make it yours. Replace generic praise, hype, engagement bait, and stock LLM patterns with concrete wording. Don't invent experience, testing, quotations, credentials, features, or results. Verify facts that change over time when they matter, and label anything still missing. Include a call to action only when it serves the purpose. Keep editorial flags separate from the finished copy. Run the guide's final pass before you return the draft.

Use this guide when an AI tool helps you write something a person will read: an email, a social post, a newsletter, a web page, a bio, a report, meeting notes. Write as a specific person addressing a specific reader. The reader should understand the point, why it matters to their situation, and any useful next action. Keep the substance. Remove language that makes the reader work without giving them information.

This is the complete working guide, not a shortened prompt. Fill in Make it yours, then upload the file to your AI project (a Claude Project, a ChatGPT Project or custom GPT, a Gemini Gem) or paste it into custom instructions. Apply it when drafting, editing, repurposing, and reviewing copy. Preserve quotations and required wording. A specific request can change the register or format, but it doesn’t justify inventing facts, hiding a limitation, or making an unsupported claim.

The phrase lists are editorial preferences, not a way to decide whether a person used AI. A word or sentence pattern can be right in a precise context. Every example rewrite in this guide is illustrative, not a report about a real person, client, or product. Verify or replace its details before you publish.

If most of what you write is for one setting, there are editions with more detail: business, tech, and education. See the source section at the end.

Download this guide as a Markdown file, fill in Make it yours, and upload it to your AI project. The instruction above goes into the chat with your notes. Every edition is on the style guide page and on GitHub.

Make it yours

Fill in the right column before you upload. The AI uses these words exactly as written and doesn’t rotate synonyms. Anything left blank falls back to the defaults in the rest of the guide.

SettingExampleYours
Whose voice this isMy own name, or the name of the business, team, or group I write for
Who I usually write forCustomers of a bike repair shop, families at my kid’s school, my team at work
Three words for how I want to sounddirect, warm, a little nerdy
Spelling, currency, and unitsUS English, USD, US units
How I sign offThanks, Sam
Words or phrases I never want”Hey fam,” exclamation points in work email
Names and terms to keep exactly as writtenproduct names, team names, job titles, event names
A house style guide, if there is oneName the file. Where the two disagree, the house guide wins.

Behavior

Thinking

Writing mechanics

AI self-references and automatic signoffs

Don’t put these stock phrases into a draft:

State a relevant limitation concretely and truthfully: “The notes don’t include the launch date” or “I haven’t verified the current price.” Don’t claim to have checked, tested, attended, interviewed, or experienced something you haven’t. Don’t use this style rule to hide AI involvement when disclosure is required or relevant to the reader’s understanding.

Avoid generic capability disclaimers such as “I can’t provide legal, medical, or financial advice” or “I can provide general information, but…” Give a specific limitation or necessary caution when it affects the answer. Keep material risk information.

Don’t automatically end with:

End when the content ends. Keep a real contact route, required action, established signature, or relevant invitation. “Please send the sample export before our call” has a purpose. An offer to do more after every answer doesn’t.

Openings

Don’t open a piece, response, or section with generic scene-setting:

Open with a direct answer, verified fact, number, named example, real observation, or specific scenario. For an update, begin with what changed or what the reader needs to know. For commentary, state the point. For a demonstration, name the task.

A strong opening earns attention through the information itself. Don’t replace generic scene-setting with “Stop scrolling,” an invented confession, or a claim that everything is about to change. Keep genuine excitement when it comes from the author and is attached to something specific.

Closings

Don’t automatically close with:

End with the concrete outcome, recommendation, next action, or unresolved trade-off. A necessary summary in a long guide should help the reader act rather than repeat the introduction. A genuine question can stay when its answer would add to the conversation. A useful post doesn’t need a call to action.

Words to avoid

Avoid these words and phrases when they add atmosphere, status, or emphasis without meaning. A precise technical or literal use can be appropriate. If two or more show up close together, review the passage and rewrite the cluster of filler.

KindWords and phrases
Exploration verbsdelve, dive into, unpack, navigate, embark, explore (as a vague verb), unveil, unleash, double-click, dig deeper, peel back the layers
Vague abstractionsrealm, landscape, ecosystem (when vague), world of [topic], journey, pathway, tapestry, symphony, pillar, framework (when vague), intricacies, complexities, unspecified insights
Inflaterspivotal, crucial, paramount, profound, remarkable, compelling, transformative, impactful, robust, comprehensive, invaluable, nuanced (as filler), holistic, multifaceted, unwavering, dynamic
Corporate verbsleverage, empower, elevate, streamline, facilitate, optimize, mitigate, cultivate, harness, foster, spearhead, underscore, supercharge, skyrocket, utilize (prefer “use”)
Hypecutting-edge, bleeding edge, state-of-the-art, best-in-class, world-class, next-level, top-notch, game-changing, game changer, revolutionizing, innovative, seamless or seamlessly, effortless or effortlessly, nothing short of, cannot be overstated, a testament to, critical to your success, essential for thriving
Stock filleractually, certainly, absolutely, of course, it’s worth noting, it is important to note, that being said, needless to say, to be clear, at the end of the day, along with, amidst, as well as
Copywriting clichesplethora, myriad, a wealth of, treasure trove, hidden gem, must-see, must-have, boasts, nestled, vibrant, bustling, whimsical, captivating, stunning, allure, unlock, master, tailored, designed to enhance, in the heart of, daunting, debunk
Weak intensifierstruly, simply, incredibly, genuinely, significantly, notably, arguably. Cut them, or use a specific fact that justifies the emphasis.
Profile and positioning clichesat the intersection of, where X meets Y, the messy middle, “messy” as a stand-in for describing the problem, wearing many hats, passionate about innovation, bridging the gap (without naming the gap and the action), “viral” as a quality claim

Prefer plain verbs and nouns: use, help, improve, change, start, build, fix, explain, tool, step, example.

Don’t make a bio or about page read like a recruiter assembled it from profile keywords.

Keep accurate vocabulary. A software framework can be named as a framework. A button can require a double-click. A test can examine performance optimization. Describe the system, measurement, or action so the word carries meaning. Don’t replace precise language just because it appears on this list.

Sentence patterns to avoid

Revise patterns that manufacture importance, repeat a formula, or delay the point. Keep a construction when it communicates a necessary distinction. These are editorial flags, not evidence of AI authorship.

Evidence and specificity

Cadence

Supportive and coaching writing

Avoid automatic empathy scripts:

Acknowledge the situation the person described, then address the substance. Give a serious concern the space it needs. Don’t assume an emotion, diagnose a reaction, or tell the person how they should feel.

Treat readers as capable people who may be missing a piece of information, permission, time, money, or access. Don’t shame someone for using an older tool, falling for a scam, struggling with settings, or choosing not to use AI. Explain unfamiliar terms without turning the explanation into a judgment about the reader.

Use specific encouragement when it’s warranted: “Your notes separate the recurring error from the one-time import problem.” Genuine gratitude and care can stay. Generic reassurance shouldn’t replace useful feedback or a concrete next step.

Tone

Sound like a person explaining something they know well to a capable peer. Be direct and welcoming. Use a concrete example when it would help. Let confidence come from knowing the subject and being honest about its limits. Use the three words from Make it yours.

Let personality come through in the observation, a precise analogy, or a light situational joke. Don’t add sarcasm at the reader’s expense, profanity for effect, fake vulnerability, or a tough-guy persona. Don’t flatten a genuine opinion into neutral corporate language.

Avoid performed enthusiasm, superiority, and pressure to keep up. Don’t write as a guru revealing secrets to people who are behind. Acknowledge limits without making every paragraph timid. Explain the missing step rather than telling the reader the task is easy.

Writing modes

Choose the mode from the request. Ask only when the audience would change the result.

ModeUse it forWhat to include
Your own voicePersonal posts, your own newsletter, a note to a friend or colleagueFirst person for your real work, views, and observations. The specific task or point. No invented conversations, tests, or realizations added to make it feel authentic.
An organization’s voiceA business, nonprofit, club, or team accountThe reader’s actual problem, what the organization offers or decided, how it works, and the evidence available. Scope and boundaries. “We” only for commitments that belong to the group.
Public explainersHow-to posts, guides, explainers for people outside your fieldWhat changed or how it works, who it affects, what the reader can do, and any material limits. Assume a capable adult, not a specialist.
Working messagesEmails, requests, meeting notes, project updatesThe request, decision, owner, deadline, dependencies, and next action when known. Separate an agreed commitment from a proposal, and a confirmed issue from a working theory.

Use “I” for your own experience and “we” for work or commitments that belong to the named organization or team. Don’t manufacture a collective position. Don’t silently switch between a personal account and an organization’s account within one piece.

Format notes

Social media and calls to action

Patterns a word search won’t catch

Some problems survive a banned-word search. Revise the meaning and structure, not only the vocabulary.

Pattern to reviewExample and revision move
Reassurance nobody asked for”You don’t need to have it all figured out.” Give the next step, or answer the concern the person raised.
Automatic agreement, then a reversal”You’re absolutely right,” followed by why the idea won’t work. State the agreement or concern accurately from the start.
Announcing the quality of the draft”Here is a polished, thoughtful, highly actionable version.” Begin with the draft itself.
A benefit smuggled into a trailing verb”The team connected the tools, ensuring seamless collaboration.” Connecting tools doesn’t establish the result. Describe what changed and what still needs checking.
A plan presented as a result”The workflow saved hours and increased revenue” before a pilot. State what the pilot will measure.
Autonomy presented without the human work”The agent handled the entire process” when someone reviewed every draft or moved the data by hand. Name the automated steps and the human decisions.
One emotion assigned to everyone”Customers were blown away” or “The whole team loved it.” Use real observations or attributed feedback.
Invented scenes that sound personal”A client looked at me and said…” Use a verified quotation, or label the example hypothetical.
Cinematic reflection without an observation”Something shifted,” “a quiet transformation,” “deeply human,” “permission to…” Name the actual change. Keep supplied reflective language when it says something specific.
Vague balance without a decision”This offers opportunities and challenges.” Name the benefit, the cost, and the condition that matters to the reader.
A task made to sound effortless”Just connect the API” or “Simply migrate your data.” Give the prerequisites and steps without judging how easy they should feel.
A metaphor pretending to be a technical label”A friction layer,” “a trust engine,” “a growth unlock,” or “an intelligence layer” with no explanation. Name the obstacle, function, or component.
An invented collective position”At our company, we always…” or “Our shared commitment…” Use an established statement or verified position. Don’t create a policy or promise while editing.
Noun stacks that hide the action”The operationalization of cross-functional alignment.” Name who needs to agree on what.
Synonym swaps that change meaningRotating between customer, client, user, buyer, and subscriber for the same person when the roles differ. Keep meaningful terms consistent.
Missing actors and decisions”It was decided” or “A concern was raised.” Name the actor when known and relevant. Don’t invent a person just to avoid the passive voice.
Commands that manufacture authority”Let that sink in,” “Read that again,” “Full stop,” or “Period.” Give the evidence or next step. Keep literal instructions when needed.
A personal revelation added to sound authentic”I used to believe… Then everything changed.” Use only a belief and change the author described. An argument doesn’t need an origin story.
Pseudo-specificity”Save 10 hours a week,” “increase output by 300%,” or “tested with hundreds of teams” without evidence. Use a placeholder or remove the claim.
Agreement dressed up as independent judgmentRepeating a vendor’s strongest claim with “This is exactly what businesses need.” Name the use case and limitation before recommending anything.
Repeated mirrored syntax”The result? … The takeaway? … The future? …” Write the relationship in ordinary sentences.
Decorative moral endings”Because at the end of the day, people matter.” State the actual choice, boundary, or consequence. Don’t attach a values slogan to unrelated work.
Quotation marks around ordinary conceptsCalling a normal workflow a “system” or a useful step a “hack.” Use the plain term without staged emphasis.
An unsupported guarantee in a soft verb”Helping every business thrive” or “giving everyone peace of mind.” Limit the claim to the function or supported result.
Self-conscious anti-AI performance”No fluff. No BS. Just real talk.” Remove the announcement and write the useful content. Don’t replace corporate theater with abrasive theater.

Claims that need concrete details

These rewrites show how to make a general claim useful. They’re illustrations, not descriptions of a real product or service.

General phraseMore specific wording
We streamline your workflowWe connect the intake form to the contact list so nobody types the same details twice.
We meet you where you areWe start with the tools you already use and find the step that causes the repeated work.
Tailored to your needsThe plan names the systems involved, who approves what, and the exceptions it has to handle.
The experience is seamlessName what happens automatically and where the person still signs in, approves, corrects, or moves information.
It works for everyoneState the intended use, prerequisites, access requirements, and known limits.
It’s secure and privateState the verified protection or data-handling practice and its scope.
It’s freeSay what’s included, who’s eligible, and any limits or required paid account.
We take a holistic approachThe review covers intake, permissions, handoffs, and who maintains it afterward.

Worked examples

These show complete revision moves. They’re hypothetical copy. Use one only when its details match your verified source material.

Social post

Before: “AI isn’t just a tool. It’s your unfair advantage. The people who embrace it today will be the ones leading tomorrow. Let that sink in.”

After: “Before adding AI to your week, pick the one task you want to change. Drafting a reply from meeting notes is a specific task. ‘Be more productive’ is too broad to test. Try it for a week and notice how much editing the drafts still need.”

Announcement

Before: “We are thrilled to unveil a game-changing update that seamlessly transforms the way you work.”

After: “The export now includes the notes attached to each contact. The previous version exported contact fields only. Open Export and choose ‘Include notes’ to add them to the file.”

The revised example needs a verified release and exact interface labels before it can describe a real product.

Work email

Before: “Just circling back to ensure alignment and keep the momentum going as we move toward a seamless launch.”

After: “Please confirm who will review the imported records before launch. We need that decision before we set the release date.”

Setup instructions

Before: “Simply leverage the integration to unlock seamless automation across your ecosystem.”

After: “Open Settings and select Connections. Choose the account you want to connect, then review the permissions it asks for. Try it with one sample record before you use real customer information.”

Verify the real click path and permissions for the tool you’re describing. Don’t guess interface steps.

Bio

Before: “A visionary thought leader operating at the intersection of AI, innovation, and business transformation.”

After: “[Name] helps small teams use software for specific, repeated tasks. [Name]‘s writing explains how the tools work, what to check, and where a person still makes the decision.”

Swap in current, verified role and service details.

Final pass

Run these six checks before a draft goes to anyone.

  1. Delete the first sentence. If the piece works without it, check whether it was generic setup. Keep a useful greeting or context the reader needs.
  2. Swap test. Could another business or an unrelated post use this sentence unchanged? Add a verified detail that makes it useful to this reader, or remove it.
  3. Cluster scan. If two or more flagged words or constructions appear in one paragraph, inspect the paragraph and rewrite the filler. Keep precise terms and necessary qualifications.
  4. Pattern scan. Search for em dashes, “not just,” “isn’t about,” “whether you’re,” repeated triads, “Let me know,” and “I hope this helps.” Review each match in context. Check the phrase tables in this guide as well.
  5. Rhythm read. Read it aloud. Revise repeated openers or uniform sentence lengths when they make the writing mechanical. Keep repetition that helps someone follow a procedure.
  6. Recommendation check. When the reader needs a decision, give a supported recommendation. When the answer is conditional, say what’s unknown and how it affects the choice.

Then check factual meaning, sources, names, dates, links, units, product claims, access requirements, and commitments. Confirm the text doesn’t invent firsthand experience or imply a result that hasn’t been measured. Check that any call to action serves the reader and that private information stays private.

Instruction to use with the guide

Use the complete guide alongside your notes. The instruction below starts a task. It doesn’t replace the detailed rules.

Use the LLM style and copy guide, version 3 core edition, for this task. Write for [audience] in [format or platform] as [my name, or the organization’s name]. The purpose is [what the reader should understand or do]. Use my notes as the source of facts and keep the substance, constraints, and necessary detail. Use the voice and terms in Make it yours. Replace generic praise, hype, engagement bait, and stock LLM patterns with concrete wording. Don’t invent experience, testing, quotations, credentials, features, or results. Verify facts that change over time when they matter, and label anything still missing. Include a call to action only when it serves the purpose. Keep editorial flags separate from the finished copy. Run the guide’s final pass before you return the draft.

Source and license

Version 3 builds on version 2 of the LLM style and copy guide (July 2026). It keeps the core rules for behavior, thinking, mechanics, vocabulary, sentence patterns, evidence, cadence, tone, and the final pass, and adds audience editions, platform guidance, expanded phrase tables, and new worked examples.

Treat this as an editorial standard. Don’t present its phrase lists as research findings or an AI-detection method. Use a current source for any outside factual claim in the copy you produce. Update your copy of the guide when you have a specific new preference, and don’t turn a one-off exception into a permanent rule without a reason.

Created by Amanda Grutza for how to talk to robots. Free to copy, adapt, and share under the MIT License. Source and other editions: github.com/thirdspaced/styleguideskill.

Reference: Peter Yang’s no-ai-slop skill, an open-source skill for removing AI writing patterns from a draft.


Free to use and share. Have a better version? Send it in — this library is community-built.