Writing craft and style patterns for Outfitter content — sentence rhythm, metaphors, enthusiasm calibration. Use when drafting or reviewing blog posts, docs, announcements, or READMEs.
Applies craft-level writing guidance for blog posts and documentation with rhythm, metaphor, and calibrated enthusiasm.
npx claudepluginhub outfitter-dev/outfitterThis skill inherits all available tools. When active, it can use any tool Claude has access to.
references/SAMPLES.mdCraft-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 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.
The "Product Person" Who Ships
Outfitter exists at the intersection of product thinking and engineering craft:
Agents as Readers
We write for Claude as much as we write for humans:
Attention as Constraint
Every tool we build, every word we write, should respect the reader's time:
Voice (always present):
Tone (adjust per context):
The key tension: We care deeply about craft and ideas. We refuse to be precious about it.
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.
| 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. |
scout, write scout.scout, say "research" unless the metaphor genuinely improves understanding.Would a thoughtful reader roll their eyes? If yes, drop the metaphor and say it straight.
The voice is engineered for readability. Ideas are "atomized" for digital consumption.
| 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)…" |
Every third or fourth sentence should act as a reset—short, punchy, direct. Uniform paragraph sludge loses readers.
Mix high-status (authority) and low-status (trust) signals strategically.
Elevate the reader through precision while leveling the field through honesty. Never lecture down. Position as a peer figuring it out alongside them.
Constraint: Don't over-credential. Let precision and comfort with tradeoffs signal competence; don't announce it.
Earned enthusiasm lands. Manufactured enthusiasm repels.
Would you say this to a smart friend over coffee? If it sounds like marketing copy, rewrite it.
| Instead of... | Try... |
|---|---|
| "game-changing" | describe the actual change |
| "seamless" | "I didn't have to…" |
| "incredible/amazing" | a concrete fact or benchmark |
| "revolutionary" | "new capability: …" |
| "We are excited to share" | Start with the value |
| "best-in-class" | specific comparison |
| "synergy" | never |
Rule: One well-placed superlative lands. Three reads as marketing.
Pick exactly one:
"I've co-founded five startups... but the engineering? Always in someone else's hands."
Vulnerability first, then the journey.
Pick exactly one:
The goal of the content determines its shape. Match the container.
Before publishing, ask:
If any answer is wrong, revise.
This skill should be used when the user asks about libraries, frameworks, API references, or needs code examples. Activates for setup questions, code generation involving libraries, or mentions of specific frameworks like React, Vue, Next.js, Prisma, Supabase, etc.