internal

Creates compelling copy for Outfitter — blog posts, announcements, marketing content. Writes with voice and style, not structure.

Reviews and refines Outfitter content for voice, style, and structure. The final pass before publishing — ensures everything aligns with Outfitter standards.

Creates technical documentation for Outfitter — READMEs, API docs, guides. Focuses on structure, completeness, and clarity for both humans and agents.

Documentation for AI agents — AGENTS.md, CLAUDE.md, and agent-readable content patterns. Use when creating agent entry points, structuring .claude/ directories, or when "CLAUDE.md", "AGENTS.md", "agent documentation", "machine-readable", or "writing for agents" are mentioned. Covers both configuration and content patterns for agent consumption.

Check and configure outfitter marketplaces and plugins. Use when setting up a new project, checking plugin configuration, or when "setup outfitter", "configure plugins", or "marketplace" are mentioned.

Rigorous quality gate for documentation before merge or publish. Verifies code examples run, links resolve, APIs match implementation, and all sections are complete. Use when auditing docs, reviewing documentation PRs, or when "verify", "quality gate", "docs audit", or "check examples" is mentioned.

Reviews documentation for voice, style, and structure alignment with Outfitter standards. Use when reviewing docs, checking content quality, or when "review this doc", "voice check", "style review", or "is this ready?" are mentioned.

Project documentation structure and templates — READMEs, API docs, guides, and CLI references. Use when creating documentation, structuring a docs/ directory, writing READMEs, or when "documentation", "README", "API docs", "docs structure", or "guides" are mentioned. Pair with styleguide for writing craft; apply voice as a review pass.