Developer Docs

Write clear READMEs, technical specs, runbooks and developer-facing docs

Build a navigable documentation canvas with sections, diagrams and cross references

Find docs that drifted from the code and sync or audit them for consistency

Write a bug post-mortem covering root cause, mechanism, fix and how it slipped through

Update changelog files with entries that follow the required format

Convert wiki markdown and Mermaid diagrams into Azure DevOps Wiki format

Generate a hierarchical wiki structure for a codebase and its architecture

Generate categorized changelogs from your git commit history

Generate llms.txt and llms-full.txt files for LLM-readable project docs

Write onboarding guides for contributors, staff engineers, executives and PMs

Write technical wiki pages with Mermaid diagrams and source code citations

Answer questions about how a codebase works from its source files

Run multi-turn deep research on how the systems of a codebase work across files

Package wiki Markdown into a VitePress site with Mermaid and dark theme

Create a Docus documentation site for a project with search and dark mode

Review docs for clarity, SEO and technical accuracy in Markdown projects

Pull code examples into Dart API docs with the example directive

Write Dart doc comments that follow the Effective Dart guidelines

Draft paper sections, project summaries and resume entries from your code

Write a nine-part onboarding doc set for any code project in its docs folder

Explain how a subsystem works and where new code should live before changing it

Explain a body of work plainly so the reader actually understands it

Fetch npm, PyPI and crates.io package source so agents see how dependencies work

Map an unfamiliar code area on one screen with entry points and data flow

Write API handoff docs so frontend developers can integrate a finished backend

Write README files with templates matched to your audience and project type

Write up the data needs of a UI as clear API requirements for backend developers

Audit and write developer docs and READMEs using Google's documentation style guide

Explain a codebase, folder or pull request to a newcomer as a visual walkthrough

Improve README and docs pages so a new reader grasps the project in one screen

Fetch current library docs from llms.txt files and GitHub repositories

Write beginner-friendly markdown explanations of an entire code repository

Publish work reports as structured local HTML pages with layered detail

Turn git commits into customer-friendly changelogs and release notes

Search and fetch Stripe docs and API reference pages, including gated content

Structure tutorials, how-to guides and reference docs using the Diataxis framework

Redesign GitHub READMEs with custom SVG, PNG and GIF hero and section visuals

Build interactive API docs, generate SDKs and create developer portals with OpenAPI 3.1

Generate C4 architecture documentation for an existing codebase bottom-up

Document code-level C4 structures with signatures, dependencies and module layout

Turn code-level docs into C4 component diagrams, boundaries and interfaces

Map C4 components to containers, deployment units and container APIs

Write C4 system context diagrams, personas, user journeys and external dependencies

Explain complex code with clear narratives, diagrams and step-by-step breakdowns

Generate API docs, architecture diagrams and user guides from source code

Write long-form technical manuals and architecture guides from an existing codebase

Generate API docs, architecture diagrams and user guides from source code

Write exhaustive API and configuration references with full parameter listings

Turn code into step-by-step tutorials with hands-on examples and onboarding guides