prompt-decorators / rules
Cursor rule44 starsChanged 20 months agoApache-2.0View on GitHub
Use emojis strategically in AI responses to enhance communication and user experience
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 repository6 other files it gives its agents.
- .cursor/rules/000-cursor-rules.mdcCursor rule
- .cursor/rules/050-careful-code-modification.mdcCursor rule
- .cursor/rules/060-coding-patterns.mdcCursor rule
- .cursor/rules/070-workflow-preferences.mdcCursor rule
- .cursor/rules/400-md-docs.mdcCursor rule
- .cursor/rules/900-software-dev-decorators.mdcCursor rule
The file
We split this 001-emoji-communication.mdc into the rules it gives an agent
8 rules. About 0 are common, 8 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
When responding to user queries in conversations
- Distinctive: line 11
When emphasizing important points or status updates
- Distinctive: line 12
When making technical communication more engaging and human-friendly
- Distinctive: line 15
Use emojis purposefully to enhance meaning, but feel free to be creative and fun
- Distinctive: line 16
Place emojis at the end of statements or sections
- Distinctive: line 35
Never use more than one emoji per statement
- Distinctive: line 37
Place emojis at the end of statements, not at the beginning or middle
- Distinctive: line 39
Don't be afraid to tell a mini-story with your emoji choice
≈ “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.
Files
--- description: Use emojis strategically in AI responses to enhance communication and user experience globs: null alwaysApply: true --- # Emoji Communication Guidelines ## Context - When responding to user queries in conversations - When emphasizing important points or status updates - When making technical communication more engaging and human-friendly ## Requirements - Use emojis purposefully to enhance meaning, but feel free to be creative and fun - Place emojis at the end of statements or sections - Maintain professional tone while surprising users with clever choices - Limit emoji usage to 1-2 per major section ## Examples <example> ✅ "I've optimized your database queries 🏃♂️💨" ✅ "Your bug has been squashed 🥾🐛" ✅ "I've cleaned up the legacy code 🧹✨" ✅ "Fixed the performance issue 🐌➡️🐆" </example> <example type="invalid"> ❌ "Multiple 🎉 emojis 🎊 in 🌟 one message" ❌ "Using irrelevant emojis 🥑" ❌ "Placing the emoji in the middle ⭐️ of a sentence" </example> ## Critical Rules - Never use more than one emoji per statement - Choose emojis that are both fun and contextually appropriate - Place emojis at the end of statements, not at the beginning or middle - Skip emoji usage when discussing serious issues or errors - Don't be afraid to tell a mini-story with your emoji choice
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
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.

