technical-writer

Write API documentation, READMEs, and ADRs using the Diataxis framework.

4|1|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/aegntic/clawreform --skill technical-writer-aegntic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: technical-writer
Source: https://github.com/aegntic/clawreform/tree/main/crates/clawreform-skills/bundled/technical-writer
Command: npx skills add https://github.com/aegntic/clawreform --skill technical-writer-aegntic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the creation of high-quality, developer-focused documentation, ensuring clarity, accuracy, and adherence to best practices.

Core Features & Use Cases

  • API Documentation: Generates clear and comprehensive API reference entries.
  • READMEs & ADRs: Structures project READMEs and Architecture Decision Records effectively.
  • Developer Onboarding: Creates tutorials and how-to guides that are easy to follow.
  • Use Case: A new feature is released, and this Skill can be used to generate the corresponding API documentation, update the README with a quick-start example, and draft an ADR explaining the architectural choices.

Quick Start

Use the technical-writer skill to generate a README for a new Rust project.

Frequently Asked Questions about technical-writer

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

FAQPage Schema
How do I generate API documentation and developer guides for a new feature release?

To generate API documentation and developer guides, provide your feature details to generate clear reference entries, quick-start README examples, and tutorials. It structures content using the Diataxis framework, organizing documentation into tutorials, how-to guides, reference material, and explanations.

What is the Diataxis framework and how does it structure technical writing?

The Diataxis framework is a documentation structure that organizes technical writing into four distinct types: tutorials, how-to guides, reference material, and explanations. It ensures developer-focused documentation maintains clarity, precision, and empathy by separating learning materials from technical references.

How do I write an Architecture Decision Record for a new software project?

To write an Architecture Decision Record (ADR), input your architectural choices and project context. The system drafts an effective ADR explaining your decisions clearly, alongside generating matching API documentation and updating your project README with relevant quick-start examples.

Can I use this for developer onboarding tutorials and how-to guides?

Yes, you can use this for developer onboarding by generating easy-to-follow tutorials and how-to guides. It focuses on developer empathy and clarity, ensuring new team members can quickly understand APIs, project READMEs, and architectural decisions through structured documentation.

What is the best way to structure a README for a new software project?

The best way to structure a README is by adhering to the Diataxis framework and focusing on developer clarity. It generates comprehensive README files with quick-start examples, ensuring high-quality, developer-focused documentation that streamlines project onboarding and feature understanding.