Writing craft and style patterns for Outfitter content — sentence rhythm, metaphors, enthusiasm calibration. Use when drafting or reviewing blog posts, docs, announcements, or READMEs.
Writing craft and style patterns for Outfitter content — sentence rhythm, metaphors, enthusiasm calibration. Use when drafting or reviewing blog posts, docs, announcements, or READMEs.
Craft-level guidance for Outfitter writing. This covers how to write — rhythm, metaphors, structural patterns.
For the philosophical foundation (why we write this way), load the outfitter-voice skill.
Write like someone who's genuinely excited to share what they discovered—while staying honest about rough edges.
The Core Stance
The Builder on the Trail
You're not a guru dispensing wisdom from a mountaintop. You're a fellow traveler who found a useful path and is sharing it with others still navigating.
Problems are design challenges, not insurmountable obstacles
Optimism is structural, but grounded in what actually works
Cynicism is avoided—never tear down without offering a better alternative
Focus on utility and durability, not hype
The "Product Person" Who Ships
Outfitter exists at the intersection of product thinking and engineering craft:
Respect for engineering: use specific metrics because craft matters
Focus on outcome: care about durable software, not code elegance for its own sake
Not claiming expert status: empowered by new tools, learning in public
Agents as Readers
We write for Claude as much as we write for humans:
Structure for machine readability, not just human skimming
Examples are copy-paste runnable
Errors and edge cases are explicit, not implied
Attention as Constraint
Every tool we build, every word we write, should respect the reader's time:
Prioritize information density over word count
If a sentence doesn't add value, delete it
Serve the goal — voice is how we say things, not permission to say more
The writing style is a recursive implementation of the product philosophy
Voice vs. Tone
Voice (always present):
Curious practitioner
Builder's mindset (even when learning)
Respectful of reader's intelligence and time
Sincere enthusiasm without self-importance
Concrete specificity over abstraction
Tone (adjust per context):
Playful when introducing tools
Precise when documenting
Earnest when mission-driven
Technical without gatekeeping
The key tension: We care deeply about craft and ideas. We refuse to be precious about it.
The Expedition Layer
The expedition layer is a brand aesthetic, not a prose checklist. It should shape the feel of names,
structure, and examples without turning every paragraph into metaphor.
Use expedition language literally when it's part of the product (for example, a command, package, or
feature name). Otherwise, treat it as background texture: present when useful, invisible when forced.
Where It Shows Up Naturally
Layer
How to Apply It
Product terminology (literal)
Use exact expedition terms when they are official names (commands, packages, features, docs headings).
Thematic vibe (atmospheric)
Let the outdoors/exploration feel influence framing and identity, but default to direct language in body copy.
Product decisions (examples)
Expedition concepts can guide naming systems, information architecture, or onboarding journeys when they improve clarity.
Practical Distinction
If the thing is literally named scout, write scout.
If the thing is not named scout, say "research" unless the metaphor genuinely improves understanding.
Prefer clarity first; theme is a multiplier, not the main payload.
When to Skip It
Technical specifications (just be precise)
Error messages (just be clear)
API documentation (just be accurate)
When it would feel forced or cutesy
The Test
Would a thoughtful reader roll their eyes? If yes, drop the metaphor and say it straight.
Sentence Rhythm: Punch-and-Flow
The voice is engineered for readability. Ideas are "atomized" for digital consumption.
Four Sentence Types
Type
Function
Example
Setup (Flow)
Draws reader in, establishes context
"Recently we've seen agents waste 60,000+ tokens per documentation lookup…"
Pivot (Hinge)
Connects thought to consequence; uses colons or dashes
"The result: search in 5-50ms, not 5-50 seconds."
Punch (Impact)
Short, direct; resets attention
"That changed everything."
Aside (Meta)
Parenthetical; adds intimacy
"…context engineering (more on that later)…"
The Rule
Every third or fourth sentence should act as a reset—short, punchy, direct. Uniform paragraph sludge loses readers.
Status Modulation
Mix high-status (authority) and low-status (trust) signals strategically.
High Status (Establish Credibility)
Specific metrics: "5-50ms," "6ms warm cache," "100k tokens saved"
Technical precision: terms like "latency," "index," "cache" used correctly
