Skip to content

maddevsio/shared_cursor_rules

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

6 Commits
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Developed by Mad Devs

Cursor Rules Templates

These templates are based on awesome-cursorrules

Structure

📁 generic - general rules for any tech stack

  • 📁 must-have - mandatory rules for all company projects
  • 📁 optional - optional rules, use as needed

📁 specific - examples for specific tech stacks

📁 project-rules - examples of rules for individual projects

📁 user-rules - examples of personal rules (apply to all your projects)


Quick start

  1. Copy rules from generic/must-have and selectively from generic/optional and specific
  2. Paste them into .cursor/rules of your project
  3. Customize the rules for your project:
    • Rules from generic/must-have can be adapted, but it's important to preserve their essence. For us, it's crucial that all company projects are based on unified principles.
    • Rules from generic/optional and specific can be completely changed
  4. Don't hesitate to ask AI to adapt the rules for your project
  5. Study project-rules and create custom rules for your project
  6. Check out user-rules and create personal rules (they are added to Cursor settings → Rules → User rules)

Example prompts for implementing Cursor rules

For familiarizing with rules

Read all rules in the `.cursor/rules` directory and confirm that you understand them.
Briefly summarize the essence of each rule and how you will apply them in your work.
Confirm that you will never ignore these rules.

For adapting rules to a project

Study the rules in `.cursor/rules/{rule}` and adapt them for the project [your project description].
Consider that we use [your tech stack], and the team consists of [team description].
It's important to preserve the essence of must-have rules, but they can be improved.

For creating custom project rules

Create rules for the project considering the following features:
1. Tech stack: [your stack]
2. Architecture: [architecture description]
3. Main problems we want to solve: [problems]
4. Our core values in code: [values]
5. Approach to task execution: [typical action algorithm]

For creating personal rules

Help create personal rules for the AI agent considering my work style:
1. I prefer [your programming preferences]
2. Often work with [technologies/libraries]
3. It's important for me that code is [your code priorities]
4. Usually face difficulties with [problem areas]
5. What should NEVER be done [prohibitions]

Setting priorities

To change the rule application mode:

  1. Open the rule file
  2. Click on the dropdown Rule type
  3. Select the appropriate option

Tips for effective rules:

✅ Use a small number of rules
✅ Keep files short (up to 100 lines)
✅ Avoid contradictions between rules
✅ Set Rule type: Always only for critically important rules
✅ At the beginning of the chat, ask AI to read the rules and summarize their essence


If AI ignores the rules, it means there are too many of them or they are not effectively written.

Found a way to improve the rules? Make a PR, we'll be happy ❤️

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published