78 boosters for "docs" — open source, verified from GitHub, ready to install
doc-coauthoring guides users through a structured three-stage workflow (context gathering, refinement, and reader testing) for collaboratively creating technical documentation, proposals, and specs. It benefits technical writers, engineers, and product managers who need to efficiently co-author structured content.
Theme Factory provides a toolkit for applying professional, pre-designed color and font themes to various artifacts like slides, documents, and HTML pages. Developers and content creators benefit from rapid styling without manual design work.
The docx skill enables AI assistants to create, read, edit, and manipulate Word documents with professional formatting, tables of contents, images, and tracked changes. It's useful for developers and users who need to programmatically generate or process .docx files as part of their workflows.
A specialized agent that transforms complex technical concepts into clear, developer-friendly documentation for APIs, READMEs, and tutorials. Ideal for engineering teams, open-source maintainers, and anyone who needs to document code quickly and effectively.
"name": "@mastra/mcp-docs-server", "version": "1.1.25-alpha.4", "description": "MCP server for accessing Mastra.ai documentation, changelogs, and news.",
Create a real CLI that future Codex threads can run by command name from any working directory. This skill is for durable tools, not one-off scripts. If a short script in the current repo solves the task, write the script there instead. Name the target tool, its source, and the first real jobs it sh
A skill for building and scaffolding ChatGPT Apps SDK applications that combine MCP servers with widget UIs, using a docs-first workflow. Developers building ChatGPT extensions and integrations benefit from structured guidance on tool design, UI registration, and SDK compliance.
Provides developers with authoritative, up-to-date OpenAI API documentation and guidance by prioritizing official MCP tools for questions about building with OpenAI products. Ideal for developers integrating OpenAI APIs who need reliable, cited references.
"email": "tobi@lutke.com" "description": "Search and retrieve documents from local markdown files.", "email": "tobi@lutke.com"
Heuristic scoring (no AI key configured).
You are an expert Documentation Architect using the Divio documentation system. Before proceeding with any documentation request, take a deep breath and center your focus on technical accuracy and user success. 1. Analyze First: When a user requests documentation, first categorize the request into o
Read and follow the instructions in documentation/AI-CODE.md.
Retrieve current documentation and code examples for any library using the Context7 CLI. Make sure the CLI is up to date before running commands: Or run directly without installing:
Use this agent when documentation in the `architecture/` directory needs to be updated or created for a specific file after implementing a feature, fix, refactor, or behavior change. Launch one instance of this agent per file that needs updating. This agent maintains the *contents* of architecture documentation files — it does not decide which files exist or how the directory is organized.\n\nExamples:\n\n- Example 1:\n Context: A developer just finished implementing OPA policy evaluation in the sandbox system.\n user: "I just finished implementing the OPA engine in crates/openshell-sandbox/src/opa.rs. Update architecture/sandbox.md to reflect the new policy evaluation flow."\n assistant: "I'll launch the arch-doc-writer agent to update the sandbox architecture documentation with the new OPA policy evaluation details."\n <uses Task tool to launch arch-doc-writer with instructions to update architecture/sandbox.md>\n\n- Example 2:\n Context: A refactor changed how the HTTP CONNECT proxy handles allowlists.\n user: "The proxy allowlist logic was refactored. Please update architecture/proxy.md."\n assistant: "Let me use the arch-doc-writer agent to synchronize the proxy documentation with the refactored allowlist logic."\n <uses Task tool to launch arch-doc-writer with instructions to update architecture/proxy.md>\n\n- Example 3:\n Context: After implementing a new CLI command, the assistant proactively updates docs.\n user: "Add a --rego-policy flag to the CLI."\n assistant: "Here is the implementation of the --rego-policy flag."\n <implementation complete>\n assistant: "Now let me launch the arch-doc-writer agent to update the CLI architecture documentation with the new flag."\n <uses Task tool to launch arch-doc-writer with instructions to update architecture/cli.md>\n\n- Example 4:\n Context: A user wants high-level overview documentation for a non-engineering audience.\n user: "Update architecture/overview.md with a non-engineer-friendly explanation of the sandbox system."\n assistant: "I'll launch the arch-doc-writer agent to create an accessible overview of the sandbox system for non-technical readers."\n <uses Task tool to launch arch-doc-writer with audience=non-engineer directive>\n\n- Example 5:\n Context: Multiple files need updating after a large feature lands.\n user: "I just landed the network namespace isolation feature. Update architecture/sandbox.md and architecture/networking.md."\n assistant: "I'll launch two arch-doc-writer agents — one for each file — to update the documentation in parallel."\n <uses Task tool to launch arch-doc-writer for architecture/sandbox.md>\n <uses Task tool to launch arch-doc-writer for architecture/networking.md>
"name": "shopify-plugin", "description": "Shopify developer tools for Claude Code — search Shopify docs, generate and validate GraphQL, Liquid, and UI extension code. Skill scripts send usage telemetry (queries, code, model/client identifiers) to shopify.dev by default; set OPTOUTINSTRUMENTATION=tru
Build reusable skill packages, not long prompts. Mode rules: Operating Modes, QA Ladder, Resource Boundary Spec, Method. 1. Decide whether the request should become a skill, then choose the lightest fit.
"name": "brand-docs", "description": "AI on-brand document generator for Claude Code & Codex: turn a company's Word, PowerPoint or Excel template into unlimited on-brand .docx/.pptx/.xlsx. Extracts a reusable Brand Profile once - off-brand output impossible by construction. Skills: brand-docx, brand
Cursor Rules for Starknet documentation that enforces Mintlify technical writing standards and best practices for creating clear, user-centered developer documentation. Ideal for Starknet contributors and documentation maintainers using Cursor.
Automatically extracts knowledge from Amp threads and synchronizes project documentation, keeping AGENTS.md and other docs up-to-date after epics and major work. Ideal for teams that need to maintain living documentation without manual overhead.
ring:dev-implementation automates code development using specialized agents and enforces test-driven development (TDD) workflows across projects. Development teams benefit from consistent implementation patterns and quality gates.
uni-cli is a unified command-line interface that enables AI agents to seamlessly interact with 25+ services (messaging, productivity, research, utilities) through a consistent pattern. Developers and AI builders benefit from simplified multi-service integration without learning individual APIs.
A plaintext-first docstring formatting specification for Python code that standardizes documentation style across projects. Developers writing or maintaining Python codebases benefit from consistent, readable documentation practices.
PSI is a structured Plan-Spec-Implement workflow that guides developers through documentation-first development with test-driven implementation. It benefits teams wanting disciplined, traceable development processes with clear artifact generation.
