The code looks convincing at first glance, but when run, the API doesn’t exist at all. This kind of rework sometimes happens when AI accidentally injects outdated code patterns into a new project. Context7 addresses the step of researching: it equips the Coding Agent with relevant library documentation and code examples, supporting version-specific retrieval. The tool fetches documentation, while the accompanying Skill teaches the Agent when and how to search. It does not guarantee code correctness. Ensure you have Node.js 18 or higher installed, then run in your terminal: node --version npx ctx7 setup Follow the prompts to log in, select your Coding Agent, and choose either CLI + Skills or MCP integration. Start by configuring only the Agent you’re currently using—don’t install all at once. After setup, use an existing Next.js test project for a small task: “First, read package.json and the lock file to confirm the actual Next.js version being used in the project. Use context7 to query how dynamic route params should be accessed for this version, and whether await is required. Output: The actual version; The retrieved documentation link; A minimal code example. Do not modify the project yet. If no matching version is found, clearly state so—do not substitute code from another version.” First, verify whether the reported version matches your project, then open the documentation to validate the example. I prefer to do this step before writing any code. Aligning the version upfront is far more reliable than letting AI guess after an error occurs. ⚠️ Documentation coverage and version matching are not always complete; queries are sent to external services—never include keys, customer data, or sensitive information in your search queries. https://t.co/aTvOqHJWmp