Forem: yamadashy

Letting Claude Code's Routines continuously tune my CLI's performance

yamadashy — Thu, 30 Apr 2026 14:45:49 +0000

I had been thinking about what to actually do with Claude Code's Routines feature for a while.
It runs prompts in the cloud on a schedule, which sounds useful, but what's actually worth firing every couple of hours?

What I landed on is performance tuning.
"Did it get faster?" is a question you can answer with numbers, so as long as you have a benchmark in place, the rest can be handed off to an AI. If you have tests, regressions get caught for you. The work happens on a branch, so nothing leaks into main. And a lot of perf wins are "patterned" changes — swapping a dependency, lazy-loading something, cutting an I/O — that don't really need much creative design.

I tried this on Repomix, the CLI I maintain, and the runtime ended up roughly 2.4x faster.

v1.14.0 release notes

It's reproducible enough now that I think it's worth sharing. Below is the prompt I'm using and the benchmark setup that makes it tick.

What Routines are

Claude Code has a feature called Routines that runs prompts in the cloud on a schedule. Point it at a GitHub repository and it pushes results to a branch automatically. Unlike /loop, which runs locally, this keeps going even when you close your laptop.

Routines docs

The setup

You configure Routines from the web UI at claude.ai/code/routines. Mine runs on a 2-hour cron.

Here's the prompt I have registered:

# Automated Performance Tuning

Perform performance improvement work.

## Settings

- Working branch: `perf/auto-perf-tuning`
- Base branch: `main`
- Target folder: `src`
- PR title: `perf(core): Automated performance tuning by Claude`
- Improvement threshold: `For a CLI run that takes 1–2 seconds, ignore changes of a few ms; require at least a 2% reduction in total execution time`
- Number of investigation sub-agents: `5`
- Sub-agent model: `sonnet`

## Policy

Improve the performance, or reduce memory usage, of <Target folder> and related code (tests, config, dependencies).
Aim for measurable, impactful changes based on <Improvement threshold>.
Do not make functional changes. Improve performance only, keeping existing behavior intact.

## Progress checklist

- [ ] 1. Branch preparation
- [ ] 2. Check existing PR
- [ ] 3. Investigation & planning
- [ ] 4. Implementation
- [ ] 5. Benchmark & verification
- [ ] 6. Commit
- [ ] 7. Local review
- [ ] 8. Create / update PR

## Steps

### 1. Branch preparation

- If <Working branch> does not exist, create it from the latest <Base branch>. If it exists, check it out.
- Then, if <Base branch> is ahead of <Working branch>, merge <Base branch> in and push. If conflicts occur, resolve them keeping in mind that the corresponding change may have already been picked up elsewhere.

### 2. Check existing PR

- Check whether a PR for <Working branch> already exists.
- If it does, read the PR description and review comments to grasp the context.

### 3. Investigation & planning

First, understand the repository structure and processing flow. Then define <Number of investigation sub-agents> non-overlapping investigation scopes yourself, and launch sub-agents (model: <Sub-agent model>) for each scope in parallel. Aggregate all reports and form an improvement plan.

Choose scopes freely based on the repository's characteristics. Examples:
- Critical path identification (locating bottlenecks)
- I/O & external communication (redundant reads, sync I/O, buffer sizes)
- Data structures & algorithms (complexity, string operations, collection choice)
- Parallelization & async (serialized work that could parallelize, redundant sequential awaits)
- Dependency libraries & init cost (lighter alternatives, lazy loading)

Even if multiple improvements are found, pick only one. Focus on the single highest-impact change for this run.

If no improvement meeting <Improvement threshold> is found, report findings and end the run.

### 4. Implementation

Implement the plan.

### 5. Benchmark & verification

- Run the benchmark and confirm the change meets <Improvement threshold>.
- Then run lint and test, confirming no regressions.
- If <Improvement threshold> is not met, revert the changes and report findings.

### 6. Commit

- Commit with the `perf` prefix.
- Include the change description and benchmark results in the commit body.

### 7. Local review

- Have multiple sub-agents review locally. If issues are raised, fix them and review again. Use amend so the work stays as a single commit.
- Once no more fixes remain, push.

### 8. Create / update PR

- Update the PR if it already exists, otherwise create a new one.
- Create as Draft.
- Title: <PR title>
- Add the change description and benchmark results to the PR body.

A few things I care about in this prompt:

The settings section is at the top with placeholders, so I can drop the prompt into another repo and just edit the variables.
One run = one improvement. This is the rule I'm strictest about. Multiple changes in one run and you can't tell which one actually moved the needle.
The investigation runs 5 sub-agents in parallel, each with a different scope (I/O, memory, dependency weight, etc.). One agent looking at everything tends to be too narrow. I use Sonnet for sub-agents to keep cost in check.
If nothing meets the improvement threshold, the run reverts and exits. No filler commits.
Sub-agents review locally before push, so I don't burn CI on obvious issues.
Everything stacks into one PR (perf/auto-perf-tuning). Having a fresh PR every time would be annoying.

How the measurement works

Inside the routine, Claude Code writes the benchmark on the fly and only commits if the result clears the threshold.

I also have a separate benchmark that runs on every PR, mostly for my own eyes:

perf-benchmark.yml

Roughly what it does:

Checks out the PR branch and main into separate directories and builds both
Measures pack time on Ubuntu / macOS / Windows (run counts tuned per OS)
Posts the diff back to the PR as a comment

The multi-OS bit is to avoid being fooled by environment-specific wins.

Since the routine stacks all its commits onto a single perf/auto-perf-tuning PR, the benchmark history naturally accumulates in that PR's comments:

I also wanted a longer-running view of main, so on every push to main the same benchmark runs and the result is saved to gh-pages via github-action-benchmark.

perf-benchmark-history.yml

The graph is public:

https://yamadashy.github.io/repomix/dev/bench/

You can read off the staircase-shaped drops, the occasional plateau, and a few sudden cliffs. I find it surprisingly fun to look at. It also makes it pretty obvious that this kind of work is something that pays off as accumulation, not as one big PR.

How changes actually land in main

The routine drops commits onto perf/auto-perf-tuning, which has a Draft PR sitting against it.

https://github.com/yamadashy/repomix/pull/1514

I look at the per-commit benchmark in the PR's comments, find the commits that look promising, and ask Claude Code (in a separate, local session) to "re-implement this from main and open a PR." That goes back through the normal review path.

I don't merge the routine's PR directly. Sometimes a regression sneaks in. Sometimes the change is way bigger than it needs to be for a 2% win. Reviewing commit-by-commit and re-implementing them lets me actually own what goes in.

What I noticed

Ideas keep coming, including counter-intuitive ones

Even when you keep the routine running, it doesn't run out of things to suggest. The most interesting ones are the ones that go against my own gut feel — "this used to be faster with X, but with the current shape it's faster to revert that." The codebase changes around old optimizations, but I rarely revisit them. An AI that only looks at numbers catches that drift more easily than I do.

It pairs well with changes I'd never bother with on my own

20+ PRs ended up in v1.14.0, and individually a lot of them are -2% or -3% kind of things. The kind of change where, if you wrote it by hand, you'd think "...is this really worth typing out?"

But when the implementation and the measurement arrive together, "okay, I'll take it" feels totally reasonable. The cost of accepting small wins drops because the work isn't on me.

What I want to improve

The prompt is fairly minimal right now. Things like "what exactly to measure," "how much regression to tolerate," "what behavior must not change" — I haven't really nailed those down. Tightening them would probably make the AI's calls more accurate.

I also don't have a benchmark scaffold checked into the repo. Right now Claude Code writes one on the fly each run, which works, but having something stable in the repo would mean more reliable measurements and lower token usage. Something to clean up.

Closing thoughts

Setting the benchmark up takes effort, the room for wins shrinks over time, and not everything the AI suggests is good. Reviews still flip a few decisions.

That said, "your PR has grown overnight" is a new kind of experience. You wake up, the PR has a few new optimization commits with benchmark results attached, and your job is just to review.

If this sounds interesting, the easiest place to start is to get a benchmark running on your CI. With that in place, Claude Code's Routines will quietly grow the rest.

Automating TypeScript @types Package Management with typesync

yamadashy — Sun, 28 Jul 2024 03:47:14 +0000

Have you ever found yourself tediously adding type definition packages to your TypeScript project? Wouldn't it be great if this process could be automated?

Today, I'm excited to introduce a package that solves this exact problem!

Introducing typesync

GitHub - jeffijoe/typesync

Install missing TypeScript typings for dependencies in your package.json.

typesync is a package that automatically adds missing type definition packages by analyzing your package.json file.

Installation

Let's get started by installing typesync:

$ yarn add -D typesync

# or if you're using npm
$ npm install -D typesync

Next, set it up to run during the preinstall phase:

{
    "scripts": {
        "preinstall": "typesync || :"
    }
}

The || : is added to ignore errors during the initial installation when typesync isn't available yet.

If you encounter issues, you can set it up as a postinstall script instead:

{
    "scripts": {
        "postinstall": "typesync"

        // To automatically install @types after adding:
        // "postinstall": "typesync && yarn install --ignore-scripts"
        // or for npm:
        // "postinstall": "typesync && npm install --ignore-scripts"
    }
}

Seeing it in Action

Let's test typesync on two popular projects: react-redux-realworld-example-app and vue-realworld-example-app.

For react-redux-realworld-example-app:

  "devDependencies": {
    ...
+    "@types/history": "^4.7.6",
+    "@types/marked": "^0.7.4",
+    "@types/prop-types": "^15.7.3",
+    "@types/react": "^16.9.35",
+    "@types/react-dom": "^16.9.8",
+    "@types/react-redux": "^5.0.21",
+    "@types/react-router": "^4.4.5",
+    "@types/react-router-dom": "^4.3.5",
+    "@types/react-router-redux": "^5.0.18",
+    "@types/redux-logger": "^3.0.7",
+    "@types/superagent": "^3.8.7",
  }

For vue-realworld-example-app:

  "devDependencies": {
    ...
+    "@types/babel-core": "6.25.6",
+    "@types/babel__core": "^7.1.7",
+    "@types/babel__preset-env": "^7.9.0",
+    "@types/marked": "^0.7.4",
+    "@types/node-sass": "^4.11.1",
  }

As you can see, typesync successfully added the missing @types packages. Note that Vue's type definitions are included in the main package, so they were correctly skipped.

Advanced Configuration

While typesync works great out of the box, you can customize its behavior by adding a .typesyncrc file:

{
    "ignorePackages": ["react", "nodemon"]
}

This allows you to specify packages that you don't want typesync to manage. For more detailed usage, check out the official documentation.

How It Works

typesync operates on a simple yet effective principle:

Fetch information about all @types packages
Compare with your package.json
Update package.json with appropriate @types packages

What makes typesync particularly impressive is that it:

Adds the closest matching version in compliance with semver
Skips packages that already include type definitions
Removes @types packages for dependencies you no longer use

The @types package information is sourced from a JSON file used by the TypeScript Types Search.

Wrapping Up

typesync is a small tool that can save you a significant amount of time and mental overhead. By automating the management of type definition packages, it allows you to focus on what really matters - writing great TypeScript code.

Give typesync a try in your next TypeScript project and free yourself from the tedium of manual @types management!

How has your experience been with managing TypeScript type definitions? Have you used typesync or similar tools? Share your thoughts and experiences in the comments below!

I made Repomix: A Tool for Seamless Coding with Claude AI

yamadashy — Tue, 16 Jul 2024 14:17:46 +0000

TL;DR

I created Repomix, a Node.js tool that combines your project files into a single document. It was originally made to help me work with AI coding assistants like Claude, but it might be useful for other purposes too. It handles file encoding, ignores binary files, and respects .gitignore patterns.

I had a positive experience coding with Claude, which inspired me to create this Node.js command. It aims to simplify the process of working with AI on larger codebases. Here's how it works:

Running the following command in the root of your repository will create a file called repomix-output.txt:

$ npx repomix

You can then send this file to an AI assistant with a prompt like:

This file contains all the files in the repository combined into one. I want to refactor the code, so please review it first.

The AI can then understand the overall content and potentially assist with tasks like refactoring.

When you propose specific changes, the AI might be able to generate code accordingly. With features like Claude's Artifacts, you could potentially output multiple files, allowing for the generation of multiple interdependent pieces of code.

Features

This tool combines files under a specified folder into a single file.

https://github.com/yamadashy/repomix

While it handles details like ignoring .gitignore targets and binary files, and includes phrases to help AI understand, what it does is simple: it outputs a file like this:

================================================================
REPOMIX OUTPUT FILE
================================================================
// Phrases to help AI understand

================
File: src/index.js
================
// File contents

================
File: src/utils.js
================
// File contents

Claude 3.5 Sonnet can understand this simple structure well, so it can easily handle refactoring across multiple files.

While the context length that AI services can process is limited, this should be sufficient for small-scale projects. (Please don't use it for work code!)

You can adjust ignore targets in the configuration file. Please check the GitHub repository for more details.

Background

I've been experimenting with Claude Pro recently, using the Projects feature to load multiple files and have it modify code. It generates code with about 60-95% accuracy, which I find quite efficient when used as a reference for rewriting code.

However, the Projects feature doesn't allow uploading folders or zip files directly. I considered using Cursor, but hesitated due to its pay-as-you-go API.

Then I saw this article and realized that Claude could understand even when everything was in a single file, which led me to create and publish this tool.

https://qiita.com/kunishou/items/ed097b46cd78030e0b29

About the Development

While it's not doing anything too complex, I hope it can be of some use 🙏

Output File Content

The output file begins with text explaining how to handle the file.

Initially, I used a simple structure with just file paths and contents, but Claude sometimes had trouble understanding it. By adding "File Purpose," "Format," "Handling Method," and "Other Notes" at the beginning, Claude could understand more accurately.

Token Optimization

For file separators, I referred to ChatGPT's Tokenizer and used 16 and 64 = characters, which count as 1 token.

https://platform.openai.com/tokenizer

The token count might be different for ChatGPT-4 or Claude, but I aimed for something similar.

CLI Implementation

I used the commander library to create the command-line tool. I could have used yargs, but I like commander's simple syntax and automatic help generation.

To get the tool's version, I read from package.json. To ensure compatibility with older Node.js versions, I use fs to read it directly instead of import. Also, since __dirname isn't available in ES modules and import.meta.dirname isn't supported in some versions, I use a slightly tricky method:

import * as url from "url";

const dirName = url.fileURLToPath(new URL(".", import.meta.url));

Publishing as an npm Package

To easily publish new versions to npm, I added these scripts to package.json:

    "npm-publish": "npm run lint && npm run test-coverage && npm run build && npm publish",
    "npm-release-patch": "npm version patch && npm run npm-publish",
    "npm-release-minor": "npm version minor && npm run npm-publish",
    "npm-release-prerelease": "npm version prerelease && npm run npm-publish"

The npm version <major|minor|patch> command is surprisingly handy.

File Encoding

Since this tool shouldn't read binary files, I use is-binary-path to ignore binaries, and jschardet and iconv-lite to handle encoding properly.

File Ignoring

For ignoring specific files, the ignore package is useful. It makes it easy to implement .gitignore-like pattern filtering:

function createIgnoreFilter(patterns: string[]): (path: string) => boolean {
    const ig = ignore.add(patterns);
    return (filePath: string) => !ig.ignores(filePath);
}

Conclusion

This is a simple tool that I created because I needed it. While Claude will likely implement folder and zip upload features if we wait, I believe this tool can be used universally with the growing number of AI generation services.

I'd be happy to receive your feedback if you try it out!

I Made a Chrome Extension. Slack Channels Grouping

yamadashy — Tue, 28 May 2019 15:22:51 +0000

Too many channels make eyes suffering 😫
I made a Chrome extension that grouping channels nicely!


Original	Grouped

Install here

Chrome: Slack Channels Grouping - Chrome Web Store
Firefox: Slack Channels Grouping – Get this Extension for 🦊 Firefox

Feature

It grouping channels by hyphens and underscores.

animal-dog
animal_cat

It observe DOM updates, so it support channel creation and renaming.
If the tab is inactive, DOM observing is turned off.

Why

In my team, there is rule of putting "prefix-" in channel name.
As the number of channels continues to increase, it has become hard to tell apart between "chat" and "club" 🤔

So I made it to make design as eye-friendly as possible.

About Development

I write about the following keywords.

webextension-toolbox
- webpack
- TypeScript
Page Visibility API
requestIdleCallback

webextension-toolbox

webextension-toolbox is extension creation tool for Chrome, Firefox etc.
webextension-toolbox/webextension-toolbox - GitHub

You can easily output Chrome and Firefox extensions without thinking about cross-browser support.

Generate a template with the following command,

yarn global add yo generator-web-extension
yo web-extension

Start development,

yarn dev chrome

Output zip,

yarn build chrome

Just uploads to Chrome Web Store Dashboard.

It's easy as pie!

webpack

webextension-toolbox builds with webpack, but you can develop even if you have never touched webpack.
If you are familiar with webpack, you can easily extend it.

TypeScript

Recently I have been actively using TypeScript, and I used it.

If you are using typescript and webextension-toolbox, you need to create a file webextension-toolbox-config.js to overwrite the configuration.

module.exports = {
  webpack: (config, { dev, vendor }) => {
    config.resolve.extensions.push('.ts')
    config.module.rules.push({
      test: /\.ts$/,
      loader: 'ts-loader'
    })
    return config
  }
}

The benefits of TypeScript are great if it is a large-scale extension.

Page Visibility API

This API observe whether the page is visible.
Page Visibility API - Web APIs | MDN

This extension observe DOM with MutationObserver. I don't want to keeping it working, so I use this API to control it.

document.addEventListener("visibilitychange", () => {
  if (document.hidden) {
    // Stop observing
  } else {
    // Restart observing
  }
}

requestIdleCallback

This API performs processing when event loop is idle so that it does not block other processing.
This article nicely order about this API.
Using requestIdleCallback | Web | Google Developers

requestIdleCallback(() => {
  // execute
}, {
  timeout: 3000 // Forced execution if not executed after 3 seconds
})

This API is used to grouping channel list.

Lastly

I knew webextension-toolbox for the first time, but it was very convenient and great.
You can create cross-browser extensions quickly, so try it! 😄

Emoji cheatsheet for DEV/Github/Slack/Discord/Qiita

yamadashy — Fri, 15 Feb 2019 17:32:30 +0000

This can be used with dev.to and Github, and so on 😊

How to use emoji
- If you enter : smile: in the markdown, you will see 😄.
reference: EMOJI CHEAT SHEET

People
Nature
Objects
Places
Symbols

People


😄 :smile:	😆 :laughing:	😊 :blush:	😃 :smiley:	😏 :smirk:
😍 :heart_eyes:	😘 :kissing_heart:	😚 :kissing_closed_eyes:	😳 :flushed:	😌 :relieved:
😆 :satisfied:	😁 :grin:	😉 :wink:	😜 :stuck_out_tongue_winking_eye:	😝 :stuck_out_tongue_closed_eyes:
😀 :grinning:	😗 :kissing:	😙 :kissing_smiling_eyes:	😛 :stuck_out_tongue:	😴 :sleeping:
😟 :worried:	😦 :frowning:	😧 :anguished:	😮 :open_mouth:	😬 :grimacing:
😕 :confused:	😯 :hushed:	😑 :expressionless:	😒 :unamused:	😅 :sweat_smile:
😓 :sweat:	😥 :disappointed_relieved:	😩 :weary:	😔 :pensive:	😞 :disappointed:
😖 :confounded:	😨 :fearful:	😰 :cold_sweat:	😣 :persevere:	😢 :cry:
😭 :sob:	😂 :joy:	😲 :astonished:	😱 :scream:	😫 :tired_face:
😠 :angry:	😡 :rage:	😤 :triumph:	😪 :sleepy:	😋 :yum:
😷 :mask:	😎 :sunglasses:	😵 :dizzy_face:	👿 :imp:	😈 :smiling_imp:
😐 :neutral_face:	😶 :no_mouth:	😇 :innocent:	👽 :alien:	💛 :yellow_heart:
💙 :blue_heart:	💜 :purple_heart:	❤️ :heart:	💚 :green_heart:	💔 :broken_heart:
💓 :heartbeat:	💗 :heartpulse:	💕 :two_hearts:	💞 :revolving_hearts:	💘 :cupid:
💖 :sparkling_heart:	✨ :sparkles:	⭐ :star:	🌟 :star2:	💫 :dizzy:
💥 :boom:	💥 :collision:	💢 :anger:	❗ :exclamation:	❓ :question:
❕ :grey_exclamation:	❔ :grey_question:	💤 :zzz:	💨 :dash:	💦 :sweat_drops:
🎶 :notes:	🎵 :musical_note:	🔥 :fire:	💩 :hankey:	💩 :poop:
💩 :shit:	👍 :+1:	👍 :thumbsup:	👎 :-1:	👎 :thumbsdown:
👌 :ok_hand:	👊 :punch:	👊 :facepunch:	✊ :fist:	✌️ :v:
👋 :wave:	✋ :hand:	✋ :raised_hand:	👐 :open_hands:	☝️ :point_up:
👇 :point_down:	👈 :point_left:	👉 :point_right:	🙌 :raised_hands:	🙏 :pray:
👆 :point_up_2:	👏 :clap:	💪 :muscle:	🤘 :metal:	🖕 :fu:
🏃 :runner:	🏃 :running:	👫 :couple:	👪 :family:	👬 :two_men_holding_hands:
👭 :two_women_holding_hands:	💃 :dancer:	👯 :dancers:	🙆‍♀️ :ok_woman:	🙅 :no_good:
💁 :information_desk_person:	🙋 :raising_hand:	👰‍♀️ :bride_with_veil:	:person_with_pouting_face: :person_with_pouting_face:	:person_frowning: :person_frowning:
🙇 :bow:	💏 :couplekiss:	💑 :couple_with_heart:	💆 :massage:	💇 :haircut:
💅 :nail_care:	👦 :boy:	👧 :girl:	👩 :woman:	👨 :man:
👶 :baby:	👵 :older_woman:	👴 :older_man:	:person_with_blond_hair: :person_with_blond_hair:	👲 :man_with_gua_pi_mao:
👳‍♂️ :man_with_turban:	👷 :construction_worker:	👮 :cop:	👼 :angel:	👸 :princess:
😺 :smiley_cat:	😸 :smile_cat:	😻 :heart_eyes_cat:	😽 :kissing_cat:	😼 :smirk_cat:
🙀 :scream_cat:	😿 :crying_cat_face:	😹 :joy_cat:	😾 :pouting_cat:	👹 :japanese_ogre:
👺 :japanese_goblin:	🙈 :see_no_evil:	🙉 :hear_no_evil:	🙊 :speak_no_evil:	💂‍♂️ :guardsman:
💀 :skull:	🐾 :feet:	👄 :lips:	💋 :kiss:	💧 :droplet:
👂 :ear:	👀 :eyes:	👃 :nose:	👅 :tongue:	💌 :love_letter:
👤 :bust_in_silhouette:	👥 :busts_in_silhouette:	💬 :speech_balloon:	💭 :thought_balloon:

Nature


☀️ :sunny:	☔ :umbrella:	☁️ :cloud:	❄️ :snowflake:	⛄ :snowman:
⚡ :zap:	🌀 :cyclone:	🌁 :foggy:	🌊 :ocean:	🐱 :cat:
🐶 :dog:	🐭 :mouse:	🐹 :hamster:	🐰 :rabbit:	🐺 :wolf:
🐸 :frog:	🐯 :tiger:	🐨 :koala:	🐻 :bear:	🐷 :pig:
🐽 :pig_nose:	🐮 :cow:	🐗 :boar:	🐵 :monkey_face:	🐒 :monkey:
🐴 :horse:	🐎 :racehorse:	🐫 :camel:	🐑 :sheep:	🐘 :elephant:
🐼 :panda_face:	🐍 :snake:	🐦 :bird:	🐤 :baby_chick:	🐥 :hatched_chick:
🐣 :hatching_chick:	🐔 :chicken:	🐧 :penguin:	🐢 :turtle:	🐛 :bug:
🐝 :honeybee:	🐜 :ant:	🪲 :beetle:	🐌 :snail:	🐙 :octopus:
🐠 :tropical_fish:	🐟 :fish:	🐳 :whale:	🐋 :whale2:	🐬 :dolphin:
🐄 :cow2:	🐏 :ram:	🐀 :rat:	🐃 :water_buffalo:	🐅 :tiger2:
🐇 :rabbit2:	🐉 :dragon:	🐐 :goat:	🐓 :rooster:	🐕 :dog2:
🐖 :pig2:	🐁 :mouse2:	🐂 :ox:	🐲 :dragon_face:	🐡 :blowfish:
🐊 :crocodile:	🐪 :dromedary_camel:	🐆 :leopard:	🐈 :cat2:	🐩 :poodle:
🐾 :paw_prints:	💐 :bouquet:	🌸 :cherry_blossom:	🌷 :tulip:	🍀 :four_leaf_clover:
🌹 :rose:	🌻 :sunflower:	🌺 :hibiscus:	🍁 :maple_leaf:	🍃 :leaves:
🍂 :fallen_leaf:	🌿 :herb:	🍄 :mushroom:	🌵 :cactus:	🌴 :palm_tree:
🌲 :evergreen_tree:	🌳 :deciduous_tree:	🌰 :chestnut:	🌱 :seedling:	🌼 :blossom:
🌾 :ear_of_rice:	🐚 :shell:	🌐 :globe_with_meridians:	🌞 :sun_with_face:	🌝 :full_moon_with_face:
🌚 :new_moon_with_face:	🌑 :new_moon:	🌒 :waxing_crescent_moon:	🌓 :first_quarter_moon:	🌔 :waxing_gibbous_moon:
🌕 :full_moon:	🌖 :waning_gibbous_moon:	🌗 :last_quarter_moon:	🌘 :waning_crescent_moon:	🌜 :last_quarter_moon_with_face:
🌛 :first_quarter_moon_with_face:	🌙 :crescent_moon:	🌍 :earth_africa:	🌎 :earth_americas:	🌏 :earth_asia:
🌋 :volcano:	🌌 :milky_way:	⛅ :partly_sunny:

Objects


🎍 :bamboo:	💝 :gift_heart:	🎎 :dolls:	🎒 :school_satchel:	🎓 :mortar_board:
🎏 :flags:	🎆 :fireworks:	🎇 :sparkler:	🎐 :wind_chime:	🎑 :rice_scene:
🎃 :jack_o_lantern:	👻 :ghost:	🎅 :santa:	🎄 :christmas_tree:	🎁 :gift:
🔔 :bell:	🔕 :no_bell:	🎋 :tanabata_tree:	🎉 :tada:	🎊 :confetti_ball:
🎈 :balloon:	🔮 :crystal_ball:	💿 :cd:	📀 :dvd:	💾 :floppy_disk:
📷 :camera:	📹 :video_camera:	🎥 :movie_camera:	💻 :computer:	📺 :tv:
📱 :iphone:	☎️ :phone:	☎️ :telephone:	📞 :telephone_receiver:	📟 :pager:
📠 :fax:	💽 :minidisc:	📼 :vhs:	🔉 :sound:	🔈 :speaker:
🔇 :mute:	📢 :loudspeaker:	📣 :mega:	⌛ :hourglass:	⏳ :hourglass_flowing_sand:
⏰ :alarm_clock:	⌚ :watch:	📻 :radio:	📡 :satellite:	➿ :loop:
🔍 :mag:	🔎 :mag_right:	🔓 :unlock:	🔒 :lock:	🔏 :lock_with_ink_pen:
🔐 :closed_lock_with_key:	🔑 :key:	💡 :bulb:	🔦 :flashlight:	🔆 :high_brightness:
🔅 :low_brightness:	🔌 :electric_plug:	🔋 :battery:	📲 :calling:	📧 :email:
📫 :mailbox:	📮 :postbox:	🛀 :bath:	🛁 :bathtub:	🚿 :shower:
🚽 :toilet:	🔧 :wrench:	🔩 :nut_and_bolt:	🔨 :hammer:	💺 :seat:
💰 :moneybag:	💴 :yen:	💵 :dollar:	💷 :pound:	💶 :euro:
💳 :credit_card:	💸 :money_with_wings:	📧 :e-mail:	📥 :inbox_tray:	📤 :outbox_tray:
✉️ :envelope:	📨 :incoming_envelope:	📯 :postal_horn:	📪 :mailbox_closed:	📬 :mailbox_with_mail:
📭 :mailbox_with_no_mail:	📦 :package:	🚪 :door:	🚬 :smoking:	💣 :bomb:
🔫 :gun:	🔪 :hocho:	💊 :pill:	💉 :syringe:	📄 :page_facing_up:
📃 :page_with_curl:	📑 :bookmark_tabs:	📊 :bar_chart:	📈 :chart_with_upwards_trend:	📉 :chart_with_downwards_trend:
📜 :scroll:	📋 :clipboard:	📆 :calendar:	📅 :date:	📇 :card_index:
📁 :file_folder:	📂 :open_file_folder:	✂️ :scissors:	📌 :pushpin:	📎 :paperclip:
✒️ :black_nib:	✏️ :pencil2:	📏 :straight_ruler:	📐 :triangular_ruler:	📕 :closed_book:
📗 :green_book:	📘 :blue_book:	📙 :orange_book:	📓 :notebook:	📔 :notebook_with_decorative_cover:
📒 :ledger:	📚 :books:	🔖 :bookmark:	📛 :name_badge:	🔬 :microscope:
🔭 :telescope:	📰 :newspaper:	🏈 :football:	🏀 :basketball:	⚽ :soccer:
⚾ :baseball:	🎾 :tennis:	🎱 :8ball:	🏉 :rugby_football:	🎳 :bowling:
⛳ :golf:	🚵 :mountain_bicyclist:	🚴 :bicyclist:	🏇 :horse_racing:	🏂 :snowboarder:
🏊 :swimmer:	🏄 :surfer:	🎿 :ski:	♠️ :spades:	♥️ :hearts:
♣️ :clubs:	♦️ :diamonds:	💎 :gem:	💍 :ring:	🏆 :trophy:
🎼 :musical_score:	🎹 :musical_keyboard:	🎻 :violin:	👾 :space_invader:	🎮 :video_game:
🃏 :black_joker:	🎴 :flower_playing_cards:	🎲 :game_die:	🎯 :dart:	🀄 :mahjong:
🎬 :clapper:	📝 :memo:	📝 :pencil:	📖 :book:	🎨 :art:
🎤 :microphone:	🎧 :headphones:	🎺 :trumpet:	🎷 :saxophone:	🎸 :guitar:
👞 :shoe:	👡 :sandal:	👠 :high_heel:	💄 :lipstick:	👢 :boot:
👕 :shirt:	👕 :tshirt:	👔 :necktie:	👚 :womans_clothes:	👗 :dress:
🎽 :running_shirt_with_sash:	👖 :jeans:	👘 :kimono:	👙 :bikini:	🎀 :ribbon:
🎩 :tophat:	👑 :crown:	👒 :womans_hat:	👞 :mans_shoe:	🌂 :closed_umbrella:
💼 :briefcase:	👜 :handbag:	👝 :pouch:	👛 :purse:	👓 :eyeglasses:
🎣 :fishing_pole_and_fish:	☕ :coffee:	🍵 :tea:	🍶 :sake:	🍼 :baby_bottle:
🍺 :beer:	🍻 :beers:	🍸 :cocktail:	🍹 :tropical_drink:	🍷 :wine_glass:
🍴 :fork_and_knife:	🍕 :pizza:	🍔 :hamburger:	🍟 :fries:	🍗 :poultry_leg:
🍖 :meat_on_bone:	🍝 :spaghetti:	🍛 :curry:	🍤 :fried_shrimp:	🍱 :bento:
🍣 :sushi:	🍥 :fish_cake:	🍙 :rice_ball:	🍘 :rice_cracker:	🍚 :rice:
🍜 :ramen:	🍲 :stew:	🍢 :oden:	🍡 :dango:	🥚 :egg:
🍞 :bread:	🍩 :doughnut:	🍮 :custard:	🍦 :icecream:	🍨 :ice_cream:
🍧 :shaved_ice:	🎂 :birthday:	🍰 :cake:	🍪 :cookie:	🍫 :chocolate_bar:
🍬 :candy:	🍭 :lollipop:	🍯 :honey_pot:	🍎 :apple:	🍏 :green_apple:
🍊 :tangerine:	🍋 :lemon:	🍒 :cherries:	🍇 :grapes:	🍉 :watermelon:
🍓 :strawberry:	🍑 :peach:	🍈 :melon:	🍌 :banana:	🍐 :pear:
🍍 :pineapple:	🍠 :sweet_potato:	🍆 :eggplant:	🍅 :tomato:	🌽 :corn:

Places


🏠 :house:	🏡 :house_with_garden:	🏫 :school:	🏢 :office:	🏣 :post_office:
🏥 :hospital:	🏦 :bank:	🏪 :convenience_store:	🏩 :love_hotel:	🏨 :hotel:
💒 :wedding:	⛪ :church:	🏬 :department_store:	🏤 :european_post_office:	🌇 :city_sunrise:
🌆 :city_sunset:	🏯 :japanese_castle:	🏰 :european_castle:	⛺ :tent:	🏭 :factory:
🗼 :tokyo_tower:	🗾 :japan:	🗻 :mount_fuji:	🌄 :sunrise_over_mountains:	🌅 :sunrise:
🌠 :stars:	🗽 :statue_of_liberty:	🌉 :bridge_at_night:	🎠 :carousel_horse:	🌈 :rainbow:
🎡 :ferris_wheel:	⛲ :fountain:	🎢 :roller_coaster:	🚢 :ship:	🚤 :speedboat:
⛵ :boat:	⛵ :sailboat:	🚣 :rowboat:	⚓ :anchor:	🚀 :rocket:
✈️ :airplane:	🚁 :helicopter:	🚂 :steam_locomotive:	🚊 :tram:	🚞 :mountain_railway:
🚲 :bike:	🚡 :aerial_tramway:	🚟 :suspension_railway:	🚠 :mountain_cableway:	🚜 :tractor:
🚙 :blue_car:	🚘 :oncoming_automobile:	🚗 :car:	🚗 :red_car:	🚕 :taxi:
🚖 :oncoming_taxi:	🚛 :articulated_lorry:	🚌 :bus:	🚍 :oncoming_bus:	🚨 :rotating_light:
🚓 :police_car:	🚔 :oncoming_police_car:	🚒 :fire_engine:	🚑 :ambulance:	🚐 :minibus:
🚚 :truck:	🚋 :train:	🚉 :station:	🚆 :train2:	🚅 :bullettrain_front:
🚄 :bullettrain_side:	🚈 :light_rail:	🚝 :monorail:	🚃 :railway_car:	🚎 :trolleybus:
🎫 :ticket:	⛽ :fuelpump:	🚦 :vertical_traffic_light:	🚥 :traffic_light:	⚠️ :warning:
🚧 :construction:	🔰 :beginner:	🏧 :atm:	🎰 :slot_machine:	🚏 :busstop:
💈 :barber:	♨️ :hotsprings:	🏁 :checkered_flag:	🎌 :crossed_flags:	🏮 :izakaya_lantern:
🗿 :moyai:	🎪 :circus_tent:	🎭 :performing_arts:	📍 :round_pushpin:	🚩 :triangular_flag_on_post:
🇯🇵 :jp:	🇰🇷 :kr:	🇨🇳 :cn:	🇺🇸 :us:	🇫🇷 :fr:
🇪🇸 :es:	🇮🇹 :it:	🇷🇺 :ru:	🇬🇧 :gb:	🇬🇧 :uk:
🇩🇪 :de:

Symbols


1️⃣ :one:	2️⃣ :two:	3️⃣ :three:	4️⃣ :four:	5️⃣ :five:
6️⃣ :six:	7️⃣ :seven:	8️⃣ :eight:	9️⃣ :nine:	🔟 :keycap_ten:
🔢 :1234:	0️⃣ :zero:	#️⃣ :hash:	🔣 :symbols:	◀️ :arrow_backward:
⬇️ :arrow_down:	▶️ :arrow_forward:	⬅️ :arrow_left:	🔠 :capital_abcd:	🔡 :abcd:
🔤 :abc:	↙️ :arrow_lower_left:	↘️ :arrow_lower_right:	➡️ :arrow_right:	⬆️ :arrow_up:
↖️ :arrow_upper_left:	↗️ :arrow_upper_right:	⏬ :arrow_double_down:	⏫ :arrow_double_up:	🔽 :arrow_down_small:
⤵️ :arrow_heading_down:	⤴️ :arrow_heading_up:	↩️ :leftwards_arrow_with_hook:	↪️ :arrow_right_hook:	↔️ :left_right_arrow:
↕️ :arrow_up_down:	🔼 :arrow_up_small:	🔃 :arrows_clockwise:	🔄 :arrows_counterclockwise:	⏪ :rewind:
⏩ :fast_forward:	ℹ️ :information_source:	🆗 :ok:	🔀 :twisted_rightwards_arrows:	🔁 :repeat:
🔂 :repeat_one:	🆕 :new:	🔝 :top:	🆙 :up:	🆒 :cool:
🆓 :free:	🆖 :ng:	🎦 :cinema:	🈁 :koko:	📶 :signal_strength:
🈹 :u5272:	🈴 :u5408:	🈺 :u55b6:	🈯 :u6307:	🈷️ :u6708:
🈶 :u6709:	🈵 :u6e80:	🈚 :u7121:	🈸 :u7533:	🈳 :u7a7a:
🈲 :u7981:	🈂️ :sa:	🚻 :restroom:	🚹 :mens:	🚺 :womens:
🚼 :baby_symbol:	🚭 :no_smoking:	🅿️ :parking:	♿ :wheelchair:	🚇 :metro:
🛄 :baggage_claim:	🉑 :accept:	🚾 :wc:	🚰 :potable_water:	🚮 :put_litter_in_its_place:
㊙️ :secret:	㊗️ :congratulations:	Ⓜ️ :m:	🛂 :passport_control:	🛅 :left_luggage:
🛃 :customs:	🉐 :ideograph_advantage:	🆑 :cl:	🆘 :sos:	🆔 :id:
🚫 :no_entry_sign:	🔞 :underage:	📵 :no_mobile_phones:	🚯 :do_not_litter:	🚱 :non-potable_water:
🚳 :no_bicycles:	🚷 :no_pedestrians:	🚸 :children_crossing:	⛔ :no_entry:	✳️ :eight_spoked_asterisk:
❇️ :sparkle:	✴️ :eight_pointed_black_star:	💟 :heart_decoration:	🆚 :vs:	📳 :vibration_mode:
📴 :mobile_phone_off:	💹 :chart:	💱 :currency_exchange:	♈ :aries:	♉ :taurus:
♊ :gemini:	♋ :cancer:	♌ :leo:	♍ :virgo:	♎ :libra:
♏ :scorpius:	♐ :sagittarius:	♑ :capricorn:	♒ :aquarius:	♓ :pisces:
⛎ :ophiuchus:	🔯 :six_pointed_star:	❎ :negative_squared_cross_mark:	🅰️ :a:	🅱️ :b:
🆎 :ab:	🅾️ :o2:	💠 :diamond_shape_with_a_dot_inside:	♻️ :recycle:	🔚 :end:
🔙 :back:	🔛 :on:	🔜 :soon:	🕐 :clock1:	🕜 :clock130:
🕙 :clock10:	🕥 :clock1030:	🕚 :clock11:	🕦 :clock1130:	🕛 :clock12:
🕧 :clock1230:	🕑 :clock2:	🕝 :clock230:	🕒 :clock3:	🕞 :clock330:
🕓 :clock4:	🕟 :clock430:	🕔 :clock5:	🕠 :clock530:	🕕 :clock6:
🕡 :clock630:	🕖 :clock7:	🕢 :clock730:	🕗 :clock8:	🕣 :clock830:
🕘 :clock9:	🕤 :clock930:	💲 :heavy_dollar_sign:	©️ :copyright:	®️ :registered:
™️ :tm:	❌ :x:	❗ :heavy_exclamation_mark:	‼️ :bangbang:	⁉️ :interrobang:
⭕ :o:	✖️ :heavy_multiplication_x:	➕ :heavy_plus_sign:	➖ :heavy_minus_sign:	➗ :heavy_division_sign:
💮 :white_flower:	💯 :100:	✔️ :heavy_check_mark:	☑️ :ballot_box_with_check:	🔘 :radio_button:
🔗 :link:	➰ :curly_loop:	〰️ :wavy_dash:	〽️ :part_alternation_mark:	🔱 :trident:
▪️ :black_small_square:	▫️ :white_small_square:	◾ :black_medium_small_square:	◽ :white_medium_small_square:	◼️ :black_medium_square:
◻️ :white_medium_square:	⬛ :black_large_square:	⬜ :white_large_square:	✅ :white_check_mark:	🔲 :black_square_button:
🔳 :white_square_button:	⚫ :black_circle:	⚪ :white_circle:	🔴 :red_circle:	🔵 :large_blue_circle:
🔷 :large_blue_diamond:	🔶 :large_orange_diamond:	🔹 :small_blue_diamond:	🔸 :small_orange_diamond:	🔺 :small_red_triangle:
🔻 :small_red_triangle_down: