July 2026
Kaeru Plugins
Two independent Claude Code plugins from one marketplace: kaeru lets non-technical staff safely edit a website's text, images, and colors in their own language and submit a PR for review — git stays hidden, it never merges; octo is the developer-facing GitHub + CI/CD toolkit — repo bootstrap, the issue → PR → merge flow, CI checks, and releases. The name folds in three meanings at once: 変える (change/edit), 帰る (return — a PR coming back for review), and 蛙 (frog — the mascot) — chosen so non-technical staff hear "Kaeru shite!" as friendly, not technical.
A Claude Code plugin marketplace, with its own doc site.
A Claude Code plugin marketplace, with its own doc site.
Two independent Claude Code plugins from one marketplace: kaeru lets non-technical staff safely edit a website's text, images, and colors in their own language and submit a PR for review — git stays hidden, it never merges; octo is the developer-facing GitHub + CI/CD toolkit — repo bootstrap, the issue → PR → merge flow, CI checks, and releases. The name folds in three meanings at once: 変える (change/edit), 帰る (return — a PR coming back for review), and 蛙 (frog — the mascot) — chosen so non-technical staff hear "Kaeru shite!" as friendly, not technical.
- kaeru: guided commands for text/image/color edits, an accessibility check, Playwright preview, and PR submission — git is hidden from the user entirely
- octo: repo bootstrap, the issue→PR→merge flow, CI checks, releases, and syncing the issue-driven templates into any repo
- Independent installs — a repo's .claude/settings.json can auto-enable a plugin for whoever opens it
- Ships its own bilingual (EN/JA) Next.js marketing/doc site alongside the plugins
More projects
view all →
LinkedIn Publisher
A LinkedIn integration inside log.exe: a registered developer app, a full 3-legged OAuth flow, and publishing to my own feed through the UGC Posts API. Captions are built from real project rows in D1 — title, tagline, highlights, tech stack, media — so a post can only claim things the CMS already knows. The interesting part was working out what the API will not give me, and saying so in the UI instead of faking it.
API Scalar
Mini-project inside log.exe: interactive OpenAPI docs powered by Scalar. Same repo as the parent — not a separate product. API skala, skalarrrrr, skala.
Mukawa AR Trail
A web AR trail built as a study for the Mukawa dinosaur story. Eight printed boards hang around a building, each with a picture and a QR. The QR only opens a link, so the phone's own camera does the scanning; the app asks for the camera when the visitor taps, recognises the picture itself as an image target, and stands the creature on the board as you move. Every board found unlocks its creature in a collection saved on the phone, with no sign-up. Built end to end by me: the trail app, the image targets, the printed panels and the deploy.