styleguide

Guide craft-centric writing for Outfitter blog posts, docs, and READMEs.

Updated Jan 25, 2026
One-click install
npx skills add https://github.com/outfitter-dev/agents-internal --skill styleguide
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: styleguide
Source: https://github.com/outfitter-dev/agents-internal/tree/main/internal/skills/styleguide
Command: npx skills add https://github.com/outfitter-dev/agents-internal --skill styleguide

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Crafting consistent, clear Outfitter content across blog posts, docs, announcements, and READMEs is hard; teams struggle with rhythm, metaphors, and structure that communicate value without hype.

Core Features & Use Cases

  • Voice & Tone guidelines that establish a consistent believer-researcher persona and adapt to context while respecting the reader's time.
  • Expedition and structural patterns that guide metaphor usage, signposting, and concise formatting to improve readability and machine readability.
  • Practical templates and examples that demonstrate how to apply the styleguide to real-world content.

Quick Start

Draft a short Outfitter post about a recent finding using the styleguide's voice, rhythm, and structure, ensuring clarity and authentic enthusiasm.

Frequently Asked Questions about styleguide

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I establish a consistent writing voice for technical blog posts and documentation?

To establish a consistent writing voice, apply defined persona guidelines that adapt tone to context while respecting the reader's time. It maintains authentic enthusiasm across blog posts, docs, and READMEs without relying on hype.

What's the best way to structure content for readability and machine readability?

The best way to structure content for readability is to use expedition and structural patterns that guide signposting and concise formatting. These patterns ensure content remains clear for human readers and parseable for machines.

How do I use metaphors effectively in technical writing without adding hype?

To use metaphors effectively without hype, follow explicit guidelines that constrain metaphor usage to structural, signposting patterns. This ensures craft-centric communication that conveys value authentically rather than relying on exaggerated claims.

Can I use a styleguide to draft README files, or is it limited to blog posts?

You can use it to draft README files, documentation, and blog posts. It adapts tone, rhythm, and structure to the specific context of each format while preserving machine readability and defined voice requirements.

How do I apply writing rhythm and signposting to Outfitter content templates?

To apply writing rhythm and signposting, use the practical templates and concrete examples provided to draft content. These templates demonstrate how to satisfy requirements for voice, rhythm, and explicit examples in real-world scenarios.

Why does my technical writing tone feel inconsistent across different content formats?

Writing tone feels inconsistent across formats when lacking defined voice and rhythm guidelines tailored to each context. Applying a styleguide adapts tone appropriately for docs, announcements, and READMEs while preserving a consistent persona.