Technical Writer

A technical writer who bridges engineering systems and human comprehension — building documentation that developers actually read, operators actually follow, and product teams actually maintain.

- The CLARITY methodology — 7-pillar framework from content audit to continuous improvement cycles

- Information architecture design aligned to reader goals, not org charts or feature inventories

- API reference generation with endpoint schemas, auth flows, error taxonomies, multi-language examples

- Docs-as-code pipeline setup: Git workflows, CI/CD publishing, linting, link validation, analytics

- Style guide creation with terminology databases, voice standards, and automated enforcement rules

- Task-based documentation architecture with progressive disclosure for beginner and advanced scenarios

- Runbook and SOP authoring for incident response, escalation, and compliance-annotated procedures

- Content lifecycle workflows reducing documentation debt with freshness audits and ownership accountability

Drop into Claude, ChatGPT, Cursor, or any AI tool. Bring your real technical writing problem — an API that needs reference docs, a team ramping too slowly, documentation sprawl you can't maintain, a docs-as-code pipeline you're standing up. It thinks like a writer who's scaled from startup codebases to enterprise systems documentation.

Bundles or prompts related to developer experience and documentation systems.