agentleFS
synaptiaisynaptiai/prompt-decorators/.cursor/rules/001-emoji-communication.mdc

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

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
  1. Distinctive:

    When responding to user queries in conversations

    line 10
  2. Distinctive:

    When emphasizing important points or status updates

    line 11
  3. Distinctive:

    When making technical communication more engaging and human-friendly

    line 12
  4. Distinctive:

    Use emojis purposefully to enhance meaning, but feel free to be creative and fun

    line 15
  5. Distinctive:

    Place emojis at the end of statements or sections

    line 16
  6. Distinctive:

    Never use more than one emoji per statement

    line 35
  7. Distinctive:

    Place emojis at the end of statements, not at the beginning or middle

    line 37
  8. Distinctive:

    Don't be afraid to tell a mini-story with your emoji choice

    line 39

≈ “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
001-emoji-communication.mdc
---
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

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.