Miki-Moni

Use when working in the miki-moni / cc-hub repo and need to find which file handles a feature (pairing, image rendering, permission mode, transcript bubbles, dashboard UI, phone client, worker relay, etc.) without re-scanning the codebase. Trigger phrases include "miki where is X", "需要修 X 在哪", "找 pair flow", "image bubble code", "permission mode chip 在哪".

Use when working in the miki-moni / cc-hub repo and need to find which file handles a feature (pairing, image rendering, permission mode, transcript bubbles, dashboard UI, phone client, worker relay, etc.) without re-scanning the codebase. Trigger phrases include "miki where is X", "需要修 X 在哪", "找 pair flow", "image bubble code", "permission mode chip 在哪".

Use when adding a new HTTP route, WebSocket handler, or `/admin/*` endpoint to the miki-moni daemon (src/server.ts). Triggers on "新增 daemon endpoint", "add route to miki", "new express route", "add admin endpoint", "expose new API on 8765". Covers the DNS-rebind-guard interaction, logging conventions, error format, and where similar endpoints live as templates.

Use when modifying any part of miki-moni's pairing / relay flow — daemon-side pair handling, worker DurableObjects, phone client bootstrap, QR generation, token registration. Triggers on "改 pair", "modify pairing", "relay change", "add pair token field", "pair URL format", "anti-MITM", "pair approval". This area has bitten us repeatedly (chicken-egg, silent-fallback, double-path, MITM); this skill is the regression-prevention checklist.

Use when shipping a new version of miki-moni (a.k.a. cc-hub). Triggers on "release miki-moni", "publish 0.x.y", "push to main and update npm", "deploy worker + pages", "ship the fix". Covers the full bump → test → push → worker deploy → Pages deploy → npm publish sequence with all the gotchas learned from 0.3.x releases.

Use when shipping a new version of miki-moni (a.k.a. cc-hub). Triggers on "release miki-moni", "publish 0.x.y", "push to main and update npm", "deploy worker + pages", "ship the fix". Covers the full bump → test → push → worker deploy → Pages deploy → npm publish sequence with all the gotchas learned from 0.3.x releases.