alexeyleshchenkoalexeyleshchenko/fast-mcp-telegram/.cursor/rules/general.mdc

fast-mcp-telegram / rules

Cursor rule2 starsChanged 4 months agoMITView on GitHub

You are running in Cursor IDE. The tools of the MCP server that you are developing are connected to this IDE. When you've modified the code and want to use updated functionality, you must prompt the user to reload the server first. All comments, docstrings, and documentation must be in English only. Do not use any other non-English language in code comments, docstrings, or documentation. Always use the DRY principle. Always check today's date with shell command date when inserting…

1 other project uses a version of this.

Adopted by

Most recently taken up by

leshchenko1979/fast-mcp-telegramword for word, first seen Jul 28, 2026

Other versions1 project uses a version of this.
Word for word · 1
leshchenko1979/fast-mcp-telegram★ 50100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.
Of the Cursor rule files we read, the 4,157 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository11 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .cursor/rules/code-optimization.mdcCursor rule
- .cursor/rules/docs-plain-language.mdcCursor rule
- .cursor/rules/implementation-workflow.mdcCursor rule
- .cursor/rules/memory-bank.mdcCursor rule
- Clean Up Docs PushSkill
- feature-developmentSkill
- Release Notes GenerationSkill
- Remove Old LogsSkill
- sourcery-pr-cycleSkill
- telegram-patternsSkill

The file

We split this general.mdc into the rules it gives an agent

5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Distinctive:
When you've modified the code and want to use updated functionality, you must prompt the user to reload the server first.
line 7
Distinctive:
All comments, docstrings, and documentation must be in English only.
line 10
Distinctive:
Always use the DRY principle.
line 12
Very specific:
Always check today's date with shell command date when inserting current date.
line 14
Distinctive:
When you modify code, ask the user to restart the server in Cursor's MCP panel.
line 19

≈ “Common” is an estimate: at least 1 in 5 of the 6,668 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

general.mdc

---
description:
globs:
alwaysApply: true
---
You are running in Cursor IDE. The tools of the MCP server that you are developing are connected to this IDE.
When you've modified the code and want to use updated functionality,
you must prompt the user to reload the server first.

All comments, docstrings, and documentation must be in English only. Do not use any other non-English language in code comments, docstrings, or documentation.

Always use the DRY principle.

Always check today's date with shell command `date` when inserting current date.

## Testing with telegram-dev MCP

This project has a `telegram-dev` MCP server configured in `.cursor/mcp.json`.
When you modify code, ask the user to restart the server in Cursor's MCP panel.
See [CONTRIBUTING.md](CONTRIBUTING.md) for setup instructions.

## Releases

For release, version bump, tag, `gh release`, or publish requests, read and follow [`.cursor/skills/release-notes/SKILL.md`](../skills/release-notes/SKILL.md) in full before changing versions or publishing.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free