Global Cursor rules - language and punctuation
Recently I wrote an article about Cursor, its features and configuration available here: Cursor – complete guide to AI agent capabilities and configuration.
Today a short note with examples of general rules.
Where to place the rules
Create the ~/.cursor/rules/ directory and place .mdc files there. These rules work globally across all projects.
Rule 1 — Polish language in conversations
A lazy rule — well, since we communicate with the agent in natural language, why not make it even more natural?
Create file: ~/.cursor/rules/polish-language.mdc
Snippet on Bitbucket: Cursor - rule for Polish in conversation
Content:
---
description: Always respond in Polish unless told otherwise.
alwaysApply: true
---
# Język komunikacji
Zawsze komunikuj się ze mną po polsku — w odpowiedziach, pytaniach, wyjaśnieniach i wszelkich wiadomościach tekstowych skierowanych do mnie.
Wyjątek: jeśli użytkownik wyraźnie poprosi o inny język, przełącz się na niego.
Nie dotyczy to kodu, nazw zmiennych, komentarzy w kodzie ani treści generowanej do plików — tam stosuj zasady właściwe dla danego języka programowania.
Rule 2 — English code comments
Regardless of the language I use to communicate with the agent — comments and docstrings should always be written in English.
Create file: ~/.cursor/rules/english-code-comments.mdc
Snippet on Bitbucket: Cursor - rule that code comments in all programming languages must be in English
Content:
---
description: Code comments in all programming languages must be in English.
alwaysApply: true
---
# Code Comments Language
All comments in any programming language must be written in English.
This applies to:
- Inline comments (`# comment`, `// comment`, `-- comment`, etc.).
- Block comments (`/* ... */`, `""" ... """`, etc.).
- Docstrings and documentation blocks.
- Robot Framework documentation (`[Documentation]`, `Documentation:`).
- Any other form of in-code annotation.
Do NOT write comments in Polish or any other language — English only.
Rule 3 — punctuation in texts and lists
Personally, missing periods at the end of sentences or in lists irritates me quite a lot, so I decided to handle that with a rule as well.
Create file: ~/.cursor/rules/punctuation-rules.mdc
Snippet on Bitbucket: Cursor - rule for punctuation in texts, docstrings, descriptions and bullet lists
Content:
---
description: Punctuation rules for texts, docstrings, descriptions and bullet lists.
alwaysApply: true
---
# Punctuation Rules
## Sentences in texts
Every sentence in any written text (docstrings, descriptions, articles, comments, documentation) must end with a period. Section headings are the only exception.
## Bullet lists
Apply punctuation based on the nature of the list items:
**1. Full sentences (each item is a standalone sentence)**
- Start each item with a capital letter.
- End each item with a period.
- Use this form for longer, complex descriptions.
**2. Short phrases continuing an introductory sentence**
If items complete or continue a lead-in sentence (items start with a lowercase letter), end each item with a comma or semicolon, and the last item with a period.
Example — "To prepare the dough you need:":
- wheat flour,
- fresh yeast,
- warm milk.
**3. Short keyword lists (no punctuation)**
Omit punctuation entirely when the list consists of standalone short keywords or labels that are not part of a sentence (e.g. a shopping list, a tag list, a feature list).
Example:
- bread
- milk
- butter