Always-Current Package Documentation

Forces GitHub Copilot to consult real-time, version-specific package documentation before using any library, module, or package. Prevents errors from outdated internal knowledge by integrating with rtfmbro-mcp for always-current documentation context.

Instructions

Package Documentation Policy

**Critical Rule:** Before using ANY package, module, or library, ALWAYS consult its documentation. Your internal knowledge may be outdated and could cause errors or failures.

Required Workflow

Follow this sequence EVERY time you work with external dependencies:

**0. Pause First**

**1. Identify Package Version**

- Python: `uv.lock`, `poetry.lock`, `Pipfile.lock`

- Node.js: `package-lock.json`, `yarn.lock`, `bun.lock`

- Swift: `Package.resolved`

**2. Fetch Documentation**

Execute one of these tools based on the package ecosystem:

**Ecosystem Selection:**

**Note:** Documentation may live in a separate repository (e.g., `tailwindlabs/tailwindcss.com`). Use the repo owner to search for documentation repos.

**3. Review Thoroughly**

Study the documentation to understand:

**4. Reference Examples**

Use code examples from the documentation to guide your implementation. Don't improvise when examples exist.

Why This Matters

**Common Issues Prevented:**

Example Usage

**Bad (Old Behavior):**

```

User: "Add authentication with next-auth"

Copilot: *immediately writes code from memory*

Result: Uses outdated v4 API in a v5 project → runtime errors

```

**Good (With This Skill):**

```

User: "Add authentication with next-auth"

Copilot:

1. Checks package-lock.json → finds "next-auth": "5.0.0-beta.4"

2. Executes get_readme with ecosystem=npm, package=next-auth

3. Reviews v5 breaking changes (App Router support, new callbacks)

4. References v5 migration guide examples

5. Writes correct implementation

Result: Clean, working code on first try

```

Integration Requirements

This skill requires the rtfmbro-mcp server to be installed and configured:

```bash

Install rtfmbro-mcp

npm install -g rtfmbro-mcp

Configure in Copilot settings (follow rtfmbro setup guide)

```

Constraints

Best Practices

1. **Always check lock files first** - Don't rely on package.json or requirements.txt for version info

2. **Read changelogs for major version jumps** - Breaking changes are often documented separately

3. **Verify deprecation warnings** - Many packages announce deprecations before removal

4. **Cross-reference multiple sources** - READMEs, official docs, and migration guides all provide value

5. **Update your mental model** - If documentation contradicts what you "know," trust the docs

Troubleshooting

**"Package not found in lock file"**

**"Documentation repository not found"**

**"Conflicting information between sources"**