What Context7 adds
Context7 gives Work a reference path for actual public library documentation. It is useful when a website task depends on supported framework behavior, routing, forms, authentication, webhooks, testing, accessibility or deployment concepts.
This connection is read-only. It does not install packages, edit the customer’s source, execute examples, authorize a deployment or inspect every private project file. Those are separate tasks with separate connections and approvals.
Connect the public libraries you need
- Open Connections and choose Context7 when it is available in your workspace’s authorized provider catalog.
- Choose explicit public access or provide your own optional API key through the secure form.
- Select the public library IDs appropriate to the task.
- Verify the connection and ask a focused documentation question for one of those libraries.
Ask for reference, then apply judgment
Use the selected Context7 library to explain the documented routing approach relevant to our website task. Summarize the source guidance and what project information is still needed. Do not edit files, install packages or deploy.
The Work adapter sends a fixed public documentation question for the selected topic; it does not use the connection to upload private customer code or records. Do not paste secrets or private implementation details into a public reference request.
Compare the reference with the project
Ask Work to distinguish “the documentation says” from “the repository currently does.” A recommendation may depend on a library version, configuration or adapter not present in the selected website. Inspect those facts through the authorized source connection before proposing a change.
Even accurate reference code needs review and testing in the actual project. A page claiming a feature exists is not proof that your deployment is configured to use it.
When the documentation is unavailable
Check the selected libraries, connection state and public or personal-plan query limits. Use the provider’s primary documentation directly when necessary. Work should state that a source read failed rather than describe remembered guidance as a newly verified result.
Instructions in documentation are examples and reference content. They cannot authorize credential disclosure, bypass platform approvals or change which customer repository is selected.