Developer Docs

Generate a project summary from milestone artifacts for team onboarding

Build a three-column documentation page with side navigation and table of contents

Apply Chinese typesetting rules for spacing, punctuation and terms in docs

Check project docs against the source so they match the code in every language

Build in-repo maintenance docs with symbol coverage maps and audits for a codebase

Draft proposals, specs, ADRs and README sections that fresh readers can follow

Build Next.js documentation sites with Geistdocs, MDX, AI chat and i18n

Look up docs and source for the Agent-Native core packages in node_modules

Manage repo-backed Markdown and MDX docs, blogs and rich documents

Build a visual docs workspace for a repo's APIs, components and flows

Write architecture decision records that capture the reasons behind a choice

Draft RFC proposals that gather stakeholder input before a major technical change

Write and review READMEs, guides and /docs pages with consistent structure and tone

Write technical design docs with mandatory sections through guided discovery

Write Angular docs pages with Google technical writing rules and adev markdown

Document C# types with XML comments and a consistent documentation style

Document Java types with Javadoc comments in a consistent, useful style

Explain code, concepts or system behavior at a depth you choose

Write release notes in several formats from your git commit history

Write CHANGELOG, PR and Slack release notes in plain language from git commits

Build VitePress documentation sites with themes and Vue components in Markdown

Generate README and DESIGN.md skeletons from a module's structure

Turn any codebase into an interactive single-page HTML course for beginners

Write docs with a clear split of tutorials, how-to guides, reference and explanation

Build a shared domain model with a glossary and architecture decision records

Generate standalone Markdown reference docs for Qt and C++ source files

Generate standalone Markdown API reference docs for QML components and apps

Add, lint and manage YAML front matter with tags, description and memo fields

Work in a source-grounded codebase wiki with architecture, module and flow notes

Frame a design proposal problem-first with real alternatives and honest drawbacks

Record an architecture decision with context, options and consequences

Organize software proposals, decisions, specs and postmortems in one docs project

Write docstrings, OpenAPI specs, JSDoc and user guides for your code

Generate OpenAPI specs from Flask, FastAPI, Express and Gin route definitions

Draft release notes from a commit range, grouped by what readers will get

Check current official docs before using any API, SDK, framework or CLI

Define and audit a project domain vocabulary and glossary across code and docs

Sync project markdown docs and release notes after changes ship

Record short ADRs that keep your decisions in your exact wording

Read every ADR in docs/adr to load past project decisions

Write user-facing App Store release notes from changes since the last git tag

Find official DOCA docs, installed versions and sample code locations

Look up version-matched NVSHMEM and NVSHMEM4Py docs for APIs and transports

Audit a product's developer experience by having subagents follow its docs

Write godoc comments, READMEs, changelogs and runnable Go examples

Look up Go packages, symbols, versions, licenses and CVEs on pkg.go.dev

Generate OpenAPI docs for Go APIs with swaggo annotations and framework support

Turn existing ADRs, PRDs and specs into a planning setup with conflict notes

Turn a codebase into Markdown docs and an index where every claim cites source