Documentation
Document APIs so developers succeed on first try, not third support ticket.
Write docs people actually read and reference. Technical accuracy meets user clarity.
Tutorial and maintenance prompts for instructions people can follow, test, and recover from.
Write docs, specs, and guides that engineers and users both understand.
Automatically turn workflows into step-by-step guides.
Create clear API documentation that helps developers integrate successfully.
Create instructions readers can follow and verify without guesswork.
Define product requirements so engineering, design, and stakeholders build the right thing.
Update technical content only where the evidence shows it needs changing.
Write tutorials that beginners can actually follow without getting stuck.