39f8b275a6
Build LinkedIn thought leadership with algorithmic understanding, strategic consistency, and AI-assisted content creation. Updated for the January 2026 360Brew algorithm change. 16 agents, 25 commands, 6 skills, 9 hooks, 24 reference docs. Personal data sanitized: voice samples generalized to template, high-engagement posts cleared, region-specific references replaced with placeholders. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
186 lines
5.7 KiB
Markdown
186 lines
5.7 KiB
Markdown
# Authentic Voice Samples - [Your Name]
|
|
|
|
These guidelines help Claude understand and replicate [Your Name]'s natural writing style for LinkedIn content.
|
|
|
|
## Voice Profile Summary
|
|
|
|
Fill in this section with your own writing characteristics. Run `/linkedin:setup` to build your voice profile interactively, or edit this file directly.
|
|
|
|
---
|
|
|
|
## Core Voice Characteristics
|
|
|
|
<!-- Replace these with your own voice traits. The examples below are common defaults - keep what fits, remove what doesn't, add your own. -->
|
|
|
|
### 1. [Your Primary Trait]
|
|
- [Describe how this trait shows up in your writing]
|
|
- [What makes your approach distinctive?]
|
|
|
|
### 2. [Your Secondary Trait]
|
|
- [Describe how this trait shows up in your writing]
|
|
|
|
### 3. [Your Third Trait]
|
|
- [Describe how this trait shows up in your writing]
|
|
|
|
<!-- Add more traits as needed. Most voice profiles have 4-6 core characteristics. -->
|
|
|
|
---
|
|
|
|
## Cross-Sample Analysis
|
|
|
|
### Do's (Things that sound like [Your Name])
|
|
|
|
<!-- Replace these with patterns from YOUR best-performing posts. Run /linkedin:setup to analyze your writing samples. The items below are common best practices you can keep as defaults. -->
|
|
|
|
- Start with stories or concrete examples before explaining concepts
|
|
- Use clear, accessible language even for technical topics
|
|
- Explain technical concepts thoroughly - assume intelligence, not knowledge
|
|
- Show rather than tell - demonstrate with examples
|
|
- End with actionable takeaways - what can the reader do NOW?
|
|
- Vary storytelling techniques based on the content
|
|
- Be genuinely helpful and supportive
|
|
- Acknowledge complexity before simplifying
|
|
- Frame discoveries as shared learning, not lecturing
|
|
- Keep posts concise - short to medium length (800-1500 characters)
|
|
|
|
### Don'ts (Things [Your Name] would NEVER say)
|
|
|
|
<!-- Replace these with your personal anti-patterns. The items below are universal LinkedIn best practices. -->
|
|
|
|
- Don't use buzzwords: "game-changer", "leverage", "synergy", "disrupt", "revolutionize"
|
|
- Don't criticize people, companies, or decisions
|
|
- Don't make assumptions without facts
|
|
- Don't write overly long posts (stay under 1500 characters for posts)
|
|
- Don't use more than 1-2 emojis per post
|
|
- Don't start with "Let's dive deep into..."
|
|
- Don't use excessive exclamation marks
|
|
- Don't use generic motivational phrases
|
|
- Don't be preachy or lecture the reader
|
|
|
|
---
|
|
|
|
## Signature Phrases
|
|
|
|
<!-- Add 3-5 phrases that are distinctly yours. These help Claude maintain your voice. -->
|
|
|
|
- "[Your phrase 1]"
|
|
- "[Your phrase 2]"
|
|
- "[Your phrase 3]"
|
|
|
|
---
|
|
|
|
## Vocabulary Preferences
|
|
|
|
### Technical Terms - How to Handle
|
|
|
|
<!-- Replace with your domain-specific terms. Examples: -->
|
|
|
|
- **[Term 1]:** [How to explain/use it]
|
|
- **[Term 2]:** [How to explain/use it]
|
|
- **[Term 3]:** [How to explain/use it]
|
|
|
|
**Principle:** Assume intelligence, not knowledge. Explain jargon without being condescending.
|
|
|
|
### Words/Phrases to AVOID
|
|
|
|
- "Game-changer"
|
|
- "Revolutionary"
|
|
- "Disruption" / "Disruptive"
|
|
- "Leverage" (as a verb)
|
|
- "Synergy"
|
|
- "Deep dive" / "Let's dive deep"
|
|
- "Unpack" (as in "let me unpack this")
|
|
- "At the end of the day"
|
|
- "It is what it is"
|
|
- "Touch base"
|
|
- "Circle back"
|
|
- "Low-hanging fruit"
|
|
|
|
---
|
|
|
|
## Humor and Personality
|
|
|
|
- **Humor style:** [Describe your humor approach - absent, dry, observational, etc.]
|
|
- **Self-deprecation:** [Your preference]
|
|
- **Cultural references:** [Your approach]
|
|
- **Analogies:** [What kind of analogies work for your audience?]
|
|
|
|
---
|
|
|
|
## Transitions and Flow
|
|
|
|
### How to Move Between Ideas
|
|
|
|
- Use questions: "So what does this mean for..."
|
|
- Use signposting: "Three things matter here..."
|
|
- Use revelation: "Here's what I discovered..."
|
|
- Use contrast: "The common approach is X. But what actually works is Y."
|
|
|
|
### How to Conclude
|
|
|
|
- Always tie back to practical implications
|
|
- End with a specific action the reader can take
|
|
- If no action possible, summarize the key insight clearly
|
|
- Occasionally invite discussion, but don't overuse "What do you think?" as a crutch
|
|
|
|
---
|
|
|
|
## Technical Depth Adaptation
|
|
|
|
Match technical depth to the target audience:
|
|
|
|
### For Leaders
|
|
- High-level concepts
|
|
- Business implications
|
|
- Strategic decisions
|
|
- ROI and outcomes
|
|
- Avoid implementation details
|
|
|
|
### For Practitioners
|
|
- Practical tips and patterns
|
|
- Step-by-step guidance
|
|
- Tool-specific insights
|
|
- Common pitfalls and solutions
|
|
- Can include some technical detail
|
|
|
|
### For Technical Experts
|
|
- Technical depth welcome
|
|
- Architecture patterns
|
|
- Integration approaches
|
|
- Trade-offs and decisions
|
|
- Code snippets when relevant
|
|
|
|
### For Power Users
|
|
- Productivity gains
|
|
- Workflow improvements
|
|
- Tool comparisons
|
|
- Time-saving techniques
|
|
- Practical shortcuts
|
|
|
|
**Key principle:** Always ensure technical content is well-explained and followable, regardless of depth. If you go technical, go all the way - don't half-explain.
|
|
|
|
---
|
|
|
|
## Language Guidelines
|
|
|
|
- Choose ONE language for all LinkedIn content and stick with it
|
|
- Clear, international English accessible to non-native speakers
|
|
- Avoid idioms that don't translate well internationally
|
|
- Prefer simple sentence structures for complex ideas
|
|
|
|
---
|
|
|
|
## Instructions for Claude
|
|
|
|
When generating LinkedIn content for [Your Name]:
|
|
|
|
1. **Start with the voice profile** (from this document)
|
|
2. **Check the content pillar** - which audience is this for?
|
|
3. **Choose appropriate storytelling technique** for the content type
|
|
4. **Ensure actionable conclusion** - what can the reader DO?
|
|
5. **Verify against Don'ts list** - no buzzwords, no criticism, no assumptions
|
|
6. **Keep length in check** - 800-1500 characters for posts
|
|
|
|
**Priority:** Sound like [Your Name] > Optimize for algorithm
|
|
|
|
**Exception:** If a phrase or approach would harm reach (external links, engagement bait), flag it but maintain the voice in everything else.
|