AI Summaryrtfmbro-mcp provides AI coding agents with always-up-to-date, version-specific package documentation to prevent outdated knowledge errors. Developers and teams using Claude/Copilot for agentic coding tasks benefit from accurate, real-time API references.
Install
Copy this and paste it into Claude Code, Cursor, or any AI assistant:
I want to add the "rtfmbro-mcp — Copilot Instructions" prompt rules to my project. Repository: https://github.com/marckrenn/rtfmbro-mcp Please read the repo to find the rules/prompt file, then: 1. Download it to the correct location (.cursorrules, .windsurfrules, .github/prompts/, or project root — based on the file type) 2. If there's an existing rules file, merge the new rules in rather than overwriting 3. Confirm what was added
Description
rtfmbro provides always-up-to-date, version-specific package documentation as context for coding agents. An alternative to context7
Package Documentation Policy
• Before using any package, module, or library, ALWAYS consult its documentation — your internal knowledge may be outdated and could cause errors or failures. • Don't assume anything about the package's functionality, usage, or configuration without verifying it against the official documentation. • If you are unsure about a user's request that may involve a package, module, or library, ALWAYS refer to the documentation first or ask the user to provide the package name and version.
Workflow
• Don't immediately lookup the user's original codebase. • First, Identify the package name and the EXACT pinned version (eg. "==1.0.5") from the project’s lock file (eg. uv.lock, bun.lock). • Using this information fetch documentation by executing one of the provided tools: • get_readme • get_documentation_tree • read_files • search_github_repositories - Search for Github packages and repositories by topic, language, or keywords. Note, sometimes the documentation is located in a separate repository (like tailwindlabs/tailwindcss.com). Use the repo owner to search for the repo containing the documentation. • Review the documentation carefully to understand: • Core functionality • Usage patterns • Any caveats or special instructions • Reference examples from the documentation to guide your implementation. Ecosystem Selection: • Use pypi for Python packages • Use npm for Node.js packages • Use spm for Swift packages • Use gh only as a fallback for languages not supported by the above registries (package name must be in 'owner/repo' format) or if you're unsure about the package's ecosystem. Also use gh when you don't find the package in the lock file.
Discussion
Health Signals
My Fox Den
Community Rating
Sign in to rate this booster
Works With
Any AI assistant that accepts custom rules or system prompts