⛷🦖🦅😙🥚🥑🤗🥦🤣🐼🏄🦊🎟🥩🧈🍠🎪🍕😫🐶🐝😠🧐🫓🤿🐷🍗😨🪂🧀
🥍😊😞🐞😭🦂🫑🏐🥨😀😩🦇🐆🍈🥉🎭😝🐧🦓🥖😡🤺🍏🐢🦎🐅🎫🥏🐺😛
🐋😥🥐🍖😁😤🫔🎨🥪🌭🐊😓🦗😰🎬🥵🍳🦕🌮🍌🍊🐭🦞😕🍇🐸🏉🐳🥈🤩

emoji-proposals

Skills for proposing a new emoji to the Unicode Consortium — from finding an idea worth pursuing, through writing and reviewing the proposal document, to submission.

Start by reading the official guidelines: https://unicode.org/emoji/proposals.html. That page defines the selection factors, the required document format, and the current submission window, and it is the source of truth for everything below. Every skill in this plugin re-fetches it at the start of a run; where this plugin and the live page disagree, the live page wins.

How emoji proposals work

New emoji are approved by the Unicode Emoji Subcommittee, which accepts proposals from anyone during defined submission windows. A proposal is a single PDF document, hosted at a public URL and submitted through the official form. It must contain:

• A descriptive name, keywords, proposed category, and sort location
• Example images in color and flat black-and-white, at 72×72 and 18×18 pixels, with a statement of the image license
• Evidence of expected usage: screenshots and cited figures from five sources (Google Search, Google Video Search, Google Trends web and image search, and Google Books Ngram Viewer), with "elephant" included in the comparative charts as a common reference term
• An argument addressing every inclusion factor (multiple meanings, use in sequences, breaks new ground, distinctiveness, usage level, completeness, compatibility) and every exclusion factor (already representable, overly specific, open-ended, transient, faulty comparison)

Some categories are declined automatically — brands, logos, UI icons, signage, specific people, deities, flags without region codes, designs containing text, requests for an exact image. Petitions and social-media campaigns carry no weight; only usage evidence does. Concepts that have been declined are ineligible for re-review for four years, and acceptance rates are low — most proposals fail on "already representable" or "overly specific". The process from submission to a shipped emoji, when it succeeds, takes roughly two years.

The skills

/emoji-ideas  →  /draft-proposal  →  /proposal-review  →  submit

/emoji-ideas

Finds a concept worth proposing. Brainstorms candidates from your own usage gaps and from gaps in the current emoji set, then runs each through a validation ladder ordered cheapest-first: the automatic-decline screen, the current emoji list, the Emoji Requests backlog (including the four-year rule for declined concepts), a Google Books Ngram check for staying power, and a gut check against each selection factor. Each candidate gets a verdict — pursue, reshape, or drop — and one survivor is recommended for the next step.

/draft-proposal

Turns a validated idea into a submission-ready PDF. It interviews you first, so the document is written from your own words and experiences; captures the five required evidence screenshots with Claude for Chrome (your real signed-in browser — Google Trends rate-limits anonymous automation); generates the example images as emoji-style SVGs, iterating until the concept is legible at 18×18; and builds the final PDF along with a checklist of the remaining manual submission steps.

/proposal-review

Reviews a finished proposal (PDF or HTML) against the selection criteria before you submit. It renders each page to an image and inspects it visually, verifies the document structure and image requirements, re-runs the Books Ngram figures and checks the Emoji Requests list, and argues every inclusion and exclusion factor from the position of a skeptical reviewer. The output is a verdict — ready to submit, needs revision, or likely decline — with a factor-by-factor scorecard and fixes ordered by impact.

Requirements

• Claude for Chrome (connect with /chrome in Claude Code), signed into Google — needed for the evidence screenshots
• Google Chrome on disk — used headless for SVG rasterization and PDF building
• poppler (brew install poppler) — used by the reviewer to inspect PDF pages