Outfitter's philosophical voice and values — opinionated stance, agent-first design, earned confidence. Use when writing content, reviewing drafts, or establishing tone.
Applies Outfitter's opinionated, agent-first philosophical voice to writing and content review.
npx claudepluginhub outfitter-dev/outfitterThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Outfitter writes like it means it. We're unapologetically opinionated — not because we think we're always right, but because wishy-washy tools make for wishy-washy software. If we've made a choice, we'll tell you why and stand behind it.
| Principle | In Practice |
|---|---|
| Opinionated | State choices clearly. Explain why. Don't hedge. |
| Agent-first | Structure for machines. Runnable examples. Typed errors. |
| Goal-serving | Match voice to container. Quick starts are quick. |
| Clear > clever | Personality that reinforces understanding, not obscures it. |
| Plain language | Save generics for code. Use words people say. |
| Earned confidence | Claims backed by examples, benchmarks, tests. |
| Ownership stance | First-person "we". Possessive when it fits. |
We build with agents at every step of the way, and we're explicit about it. Agents aren't an afterthought or a marketing angle — they're first-class consumers of everything we make. When we write, we're writing for Claude as much as we're writing for you.
This shapes everything:
Voice is how we say things, not permission to say more.
If someone needs a code example, give them the code example. If they need a quick answer, give them the quick answer. Don't make people scroll past your life story to get the recipe.
The goal of the content determines its shape:
Match the container. A README Quick Start and a blog post have different jobs.
Default to clarity. When established conventions exist, follow them.
But clever can be clear when it reinforces the mental model:
crumb drop has personality without sacrificing meaning. crumb new is functional, but forgettable.Clever fails when it requires translation:
The test: Does the cleverness help you understand, or make you pause to decode?
Reinforce the vibe. Don't invent vocabulary.
"Typed errors instead of throwing" lands better than Result<T, E> in prose.
Save the generics for code blocks. When explaining concepts, use words people actually say. Technical precision matters in code; human clarity matters in explanation.
This doesn't mean dumbing down. It means choosing the right level of abstraction for the medium.
We care about how things feel, but we don't trust feelings alone.
If a rule matters, it's codified, tested, and enforced. Opinions without teeth are just suggestions. We don't say "prefer X" — we lint for it, test for it, fail builds over it.
This applies to voice too. If we claim something is simple, there's a working example. If we claim something is fast, there's a benchmark. Earned confidence, not asserted confidence.
Outfitter takes ownership. First-person "we" when speaking as the project. Possessive when it fits: "Outfitter's shared infrastructure" not "shared infrastructure for Outfitter."
We're unapologetically opinionated about:
We're not hedging. We're not "just a simple tool." We're building something with purpose.
This skill is the philosophical foundation — the why and how we think.
It's not:
outfitter-styleguide skill)outfitter-documentation skill)Load this skill to ground your writing in Outfitter's values. Load outfitter-styleguide for craft, outfitter-documentation for structure.
When reviewing content against Outfitter voice:
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.