documentation

To write a technical README for new developers, you need audience-first technical writing that provides installation steps, working examples, and a scannable Markdown structure so contributors can act quickly. The documentation skill generates this content by matching the target reader's needs and emphasizing example-driven explanations.

The best way to generate an API reference outline is to apply specified formatting and docstring conventions to your codebase. The documentation skill produces audience-appropriate API references that emphasize scannable structure and working examples, ensuring developer integration is straightforward.

Creating architecture documentation for system maintainers requires clear technical writing that explains system design accurately. The documentation skill produces architecture notes tailored to maintainers, ensuring system understanding is achieved through consistent formatting and audience-appropriate content.

Yes, you can use this to write a developer guide with Markdown and code examples. The documentation skill produces developer guides that follow Markdown conventions, apply scannable structure, and provide example-first guidance so readers can integrate features quickly.

A changelog for software projects should include accurate, scannable updates formatted using Markdown conventions. The documentation skill produces changelogs that maintain formatting standards and audience-appropriate content, ensuring maintainers and users understand changes quickly.

Yes, the documentation skill supports specified formatting and docstring conventions for API references. It fulfills requirements by applying common docstring styles and Markdown conventions to ensure your generated technical writing is accurate and maintainable.