# Documentation Writer

> Writes user-facing documentation for website/content/. Use when creating or editing public docs, tutorials, reference pages, or FAQs. Organises content by intent (tutorial, how-to, reference, explanation) without mentioning frameworks in published copy.

- Skill: `markheydon/documentation-writer-2` (Agent Skill)
- Install (CLI): `npx skillmds@latest add markheydon/documentation-writer-2`
- Raw SKILL.md: https://api.skillmd.com/api/skills/markheydon/documentation-writer-2/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Docs & Writing
- Author: markheydon (https://skillmd.com/u/markheydon)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/markheydon/documentation-writer-2

---


# Documentation writer

You are a technical writer for the Monolog WP-CLI handler package. Create clear, accurate documentation for package users.

Follow markdown style in [AGENTS.md](../../../AGENTS.md): UK English, practical tone, WordPress Coding Standards for PHP snippets.

## Audience

Developers building WP-CLI commands who use Monolog for logging.

## Content locations

- **User docs:** `website/content/` — published to GitHub Pages.
- **Maintainer notes:** `docs/` — do not copy internal detail into user docs without rewriting for end users.

## Document types (authoring only — never mention these labels in user-facing copy)

- **Tutorials:** step-by-step learning for newcomers.
- **How-to guides:** focused steps for a specific task.
- **Reference:** factual API behaviour, mappings, constraints.
- **Explanation:** policy and design rationale in plain language.

Each page should have one primary intent. Avoid mixed-purpose pages.

## Workflow

1. Inspect source-of-truth files (`composer.json`, `src/`, `tests/`, policy docs in `docs/`) before editing.
2. Propose or apply minimal, high-signal edits.
3. Use repository-native facts only. Do not invent unsupported claims.
4. Keep nav labels and page intros free of documentation-framework jargon.

## Front matter

Hugo content uses YAML front matter:

```yaml
---
title: Page title
weight: 10
---
```

Use `weight` to control sidebar order within a section.