mochi

Use whenever the user asks to build, add, or modify anything in this Mochi app — pages, routes, islands, selective/lazy/server hydration, forms, JSON/WS/SSE endpoints, cookies, caching, or request context. Before writing any framework code, invoke the "mochi" skill to fetch the relevant Mochi docs and demos.

Add a new lifecycle event to Mochi's event bus (`packages/mochi/src/events.ts`). Use when the user asks to "add an event", "emit a new event", "create a new mochiEvents emission", or "/add-event <name>". Walks the payload type, the `MochiEventMap` registry, the emission site, public exports, optional logger wiring, tests, and docs.

Mutation-test unit tests to verify they catch real failures. For each test, temporarily breaks the source code it exercises, confirms the test fails, then reverts. Flags mock-only tests and suggests fixes. Use when the user says "validate tests", "test-validator", or wants to check test quality.

Take a 16:9 screenshot of a single component via the /shot/:name endpoint (`packages/site/src/shot/`). Use when the user asks to "screenshot a component", "take a component screenshot", "generate an image of <component>", "grab a shot of X for the docs", or "/component-screenshot <component>". Covers registering a new subject, sizing, and driving the browser.

Stage and commit the current working changes with a short release-please-style commit title. Does not push. Use when the user says "commit", "commit my changes", or "/commit". Optional args list paths to skip (e.g. "/commit ignore IMPROVEMENTS.md").

Add a new hook or filter to Mochi's extension API (`packages/mochi/src/extensions.ts`). Use when the user asks to "add a hook", "add a filter", "create an extension point", or "/add-extension <name>". Walks both halves of the type/runtime kind-map registry and the call-site wiring.

Check whether the scripts vendored under packages/mochi/src/vendor/ are on the latest upstream release, and update the ones that aren't. Use when the user asks to "check vendored versions", "update vendored scripts", "refresh vendored deps", or "/update-vendored".

Review the current branch's changes (or a specific PR). Use when the user asks to "review my branch", "review this", "review PR <number>", or "/mochi-review [number]". Always consumes the entire diff into context, then produces a thorough, concise code review.

Generate a VERY BRIEF changelog of what has shipped since the last mochi-framework release tag, written to CHANGELOG-NEW.md. Use when the user says "generate a changelog", "what's changed since the last release", or "/mochi-changelog".

Use whenever the user asks to build, add, or modify anything in this Mochi app — pages, routes, islands, selective/lazy/server hydration, forms, JSON/WS/SSE endpoints, cookies, caching, or request context. Before writing any framework code, invoke the "mochi" skill to fetch the relevant Mochi docs and demos.

Author or revise a docs page in `packages/docs/` in the project's terse, code-first, Svelte-idiomatic style. Use when the user says "write docs for X", "document X", "/write-docs <topic>", or asks to revise an existing page in that folder.

Apply the 30 Laws of UX (Jon Yablonski) to web and app interface work — design review, component building, layout decisions, copy, flows, forms, navigation, error states, performance perception, and accessibility. Use whenever the user is building, reviewing, refactoring, or critiquing a website or web/mobile app UI; whenever they ask "how should this look/feel/behave"; whenever they're picking between layout or interaction options; whenever they share a screenshot or component for feedback; and proactively flag relevant laws during any frontend code work involving user-facing surfaces. Scope is digital screens only — not print, not voice, not physical product design.

Upgrade Bun to the latest version and sync the pinned version across .bun-version, Dockerfile, Dockerfile.production, and @types/bun in package.json. Use when the user asks to "update bun", "upgrade bun", or "bump bun version".