no-emoji
Skill0 starsChanged 43 days agoMITView on GitHub
Standards prohibiting emojis and decorative unicode symbols, with solutions using plain text, status badges, and inline SVG icons.
In this repository8 other files it gives its agents.
- skills/project-starter/template/AGENTS.mdAGENTS.md
- commit-nyancodeidSkill
- dealtech-uiSkill
- devflow-orchestratorSkill
- humanize-writingSkill
- impeccable-designSkill
- ponytail-leanSkill
- project-starterSkill
The file
Files
No Emoji
This skill enforces strict rules against the use of emojis and decorative unicode characters across codebases, user interfaces, documentation, branch names, and commit messages.
Scope of Restriction
Emojis and decorative symbols must not be used in:
- User Interfaces: Headings, body text, form placeholders, badges, toasts, alerts, and empty states.
- Code and Attributes:
alt,title,aria-label, function names, variable identifiers, code comments, and terminal log outputs. - Documentation and Repository: README files, PR descriptions, commit messages, and filenames.
Characters such as unicode checkmarks, crosses, decorative stars, or symbol arrows are also prohibited when used as makeshift UI icons.
Recommended Alternatives
| Visual Requirement | Applied Alternative |
| Navigation / Action icons | Inline SVG (<svg>) or project icon libraries (Lucide, Heroicons). See examples in references/svg-icons.md. |
| Status indicators (success / error) | Text-based badges ("Success", "Failed", "Pending") with appropriate CSS styling. |
| Detail lists | Standard Markdown bullet points (-) or HTML <ul> / <li> elements. |
| Progress indicators | Descriptive status text ("Loading data...") or CSS animation spinners. |
Exceptions
Emojis are permitted only under these specific conditions:
- The user explicitly requests specific emojis.
- The text displays raw, dynamic user-generated content from database storage.
- Legacy files already employ emojis consistently and the current task is not style normalization.
Verification
To check files in a Windows PowerShell environment:
Select-String -Path .\path\to\file -Pattern '[\p{Cs}\u2190-\u27BF\u2B00-\u2BFF\uFE0F]'Or using ripgrep:
rg -n '[\x{1F300}-\x{1FAFF}\x{2190}-\x{27BF}\x{2B00}-\x{2BFF}\x{FE0F}]' .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.