Claude is my favorite AI at the moment and I use it to manage my own posting on LinkedIn, as well as creating content for clients of my LinkedIn agency BlueMethod.
Note: No, AI isn’t writing LinkedIn posts for us, but it helps us do it faster and better. Read on, you’ll see.
The default way most people use Claude for LinkedIn is to open a fresh chat, paste a topic, and ask for a post. The result is generic. It sounds like AI. They spend twenty minutes editing it back into something usable, or they give up and post the AI version anyway.
The fix is to set Claude up once, properly, so every chat starts with the context it needs to write in your voice. The setup takes about fifteen minutes. After that, every post you draft together gets faster and sounds more like you.
This isn’t the only way to do this, and at BlueMethod we don’t use the exact same process for any two clients. But what’s below is a solid starting point you can adapt.
Step 1: Create a Claude Project
Claude Projects let you store persistent instructions and reference files that apply to every chat inside that project. Without a project, you have to re-explain your voice, your audience, and your rules every time you start a new chat. With one, you do it once.
Go to Claude, click Projects, and create a new project. Name it something like “LinkedIn Content.”
Step 2: Write your project instructions
This is the part that does most of the work. Project instructions tell Claude who you are, who you’re writing for, and how you write. Here’s a template you can adapt. Replace the bracketed sections with your own information.
I am [your name and title], [what you do and for whom]. My LinkedIn audience is [describe them specifically]. I am not writing for [groups you are not targeting].
My LinkedIn content is managed in collaboration with [yourself, your assistant, your agency]. They draft posts, I approve or tweak them. Sometimes I draft them and they provide feedback or edit them and send them back to me for approval.
Voice rules. One thought per line, one thought per paragraph. My rhythm is short declarative lines, each on its own line. Use formal grammar as a default. Minimize contractions. Use complete sentences. [Add anything specific to your field, for example “Clinical register” or “Investor-friendly tone.”] Do not apply this so rigidly that it sounds stiff. Qualify broad claims with “often” and “many” rather than “most” or absolutes. [Add the things you are cautious about in your field.] Do not put specific statistics or timeframes in my mouth unless I give them to you. Avoid long checklists. Make one or two specific points instead. I do not want to sound like a [generic guru type in your field]. Business analogies work when speaking to executives, for example “no founder would run a company on lagging indicators alone.” Set up frames where these can emerge. Do not force them. Never open posts with “For years, I have told [audience]” or any first-person setup construction. State the claim directly. No CTAs unless I include one in my source material. Avoid the one-sentence-per-line LinkedIn formatting pattern. It reads as too obviously optimized. Closing questions should be simple enough for any reader to answer in one sentence, personal but not vulnerable, no wrong answer.
Formatting rules. Never use em-dashes. Never use hyphens as em-dash substitutes. Never use horizontal rules. Never use colons except before a bulleted or numbered list. Never use markdown unless I specifically ask for it. Plain text only.
[Stories or examples] in my posts are placeholders until I supply real ones. Flag any [story or example] in a draft as PLACEHOLDER so I know to replace it.
Edit suggestions. When suggesting edits to a draft, use this format. Put SEARCH on its own line, then the shortest unique string from the draft. Put REPLACE on its own line, then the new text. Only include a reason if the reasoning is not self-evident.
Output style. Give me one finished version, not options to choose from. If something requires a decision only I can make, ask. Otherwise make the call.
Adapt the bracketed pieces to your situation and paste the result into the Project Instructions field. You can also paste it all, brackets included, into Claude and say, “Help me create new project instructions, using this format, but adding in additional rules and instructions based on our previous interactions. Ask me questions where information or clarification is needed.”
Step 3: Upload reference files to Project Knowledge
Project Knowledge is a folder of documents Claude reads alongside every chat. The minimum useful set:
- A content bank. Every LinkedIn post you’ve written that represents the quality you want going forward, in one document. Export from a Google Doc, Notion page, or wherever you keep your drafts.
- An explainer document. A one-page document explaining what you do, who your customers or audience are, and what makes you different from competitors. Plain language, not marketing copy.
- A voice sample document. Three to five posts you’ve written yourself, unedited, labeled “This is my actual voice.” This is the single most valuable file you can upload. Claude calibrates faster from real writing than from any amount of instruction.
- Other writing samples. If you’ve written a book, attach the manuscript or PDF. If you’ve published articles, attach those. The more raw writing in your voice Claude can read, the faster the drafts start sounding like you.
Step 4: Add facts to Claude’s memory
Claude has a memory feature that persists across every chat, not just inside the project. Open a new Claude chat (inside or outside your project, it doesn’t matter) and paste this block in (including “Add these to memory”):
Add these to memory:
I am [name and title]. My LinkedIn audience is [audience]. My name displays as [display name] but my legal name is [legal name, if different]. Never use em-dashes in anything you write for me. Do not add statistics or timeframes to my writing unless I provide them. Do not add CTAs to my LinkedIn posts unless I include one in the source material.
Memory captures things you want Claude to remember everywhere. Project instructions capture things specific to one type of work. The two sets of instructions work together and strengthen each other where they overlap.
Step 5: Build a library of prompts you reuse
The same five or six prompts cover most LinkedIn writing. Save them in a notes app or Google doc and copy them in when you need them.
Turn a thought into a post.
I want to write a LinkedIn post about [TOPIC]. The point I want to make is [YOUR POINT IN ONE SENTENCE]. Draft one post in my voice using the rules in the project instructions. Include a closing question. Keep it under 1,500 characters. Flag any [story or example] as PLACEHOLDER.
Fix a post that feels off.
Here’s a draft. Something is off but I can’t name it. Tell me what’s wrong in one or two sentences, then give me a revised version. [PASTE DRAFT]
Generate hooks for a topic.
Give me five different opening lines for a LinkedIn post about [TOPIC]. Each hook should either create tension, present a surprising number I can verify, or state a contrarian claim. No setup constructions. State the claim directly. No em-dashes.
Turn an interaction into a post.
I had an interaction with a [client, customer, colleague] today. Here’s what happened. [DESCRIBE IT IN WHATEVER ORDER IT COMES OUT]. Turn this into a LinkedIn post in my voice. Protect their privacy by changing identifying details. Don’t invent any factual claims I didn’t tell you. End with a question my audience can answer in one sentence.
Repurpose a post into something new.
Here’s a post that performed well. [PASTE POST]. Give me three ways to revisit this theme from a different angle so I can post on the same topic again in a few weeks without repeating myself.
Content bank review.
Review my content bank and tell me which topics I’m overusing, which topics in my Genius Zone I’m not covering enough, and what patterns in my strongest posts I should do more of. Be specific. Reference individual posts.
Reverse engineer a post you admire.
Here’s a LinkedIn post from someone in my space that I thought was excellent. [PASTE POST]. Don’t copy it. Analyze what works structurally, what hook technique is used, and what makes the closing question effective. Then suggest how I could apply one of those techniques to a post about [MY TOPIC].
Step 6: Build habits that compound
- Keep one long-running chat per week. Instead of starting fresh every time, open one chat on Monday and keep using it all week. Context compounds. Past a week, chats start to slow down as the context fills.
- Voice-dictate rough thoughts. Open the Claude mobile app, tap the microphone, and ramble for two minutes about a topic, an interaction, or an idea. Claude will turn it into a clean draft. Faster than typing and it captures your natural speech patterns.
- Flag what you change and why. When you edit something Claude drafted, whether a single word swap or a full rewrite, paste both versions back and say “I changed X to Y because Z.” That feedback loop is how voice calibration happens, and over time Claude learns your voice without you having to describe it. This may take slightly more time when you’re getting started, but will save you a lot of time in the long run.
What not to use Claude for
Don’t use Claude to post directly to LinkedIn. Posting stays with you or your team.
Don’t use Claude to invent stories. Placeholders only, replaced with real ones by you.
Don’t use Claude to write claims you haven’t verified. You are the authority. Claude is a writing tool.
If you ever feel something is off, or doubt something Claude has inserted based on research it did, bring it up. I always ask Claude to quadruple check itself when it gives me a statistic or figure. And then I still go and look it up myself. Trust but verify. Or just verify.
The shortcut
If you’d rather skip the setup and have us run your LinkedIn presence end to end, that’s what BlueMethod does. We build the project, train Claude on your voice using your existing writing, draft posts for your approval, and run the publishing schedule. If you send us rough notes, a thought, or an idea, we turn it into a finished post in your voice. The methodology in this post is what we deliver, but built around your specific business, audience, and voice instead of a template.
If you want the deeper book on the LinkedIn fundamentals underneath all of this, my book 60 Days to LinkedIn Mastery covers profile, connections, and content in 60 short chapters.
Leave a Reply