File size: 2,134 Bytes
0f62534
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
# Implementation Notes
- IT S VERY IMPORTANT CRITICAL
For developers working on this enhancement, the Context7 MCP will be used to fetch up-to-date documentation This will ensure the implementation uses the most current APIs and best practices.Use it and the tools associated to it, use it in testing phase too 
- WHEN using context7 and you dont found what you re looking search the base name of the library first 
- context7 - Ready (2 tools)
    Tools:
    - get-library-docs:
        Fetches up-to-date documentation for a library. You must call 
  'resolve-library-id' first to obtain the exact Context7-compatible 
  library ID required to use this tool, UNLESS the user explicitly 
  provides a library ID in the format '/org/project' or 
  '/org/project/version' in their query.
    - resolve-library-id:
        Resolves a package/product name to a Context7-compatible library     
  ID and returns a list of matching libraries.

        You MUST call this function before 'get-library-docs' to obtain a    
   valid Context7-compatible library ID UNLESS the user explicitly
  provides a library ID in the format '/org/project' or
  '/org/project/version' in their query.

        Selection Process:
        1. Analyze the query to understand what library/package the user     
  is looking for
        2. Return the most relevant match based on:
        - Name similarity to the query (exact matches prioritized)
        - Description relevance to the query's intent
        - Documentation coverage (prioritize libraries with higher Code      
  Snippet counts)
        - Trust score (consider libraries with scores of 7-10 more
  authoritative)

        Response Format:
        - Return the selected library ID in a clearly marked section
        - Provide a brief explanation for why this library was chosen        
        - If multiple good matches exist, acknowledge this but proceed       
  with the most relevant one
        - If no good matches exist, clearly state this and suggest query     
  refinements

        For ambiguous queries, request clarification before proceeding       
  with a best-guess match.