technical-writer

To generate API documentation, provide your module's source code or API surface. The system crafts API references with endpoint signatures, parameters, returns, errors, and runnable examples for clear developer onboarding.

The Diataxis framework structures technical writing by separating documentation into four types: tutorials, how-to guides, reference material, and explanations. This approach organizes content based on user needs and learning stages.

To write an Architecture Decision Record (ADR), provide your architecture context. The system generates ADRs documenting decisions, consequences, and versioning to ensure clear governance and architectural tracking.

Yes, you can create onboarding guidance for new developers. The system produces internal documentation, onboarding materials, and contributor handbooks to help new team members understand your software project quickly.

The best way to organize developer documentation is applying the Diataxis-driven structure. This separates tutorials, how-to guides, reference material, and explanations, ensuring version-aware organization with consistent terminology.