Skill

writing

Delivers scannable structure, clear payoffs, and strong titles when creating or editing developer docs, tutorials, proposals, and reviews.

documentation

npx claudepluginhub tomtucka/claude-plugins --plugin core

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Guidelines for creating technical content that developers can skim first and trust enough to finish.

Supporting Assets

formatting.md

SKILL.md

Similar Skills

writing

Delivers scannable structure, clear payoffs, and strong titles when creating or editing developer docs, tutorials, proposals, and reviews.

1 file

core

technical-writer

Drafts READMEs, API docs, tutorials, release notes, and reviews technical docs for clarity and structure. Activates on docs/ .md files and READMEs.

2 files

technical-writer

technical-writing

Writes clear technical prose for documentation, READMEs, design docs, blogs, and reports using multi-layer reviews for structure, clarity, and evidence quality.

1 file

alice

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitApr 24, 2026

Used By2 plugins

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Developer Writing Playbook

Guidelines for creating technical content that developers can skim first and trust enough to finish.

Philosophy

Reader-first - Lead with clarity and payoff; assume readers skim before committing

Scannable - Clear headings, short paragraphs, purposeful emphasis

Practical - State what the reader will achieve, then show how

Concise - Keep pages performant with direct copy; avoid walls of text

Consistent - Maintain brand voice, correct product names, and formatting patterns

Voice & Tone

Friendly, practical, confident

Write in first/second person ("I", "you")

Use active voice and straightforward vocabulary

Break complex ideas into shorter sentences

Aim for ~65-character reading width

Quick Reference

Task

Guide

Structural formatting rules

formatting.md

When to Use Each Guide

Formatting

Title and heading structure guidelines

Paragraph and list formatting rules

Intro and outro patterns

SEO-aware keyword placement

Developer Writing Playbook

Guidelines for creating technical content that developers can skim first and trust enough to finish.

Philosophy

Reader-first - Lead with clarity and payoff; assume readers skim before committing
Scannable - Clear headings, short paragraphs, purposeful emphasis
Practical - State what the reader will achieve, then show how
Concise - Keep pages performant with direct copy; avoid walls of text
Consistent - Maintain brand voice, correct product names, and formatting patterns

Voice & Tone

Friendly, practical, confident
Write in first/second person ("I", "you")
Use active voice and straightforward vocabulary
Break complex ideas into shorter sentences
Aim for ~65-character reading width

Quick Reference

Task	Guide
Structural formatting rules	formatting.md

When to Use Each Guide

Formatting

Use formatting.md when you need:

Title and heading structure guidelines
Paragraph and list formatting rules
Intro and outro patterns
SEO-aware keyword placement