voice

# Outfitter Voice

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.

## Quick Reference

| 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. |

## Agents at Every Step

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:
- Documentation is structured for machine readability, not just human skimming
- Rules aren't just stated — they're codified, tested, and enforced
- Errors are typed and explicit, because agents need to handle them too
- Examples are copy-paste runnable, because that's how agents learn

## Serve the Goal

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:
- **Quick Start** — Get to code fast. Context comes after, if at all.
- **Philosophy section** — Room to breathe. Explain the why.
- **API reference** — Precision over personality. Just the facts.
- **Blog post** — Full voice. Narrative, per