- Notifications
You must be signed in to change notification settings - Fork0
maddevsio/shared_cursor_rules
Folders and files
| Name | Name | Last commit message | Last commit date | |
|---|---|---|---|---|
Repository files navigation
These templates are based onawesome-cursorrules
Therules directory contains ready-to-use cursor rules.
📁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)
Theprompt-templates directory contains ready-to-use prompts
- 📁rules - prompts to help create, adapt, and work with rules
- 📁documentation - prompts to help generate documentation
- 📁other
- Copy and paste
- Customize placeholders like
[your tech stack]with your specific information - Refine as needed
These prompts serve as starting points to help you get the most out of LLM
- Copy rules from
generic/must-haveand selectively fromgeneric/optionalandspecific - Paste them into
.cursor/rulesof your project - Customize the rules for your project:
- Rules from
generic/must-havecan 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/optionalandspecificcan be completely changed
- Rules from
- Don't hesitate toask AI to adapt the rules for your project
- Study
project-rulesand create custom rules for your project - Check out
user-rulesand create personal rules (they are added toCursor settings → Rules → User 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.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.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]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]Write a clear, concise README for this project that follows industry best practices and includes:1. Project title and brief description (1-2 sentences)2. Problem the project solves3. Key features (bullet points)4. Technologies/frameworks used5. Installation instructions with prerequisites and step-by-step setup6. Basic usage examples with code snippets7. Project structure overview (only key directories/files)8. Configuration options9. Contribution guidelines (if applicable)10. License information11. Credits/acknowledgmentsTo change the rule application mode:
- Open the rule file
- Click on the dropdown
Rule type - Select the appropriate option
✅ Use a small number of rules
✅ Keep files short (up to 100 lines)
✅ Avoid contradictions between rules
✅ SetRule 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
Resources
Uh oh!
There was an error while loading.Please reload this page.
Stars
Watchers
Forks
Releases
Packages0
Contributors2
Uh oh!
There was an error while loading.Please reload this page.