tech-writer

You can automate API documentation generation by processing code and design artifacts through frontmatter-driven templates. This Skill transforms ADRs and design notes into consistent API docs, READMEs, and changelogs while enforcing code-style examples and standardized terminology.

The docs-as-code approach treats documentation like source code by enforcing Markdown frontmatter, versioned docs, and templates aligned with code. It centralizes and standardizes developer-facing materials, ensuring documentation remains consistent, maintainable, and directly synchronized with software project updates.

Writing consistent ADRs and changelogs across projects requires applying standardized templates and consistent terminology. This Skill automates the generation of these materials from design notes and code, ensuring every architecture decision and changelog entry maintains a uniform style for developer experience.

Yes, you can use Markdown frontmatter and versioned templates for onboarding materials. This Skill supports documentation as code practices by enforcing frontmatter-driven templates and versioned docs, allowing teams to scale onboarding materials alongside code changes while maintaining consistency.

Yes, this documentation approach works without external dependencies or component libraries. The Skill operates independently to generate API documentation, READMEs, and ADRs by directly applying frontmatter-driven templates and consistent terminology to your code and design artifacts.