Sheela
Sheela
Home
Add
Questions
Thinkers
Claims
People
Concepts
Jargon
Sources
Health
Predictions
Collections
Domain Landscape
Contribute
Review
Dedup
Topic requests
Settings
Help

← Jargon

Jargonsoftware engineering· 2 claims· 1 episode

Rules (cursor rules / windsurf rules)

Persistent natural-language instruction files (MDC files in a .cursor/rules folder) that tell the agent how to code, which technologies and workflows to use—functioning like a system message.

As defined in Vibe Coding Tutorial and Best Practices (Cursor / Windsurf)


Where it comes up · 1
  • Vibe Coding Tutorial and Best Practices (Cursor / Windsurf)2 claims

Most important claims · 2 of 2Search all claims for “Rules (cursor rules / windsurf rules)” →
  • Using cursor/windsurf rules files (project-level natural-language instructions) to dictate how the agent codes, which technologies to use, and which workflows to follow is critical—especially as the codebase grows—because the agent otherwise introduces technologies not in your spec and breaks other things when fixing bugs.Vibe Coding Tutorial and Best Practices (Cursor / Windsurf)
  • You should specify your technical stack explicitly in the rules (e.g., Python backend, HTML/JS frontend, SQL database never JSON file storage, hosted Elasticsearch) because the agent otherwise defaults to alternatives like JSON file storage or local services that you didn't want.Vibe Coding Tutorial and Best Practices (Cursor / Windsurf)