Prose

Style guidelines for technical prose based on Google’s Developer Documentation Style Guide. Helps you write clear, consistent documentation with proper voice, inclusive language, and effective formatting.

Features

• 📝 Technical Writing Skill: Guidelines for writing clear, consistent documentation following industry best practices

Installation

Interactive

Use the plugin manager UI in Claude Code.

1. Run /plugin in Claude Code Enter
2. Go to Marketplaces Tab
3. Select + Add Marketplace Enter
4. Type tenzir/claude-plugins Enter
5. Install prose from the plugin list

Shell

Run the CLI command with your preferred scope.

# Install to user scope (default)
claude plugin install prose@tenzir

# Install to project scope (shared with team)
claude plugin install prose@tenzir --scope project

# Install to local scope (gitignored)
claude plugin install prose@tenzir --scope local

Settings

Add the marketplace and plugin to your settings file.

.claude/settings.json

{
  "extraKnownMarketplaces": {
    "tenzir": {
      "source": {
        "source": "github",
        "repo": "tenzir/claude-plugins"
      }
    }
  },
  "enabledPlugins": {
    "prose@tenzir": true
  }
}

Capabilities

Type	Name	Description
Skill	technical-writing	Write clear technical documentation following Google’s style guide. Use when writing docs, README files, API documentation, code comments, user guides, or asking about documentation style.

Usage

prose:technical-writing skill

Activates automatically when writing documentation, README files, API docs, code comments, or user guides. Provides guidance on voice, formatting, word choice, and inclusive language based on Google’s Developer Documentation Style Guide.

Example scenarios:

• “Write a README for this CLI tool” - The skill guides sentence structure, heading style, and code formatting
• “Document this function” - Ensures active voice and proper use of backticks for parameters and return values
• “Create a getting started guide” - Applies procedure formatting with numbered steps, location-before-action phrasing, and imperative verbs

What the skill catches:

• Passive voice: “An error is returned” becomes “The function returns an error”
• Jargon: “utilize,” “leverage,” “synergy”
• Non-inclusive terms: “whitelist” to “allowlist,” “master/slave” to “primary/replica”
• Filler phrases: “please note that,” “it should be noted”
• Implied simplicity: “simply,” “just,” “easy”

Changelog

View the release history and recent changes.

View on GitHub

Browse the plugin source code and documentation.