Install them

Three lines in Claude Code, or one prompt you paste and let the agent do it for you.

About two minutes

You do this once per computer. After it, the commands are available in every project you open.

The three lines

Open Claude Code and type these, one at a time:

/plugin marketplace add amirahosbr/kaeru-plugins
/plugin install kaeru@kaeru-plugins
/reload-plugins

The first line tells Claude Code where the plugins live. The second installs the one for making changes. The third makes the new commands available without restarting.

Developer, and want the GitHub side too?

/plugin install octo@kaeru-plugins

Checking it worked

Each line confirms what it did: the marketplace was added, and the plugin was installed at its version number. Then type / — the command list appears, and the sixteen /kaeru: commands are in it:

/kaeru:start        Start a new change — pull the latest main and open a fresh branch
/kaeru:edit-text    Change wording or copy on the site
/kaeru:edit-image   Swap an image for a new one
/kaeru:edit-color   Change a color (design-token values only)
/kaeru:preview      Preview the change locally
/kaeru:check        Check your own change before submitting
/kaeru:submit       Submit the change for review — opens a pull request
…

If /kaeru:start is there, you are done.

Or paste this instead

Rather not type commands? Paste this into Claude Code and it will do the whole thing, including telling you what is missing on your machine:

Install the Kaeru plugins for me, then tell me if anything is missing.

1. Add the marketplace amirahosbr/kaeru-plugins, install the "kaeru" plugin from
   it, and reload plugins.
2. Check I have what the plugins need: git, the GitHub CLI (gh) signed in, and
   Node with bun or npm. Tell me which of those are missing and the one command
   that installs each on my system — do not install them without asking me.
3. List the /kaeru: commands I now have, in a table, with one plain sentence
   each about what it does and when I would use it.
4. Tell me the single next command to type to make my first change.

Keep it short and skip anything that already works.

Per project, once

Before anyone makes a change in a project, a developer runs this inside that project's folder:

/kaeru:setup

It reads the project and writes a short map at .kaeru/where.md — where the text lives, where images and colours live, how to start the dev server, which branch pull requests go to. Every other command reads that map, which is why the edit commands work the same way on a Next.js site and an Astro one.

Skipping this shows up later

Without the map, the edit commands have to guess where anything lives, and /kaeru:check cannot start the dev server to look at the page. It is one command, once, and it is worth doing before handing the project to anybody.

Keeping them up to date

In your terminal, not inside Claude Code:

claude plugin update kaeru@kaeru-plugins

Restart Claude Code afterwards — that is what actually loads the new version.

Worth knowing: the plugin only updates when its version number changes, and there is no force flag. If you are told you are already at the latest version but you expected something new, it was published without a version bump — tell whoever published it, because no amount of updating will fetch it.

What's next

Making a change — the commands you will actually use
Before you submit — the self-check