22 stories
Most runbooks fail the moment they are needed: the command was renamed, the dashboard moved, the owner left. Learn how to write a runbook that a tired engineer can follow, a template you can copy, and how to keep it from rotting.
Most pull request descriptions restate the title or the prompt. A practical guide to writing PR descriptions that speed up review and survive in git history: what to include, a copy-paste GitHub template, examples, and how to keep agent-written descriptions honest.
AI agents now read your API docs before developers do. What OpenAPI, llms.txt, Markdown pages, and an MCP server each give an agent, which one to build first, how to write descriptions an agent can act on, and how to keep all of them in sync with the code.
llms.txt is a small Markdown file that tells AI agents which pages on your site matter. What the v2 spec requires, a worked example, the mistakes validators catch, how to serve it, and why the file quietly goes stale.
Agents write code faster than teams can review it, and agent PRs fail differently than human ones. A practical guide to reviewing AI-generated pull requests: the failure modes worth your attention, a review order that catches them, and how to move the work earlier so less of it lands on a human.
Coding agents fail on context, not capability. A practical guide to context engineering for a real repository: the four layers, a token budget you can reason about, how to diagnose which layer is failing, and how to keep it from going stale.
Skills, MCP servers, and CLAUDE.md all load context into a coding agent, but they are not interchangeable. A decision guide to picking the right one - static procedure vs. live data - without bloating the context window or shipping stale answers.
Struggling with slow developer onboarding? We tested MoxieDocs and found out if it cuts ramp-up time by 30%—plus its hidden perks for GitHub maintainers.
Struggling to keep docs up-to-date with a tiny team? Compare MoxieDocs and DeepDocs to see which AI docs generator saves your engineers time without sacrificing clarity—so you can ship faster.
GitHub documentation tools matter—especially for teams using docs as code. This comparison cuts through the noise to show which tool, MoxieDocs or DocuWriter.ai, keeps your docs in sync with your codebase *without* the hassle.
Outdated docs slow teams down. Discover how **living documentation tools** help engineering teams sync docs with code, reduce friction, and keep knowledge current—without the manual busywork.
Moxie Docs now has a permanent Free plan: connect one repository, no credit card required ever, and see real generated docs, search, and live MCP context on your own code.
Discover 8 MCP documentation servers that streamline setup for developers, AI tool builders, and technical teams. Improve efficiency with targeted solutions for coding assistants.
Documentation debt compounds like tech debt but almost nobody tracks it. Learn where it comes from, how to score it, and how to set up a ratchet that keeps docs from rotting again.
Learn how to set up and utilize the MCP Documentation Server to streamline your documentation workflows, improve collaboration, and support AI-driven projects with detailed, step-by-step guidance.
MCP servers introduce a new attack surface: tool poisoning, rug pulls, confused deputy, and the lethal trifecta. What is real, and how to mitigate it.
Explore the best ADR tools to manage Architecture Decision Records. Compare ADR-Tools CLI, Log4brains, and Moxie Docs, and get a free Markdown ADR template.
Learn how to build an enhanced MCP feedback loop for coding agents. Practical guide to integrating automated testing, linting, and self-correction via MCP servers.
Showing 18 of 22 stories
Load more storiesGet the top AI news and tools straight to your inbox every week.
Weekly · AI news from Moxie Docs Blog
Join 15,000+ AI enthusiasts
