From edbae02a91e7e5964f88f2fcceeaf272c4c0e6b1 Mon Sep 17 00:00:00 2001 From: lance2k Date: Sun, 15 Feb 2026 07:04:00 +0800 Subject: [PATCH] Update instructions/context7.instructions.md Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- instructions/context7.instructions.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/instructions/context7.instructions.md b/instructions/context7.instructions.md index 43fb340d..da377caf 100644 --- a/instructions/context7.instructions.md +++ b/instructions/context7.instructions.md @@ -65,17 +65,17 @@ When Context7 is available as an MCP server, use it automatically as follows. ### Tool workflow 1) **If the user provides a library ID**, use it directly. - - Valid forms: `/owner/repo` or `/owner/repo/version` (for pinned versions). + - Valid forms: `/owner/repo` or `/owner/repo/version` (for pinned versions). 2) Otherwise, **resolve the library ID** using: - - Tool: `resolve-library-id` - - Inputs: + - Tool: `resolve-library-id` + - Inputs: - `libraryName`: the library/framework name (e.g., “next.js”, “supabase”, “prisma”) - `query`: the user’s task (used to rank matches) 3) **Fetch relevant documentation** using: - - Tool: `query-docs` - - Inputs: + - Tool: `query-docs` + - Inputs: - `libraryId`: the resolved (or user-supplied) library ID - `query`: the exact task/question you are answering