documentation-writer

Generate Diátaxis-style documentation with tutorials, guides, reference, and explanations.

1|Updated May 7, 2026

Search Tags:#documentation #writing #markdown #diataxis #brand-voice #content-design

Ready to run

npx skills add https://github.com/ChristopherAlphonse/calphonse-skills --skill documentation-writer-christopheralphonse

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: documentation-writer
Source: https://github.com/ChristopherAlphonse/calphonse-skills/tree/main/documentation-writer
Command: npx skills add https://github.com/ChristopherAlphonse/calphonse-skills --skill documentation-writer-christopheralphonse

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Produces high-quality software documentation guided by the Diátaxis framework, ensuring clarity, consistency, and brand voice across projects.

Core Features & Use Cases

Diátaxis quadrants: Tutorials, How-to Guides, Reference, and Explanations covered in a single documentation suite.
Brand voice and guardrails: Maintains consistent tone, accuracy, and user-centricity across materials.
Quick-start focus: Generates ready-to-publish content with a clear structure for a given topic and audience.

Quick Start

Provide a topic and audience to generate a four-quadrant Diátaxis documentation set.

Frequently Asked Questions about documentation-writer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

What is Diátaxis documentation and how does it structure technical writing?▼

Diátaxis documentation structures technical writing into four quadrants: tutorials, how-to guides, reference material, and explanations. This framework separates learning-oriented content from practical work guides and reference data to ensure user-centric clarity across software documentation projects.

How do I generate a complete documentation suite across Diátaxis quadrants?▼

To generate Diátaxis documentation, provide a topic and audience to produce a four-quadrant documentation set. The output includes ready-to-publish Markdown content covering tutorials, how-to guides, reference material, and explanations with a consistent brand voice.

Can I enforce a specific brand voice in my developer portal documentation?▼

Brand voice is enforced across your developer portal documentation by applying consistent tone, accuracy, and user-centric writing guardrails. This ensures all generated tutorials, guides, and reference materials maintain a unified style aligned with your repository guidelines.

Does this approach produce Markdown-ready content for software documentation projects?▼

Yes, this approach produces Markdown-ready content specifically for software documentation projects and developer portals. The output is structured with clear formatting, ready to publish directly into your repository without requiring additional content design or conversion steps.

What's the best way to write tutorials and how-to guides that maintain accuracy and clarity?▼

The best way to write accurate tutorials and how-to guides is using the Diátaxis framework to separate learning goals from practical steps. This user-centric approach enforces clarity by matching content type to user intent, ensuring reference material remains precise and explanations stay focused.