Platform Personas: Tweets, Slide Decks, and Output-Specific Files
Part 9 of 11 — A Practical Guide to Claude Setup
It’s day 9 and if you’ve stuck through this series until now, you’ve built some really cool integrations for setting up your Claude stack. You’ve built files for how you think and how you write. Now let’s talk about the outputs.
Different platforms have radically different constraints. A tweet is 280 characters. A board deck follows specific narrative logic. A conference keynote has a completely different story arc than an executive briefing. A workshop facilitation deck needs instructions large enough to read from across a table.
Asking Claude to write a tweet using your general writing file is like asking a novelist to write advertising piece for Facebook. The voice might be right. The output format will be all wrong.
The problem isn’t Claude. The problem is that “write like me” isn’t the same as “write like me for this platform, for this audience, in this format.“
Creating platform-specific files solve this problem.
The Persona File Concept
A platform file does something specific. It creates a constrained persona. Think of this as a version of Claude that knows your voice AND the specific rules and mechanics of a particular output format.
The key difference from your general writing file is that platform files are defined by constraints, not just voice. These are hard limits and non-negotiable rules. Format specifications that can’t be violated.
Think of each specialized file you’ve built in this series as a persona. CLAUDE_WRITING.md is your newsletter writer persona. CLAUDE_PROMPTS.md is your prompt architect persona.
Platform persona files extend that same logic to specific output formats.
CLAUDE_TWEETS.md is the version of you that shows up on X/Twitter. Tight. Direct. One idea per post. Built for scroll-stopping in a feed of noise.
For a tweet file, 280 characters is a hard ceiling, not a target. Output ONLY the tweet text. That means there is no preamble, no explanation, and no summary. This is one idea per tweet. To do this, you never start with “I think” or “In today’s world.”
CLAUDE_PRESENTATIONS.md is the version of you that shows up on a stage or in a board meeting. Visual, structured, and built for people who are half-listening and reading slides at the same time. For a deck file, you want to cover only one idea per slide. Slide title equals the point, not the topic. Data slides get annotated to show what to notice. Narrative structure determined before any slide is built.
Those constraints are what make the file useful. Without them, Claude will produce content that’s voice-accurate but format-wrong every time.
Building a Tweet File
A tweet file contains:
Core voice rules compressed for the format Not your full voice guide. A distillation. For most people: open with tension or a bold claim, short sentences, one idea, end with a question or declaration.
Hard rules The non-negotiables of things like character count, output format, and what to never include in a tweet
Two modes Link tweets (promoting a specific piece of content, extract the sharpest hook, link at the end) and topic tweets (standalone opinion or observation, slightly more latitude).
Signature moves Your most characteristic patterns compressed into examples.
A fictional example: Marcus, our consultant from Article 03, might have these signature moves in his tweet file: Sharp contrast between how consultants talk and how clients think. Data point followed by a reframe that challenges what the data is usually used to prove. Short declaration followed by a question he genuinely wants answered.
Building a Presentations File
A presentations file is more complex because presentations have more variables like audience, purpose, length, format, and delivery context.
What to include:
Narrative structures for different contexts An executive briefing follows a different logic than a keynote. A workshop deck is different from a pitch. Document the arc for each type you use regularly. For an executive briefing: conclusion first, evidence second, one clear ask. For a keynote: problem → stakes → possibility → path forward → call.
Slide design principles One idea per slide. Slide title states the point, not the topic (”Most organizations are already behind” not “AI Adoption Trends”). Data slides annotated to show what to notice. Never walls of text.
Your typical slide types The specific templates you reach for repeatedly: section divider, data slide, framework slide, quote slide, call-to-action slide. Document each one’s structure.
Workflow Start by building your narrative. Only when this is complete do you build out the slide spine. Now add evidence. Now you’re ready to build the design. Design comes last. This order prevents the most common presentation failure of building slides before knowing the story.
A Fictional Example
Meet Priya again (our leadership coach from Article 04). She keynotes regularly at leadership conferences.
Her presentations file contains:
Her keynote arc: Open with a behavior she’s observed in real organizations → name the underlying dynamic → offer the reframe → close with a question the audience will still be thinking about tomorrow
Her hard rules: Never read slides aloud. Never end on Q&A. Always close by returning to the opening frame.
Her typical slide types with structural templates for each
Her vocabulary for transitions between sections
When she asks Claude to help her build a 45-minute keynote on leadership under uncertainty, Claude doesn’t produce a generic conference talk. It builds from her arc, follows her rules, uses her vocabulary.
The content is still Priya’s. The structure and discipline come from the file.
How Many Platform Files Do You Need?
Only build what you actually use. A tweet file makes sense if you post on X regularly. A presentations file makes sense if you build decks regularly. Don’t build files for platforms you’re not active on.
Start with the two output types that take you the most time to get right. That’s where the investment pays off fastest.
Starter Template — Tweet File
# [Your Name] — Tweet Guide
## Voice (compressed)
[2-3 rules that capture your tweet voice specifically]
## Hard Rules
- Max 280 characters — non-negotiable
- Output ONLY the tweet text
- [Your non-negotiables]
## Link Tweet Format
[How you write tweets promoting content]
## Topic Tweet Format
[How you write standalone opinion tweets]
## Signature Moves
- [Pattern 1]
- [Pattern 2]
Starter Template — Presentations File
# [Your Name] — Presentations Guide
## Narrative Structures
### Executive Briefing
[Your arc]
### Keynote
[Your arc]
### Workshop Deck
[Your arc]
## Slide Design Principles
[Your rules]
## Slide Types
### [Slide type 1]: [structure]
### [Slide type 2]: [structure]
## Workflow
[Your order of operations]
These are just a couple of the many different “personas” that you may need to set up for Claude to make it really understand who you are and how to respond in a way that reflects that reality. Keep building!
Next: Article 10 — adapting your setup as a faith-based leader.