RuleStack

Configs

Stacks

Compare

Diff

RuleStack

Configs

Stacks

Compare

Diff

Read API

RuleStack

Configs

Stacks

Compare

Diff

Read API

Configs/.cursorrules/aiurda/devcontext

.cursorrules (deprecated)

.cursorrules
.cursorrulesroot

Quality

65/100

Scores the file, not the repository.

Length

592 words

5 headings · 3 code blocks

Repository

47

— · pushed 430 days ago

Last changed

2 days ago

First indexed 2 days ago.
aiurda/devcontext/.cursorrulesRawGitHub
1# These rules MUST be followed ALWAYS without exception.
2 
3## 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.
4 
5## 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.
6 
7## 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.
8 
9## RULE: External Library Documentation Requirements
10 
11- **ALWAYS Use Context7 Before Using External Libraries**
12 
13 - The agent MUST retrieve and review documentation via Context7 before implementing any code that uses an external library
14 - This applies to ALL libraries not part of the standard language libraries
15 - No exceptions - even for commonly known libraries like React, Express, or Lodash
16 
17- **Two-Step Documentation Retrieval Process**
18 
19```javascript
20 // ✅ DO: ALWAYS follow this exact two-step process
21 // Step 1: Resolve the library name to a Context7-compatible ID
22 const libraryIdResponse =
23 (await mcp_context7_resolve) -
24 library -
25 id({
26 libraryName: "express",
27 });
28 
29 // Step 2: Get the documentation using the resolved ID
30 const docsResponse =
31 (await mcp_context7_get) -
32 library -
33 docs({
34 context7CompatibleLibraryID: libraryIdResponse.libraryId,
35 tokens: 10000, // Adjust based on documentation needs
36 topic: "routing", // Optional: focus on specific area
37 });
38 
39 // ❌ DON'T: Skip the resolution step
40 // ❌ DON'T: Use hardcoded library IDs
41 // ❌ DON'T: Proceed with implementation without review
42```
43 
44- **Never Skip Documentation Retrieval**
45 
46 - Documentation MUST be retrieved even for seemingly simple APIs
47 - Do not rely on previously cached knowledge for current implementations
48 - Never make assumptions about library interfaces, verify with current documentation
49 
50- **Document First, Implement Second**
51 
52```javascript
53 // ✅ DO: Review documentation BEFORE writing implementation code
54 // 1. Identify library need
55 // 2. Retrieve documentation
56 // 3. Review relevant sections
57 // 4. THEN implement solution
58 
59 // ❌ DON'T: Implementation without documentation
60 const app = express(); // WRONG - Documentation not retrieved first
61 app.get("/", (req, res) => res.send("Hello"));
62```
63 
64- **MUST Use Web Search When Documentation Is Unavailable**
65 
66 - If Context7 cannot provide documentation or returns insufficient information, the agent MUST use the web search tool
67 - Always search for the most recent documentation as of mid-2025
68 - Verify the library version against the latest available release
69 
70```javascript
71 // ✅ DO: Fallback to web search when Context7 fails
72 try {
73 // First attempt to use Context7
74 const libraryIdResponse =
75 (await mcp_context7_resolve) -
76 library -
77 id({
78 libraryName: "some-library",
79 });
80 
81 const docsResponse =
82 (await mcp_context7_get) -
83 library -
84 docs({
85 context7CompatibleLibraryID: libraryIdResponse.libraryId,
86 });
87 
88 // Check if documentation is insufficient
89 if (!docsResponse.content || docsResponse.content.length < 100) {
90 throw new Error("Insufficient documentation");
91 }
92 } catch (error) {
93 // If Context7 fails or returns insufficient docs, use web search
94 const webResults = await web_search({
95 search_term: "some-library latest documentation api reference mid 2025",
96 explanation: "Context7 documentation was unavailable or insufficient",
97 });
98 
99 // Analyze multiple search results to get comprehensive information
100 const latestDocs = webResults.filter(
101 (result) =>
102 result.includes("documentation") ||
103 result.includes("api reference") ||
104 result.includes("guide")
105 );
106 
107 // Use these web results to guide implementation
108 }
109 
110 // ❌ DON'T: Skip web search when Context7 fails
111 // ❌ DON'T: Proceed with implementation without documentation
112 // ❌ DON'T: Use outdated web search results (verify they're current as of mid-2025)
113```
114 

Sections

  • 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

What it covers

architecturedo-notagent-behaviourdocs

Stack — with the evidence

vitest

(1.00)

jest

(1.00)

javascript

(0.60)

Format

.cursorrules

Cursor's original single-file format, superseded by .cursor/rules/*.mdc. Tracked here precisely because it is dead: how much of the ecosystem is still shipping a deprecated file is a measurable answer, and a large share of the "best cursor rules" pages on the web still teach this format.

What the corpus says about it

Repository

Owner
aiurda
Language
—
License
—
Archived
no

All configs in this repo

Also in aiurda/devcontext

Diff this repo’s formats

One repository carrying more than one format is the comparison this product exists for: does anyone actually write different content in each file, or is one a copy of the other?

The other instruction files in this repository
RepositoryFormatStackCoversScoreChanged
aiurda/devcontext.cursor/rules/020-tasks-workflow.mdc · 47Cursor rulesvitestjest+1archagent-behaviour58/1002 days ago
aiurda/devcontext.cursor/rules/200-cursor-rules.mdc · 47Cursor rulesvitestjest+1no sections36/1002 days ago
aiurda/devcontext.cursor/rules/010-documentation-context.mdc · 47Cursor rulesvitestjest+1docs40/1002 days ago
Diff against .cursor/rules/020-tasks-workflow.mdc Diff against .cursor/rules/200-cursor-rules.mdc Diff against .cursor/rules/010-documentation-context.mdc

Similar configs

Same format, overlapping stack, ranked by quality.

Same format, overlapping stack, ranked by quality
RepositoryFormatStackCoversScoreChanged
SkeneTechnologies/skene-cookbook.cursorrules · 51.cursorrulespythoneslint+3setuptestlint-formatstyle+1196/1002 days ago
HerringtonDarkholme/megarepo.cursorrules · 17.cursorrulesnodejavascriptsetupbuildtestlint-format+1396/1003 days ago
survivorforge/cursor-rulesrules/devops-docker/.cursorrules · 16.cursorrulesnodejavascriptsetupbuildteststyle+493/1002 days ago
survivorforge/cursor-rulesrules/devops-infrastructure/.cursorrules · 16.cursorrulesnodejavascriptbuildteststylesecurity+393/1002 days ago
survivorforge/cursor-rulesrules/api-microservices/.cursorrules · 16.cursorrulesnodejavascriptbuildteststylearch+592/1002 days ago
fall-out-bug/sdp_lab.cursorrules · 0.cursorrulesgodocker+3setupbuildtestlint-format+386/1003 days ago
bashdeban/fastmind.cursorrules · 5.cursorrulestypescriptnode+8buildtestlint-formattypes+581/1003 days ago
storybookjs/storybook.cursorrules · 91k.cursorrulestypescriptjavascript+6teststylearchdo-not+178/1003 days ago
RuleStack

Built by

Kynth Studio

Directory

Configs
Stacks
Compare formats
Diff two configs
Best AGENTS.md examples

Formats

AGENTS.md
CLAUDE.md
Cursor rules
Copilot instructions

Reference

Read API
Corpus health
Privacy Policy
Terms

RuleStack

RuleStack

Built by

Kynth Studio

Directory

Configs
Stacks
Compare formats
Diff two configs
Best AGENTS.md examples

Formats

AGENTS.md
CLAUDE.md
Cursor rules
Copilot instructions

Reference

Read API
Corpus health
Privacy Policy
Terms

RuleStack

RuleStack

Built by

Kynth Studio

Directory

Configs
Stacks
Compare formats
Diff two configs
Best AGENTS.md examples

Formats

AGENTS.md
CLAUDE.md
Cursor rules
Copilot instructions

Reference

Read API
Corpus health
Privacy Policy
Terms

RuleStack