devcontext: Cursor rule for Cursor

These rules MUST be followed ALWAYS without exception.

RULE: You are an agent - please keep going until the user’s query is completely resolved, before ending your turn and yielding back to the user. Only terminate your turn when you are sure that the problem is solved.

RULE: If you are not sure about file content or codebase structure pertaining to the user’s request, use your tools to read files and gather the relevant information: do NOT guess or make up an answer.

RULE: You MUST plan extensively before each function call, and reflect extensively on the outcomes of the previous function calls. DO NOT do this entire process by making function calls only, as this can impair your ability to solve the problem and think insightfully.

RULE: External Library Documentation Requirements

• ALWAYS Use Context7 Before Using External Libraries

  • The agent MUST retrieve and review documentation via Context7 before implementing any code that uses an external library
  • This applies to ALL libraries not part of the standard language libraries
  • No exceptions - even for commonly known libraries like React, Express, or Lodash

• Two-Step Documentation Retrieval Process

  // ✅ DO: ALWAYS follow this exact two-step process
  // Step 1: Resolve the library name to a Context7-compatible ID
  const libraryIdResponse =
    (await mcp_context7_resolve) -
    library -
    id({
      libraryName: "express",
    });
  
  // Step 2: Get the documentation using the resolved ID
  const docsResponse =
    (await mcp_context7_get) -
    library -
    docs({
      context7CompatibleLibraryID: libraryIdResponse.libraryId,
      tokens: 10000, // Adjust based on documentation needs
      topic: "routing", // Optional: focus on specific area
    });
  
  // ❌ DON'T: Skip the resolution step
  // ❌ DON'T: Use hardcoded library IDs
  // ❌ DON'T: Proceed with implementation without review
  

• Never Skip Documentation Retrieval

  • Documentation MUST be retrieved even for seemingly simple APIs
  • Do not rely on previously cached knowledge for current implementations
  • Never make assumptions about library interfaces, verify with current documentation