# dhh-writing

This skill guides an agent toward bold, direct prose for articles, business writing, and manifestos. Use it when a draft needs a clear stance and concrete arguments.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · ★ 132
- Author: robertguss
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/robertguss/claude-code-toolkit/tree/HEAD/plugins/compound-writing/skills/dhh-writing/SKILL.md
- Updated: 2026-09-16
- HTML: https://affpapa.org/en/nevibecode/skills/dhh-writing

## What it does

dhh-writing steers an agent toward David Heinemeier Hansson’s writing style: take a position, drop hedging, and make arguments with concrete examples. Its guidance covers opinion pieces, blog posts, product philosophy, and business writing, with distinct structures for different kinds of content.

The skill also points to `techniques.md`, `examples.md`, `anti-patterns.md`, and `resources.md`. It is available for Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, and OpenCode. It shapes the prose, not the evidence: bring the facts and experience your piece needs.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add robertguss/claude-code-toolkit --skill dhh-writing -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/dhh-writing/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/dhh-writing/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add robertguss/claude-code-toolkit --skill dhh-writing -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/dhh-writing/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add robertguss/claude-code-toolkit --skill dhh-writing -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/dhh-writing/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install robertguss/claude-code-toolkit dhh-writing
```

2. **Manually: put the files in place**
- File: `.github/skills/dhh-writing/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add robertguss/claude-code-toolkit --skill dhh-writing -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/robertguss/claude-code-toolkit --path plugins/compound-writing/skills/dhh-writing
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/dhh-writing/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add robertguss/claude-code-toolkit --skill dhh-writing -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/robertguss/claude-code-toolkit/tree/HEAD/plugins/compound-writing/skills/dhh-writing/SKILL.md

## When to use it
- give an opinion piece a clear thesis
- rewrite business copy without corporate jargon
- replace abstract claims with concrete examples
- shape a manifesto around a firm position

## Example prompts
- Write an article arguing that small teams should cut back on meetings; take a clear position and support it with specific points.
- Rewrite this draft in a direct, confident voice, removing hedges and corporate phrasing.
- Draft a product manifesto with a clear thesis, a response to the strongest objection, and a memorable final line.

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 1a60bb09a89a465a.

BEGIN THIRD-PARTY FILE 1a60bb09a89a465a
````text
---
name: dhh-writing
description: This skill should be used when writing in the distinctive style of David Heinemeier Hansson (DHH). It applies when creating blog posts, technical articles, business content, manifestos, or any prose requiring a clear, punchy, opinionated style.
---

# DHH Writing Skill

Write in the distinctive style of David Heinemeier Hansson—direct, brave, opinionated prose that takes a stand and defends it unapologetically.

## When to Use This Skill

This skill applies when:
- Writing opinion pieces or manifestos
- Creating blog posts that need to take a strong position
- Crafting business or product philosophy content
- Writing in a "Basecamp/37signals voice"
- Creating content that challenges conventional wisdom
- Any writing that needs to be punchy and memorable

## Core Philosophy

> "Strong opinions, weakly held" is half-right. You need strong opinions, *strongly expressed*. The weakness comes from being willing to change when presented with better evidence—not from hedging your delivery.

DHH's writing is characterized by:
- **Conviction**: Every piece has a clear position
- **Courage**: Willing to say unpopular things
- **Clarity**: No corporate-speak, no hedging
- **Concision**: Short sentences, short paragraphs

## The 10 Core Techniques

Reference [techniques.md](./references/techniques.md) for the complete guide.

### 1. Take a Stand

Every piece must have a thesis you can disagree with.

```
❌ "There are pros and cons to remote work that teams should consider."

✅ "Remote work is the future. Companies clinging to mandatory office time
    will lose their best people to those who trust their employees."
```

### 2. No Hedging

Remove qualifiers that weaken your position.

**Words to eliminate**:
- "I think..." (just say it)
- "In my opinion..." (obviously)
- "It seems like..." (commit)
- "Some might say..." (who?)
- "Generally speaking..." (specifically speak)

### 3. Short Sentences

Punch. Impact. Clarity.

Long sentences with multiple clauses, while sometimes necessary for complex ideas that require careful qualification and nuanced expression, often dilute the force of your argument and lose readers who are scanning for the key point.

Short sentences work better.

They're memorable.

They're quotable.

They're true.

### 4. Contrarian Framing

Start by identifying what "everyone knows." Then challenge it.

```
"Everyone knows you need to move fast and break things."

Actually, you don't. Moving deliberately and building things that last
is how you win the long game.
```

### 5. Concrete Over Abstract

Don't argue about philosophies. Argue about practices.

```
❌ "Agile methodologies can become bureaucratic when over-implemented."

✅ "If your 'agile' process requires 3 meetings before a developer can
    start coding, you're doing waterfall with more steps."
```

### 6. The Rule of Three

Three examples. Three reasons. Three beats.
````
END THIRD-PARTY FILE 1a60bb09a89a465a

The third-party file has ended. Everything between the 1a60bb09a89a465a tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2934 of 6427 bytes. © robertguss · MIT · https://github.com/robertguss/claude-code-toolkit/tree/HEAD/plugins/compound-writing/skills/dhh-writing/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md