Create interactive UI prototypes with a CDN-only stack built from z-proto, HTM UI, Tailwind CSS v4, Preact/htm, and preact-iso, including faithful send-to-Figma captures when requested. Use when asked to prototype, create mockup screens, explore an interactive UI flow, or validate product behavior before implementation.
Initialize, migrate, or refresh a repo's ai-memory wiring: the .ai-memory.toml routing marker (workspace/project), the recall/write routing snippet in CLAUDE.md/AGENTS.md, the ai-memory MCP server entry, and the global capture hooks. Includes the qmd→ai-memory migration for repos still on the old wiki/qmd stack, and a refresh flow that detects CLI↔server version skew and re-stages hooks to parity. Use when the user asks to set up ai-memory in a project (greenfield or brownfield), wire the MCP, enable auto-capture, migrate off qmd, diagnose with doctor, or upgrade/refresh an existing setup (local CLI + hooks) to the server's version.
Toggle "minions mode" — you become a coordinating agent that delegates all real work to background Codex minions (the codex:codex-rescue subagent) while you brief, verify, and own the git flow. Enforced by hooks that inject a coordinator directive on every prompt and deny direct Edit/Write outside coordination files. Use to turn the mode on/off/status, or to install/refresh its hooks. Superseeds the older "orchestrator" naming (which stays as a compatibility alias).
Catalog + orchestrator for a web application's usage (E2E) flows. Keeps the project's flow definitions and hands them, ONE at a time, to the `ux-persona` skill to validate usability in the browser. Use to "list the flows", "validate all flows as a user", "run the usability walkthrough", "create a new usage flow", or run flow walkthroughs with Webwright-style replayable evidence.
Embody a user persona and walk through ONE usage flow of a web application THROUGH THE UI (starting from the flow's entry point, never typing internal URLs), judging whether the journey is usable and recording actionable findings. Takes the flow as an argument. Use when you want to "test as a user", "check if it's usable", "walk flow X as a persona", "validate the usability of a screen/journey", or run a flow with Webwright-style replayable screenshots/log evidence.
Author and edit Excalidraw scene files (`.excalidraw`): the JSON element model (rectangle, text, arrow), two-way arrow binding, ids/z-order, coordinates & sizing, groups, and reading/updating an existing scene. Two paths — by hand for small scenes/edits, or programmatically via `scripts/` which builds scenes with Excalidraw's own `convertToExcalidrawElements`, renders a faithful preview with `exportToSvg`, and lints geometry. Use whenever you create or modify a `.excalidraw` file directly (not through the editor UI). Mermaid is a supported INPUT for standard diagrams, not the file format.
Check your work with a verification sub-agent that runs direct oracles first (build/test/typecheck/lint/run-the-app), re-reads the changed code, and returns a schema-validated PASS/FAIL verdict — not prose to grep. Spawns one verifier for small diffs, or parallel lenses (BARRIER) for larger or security/auth/data-boundary changes, then fixes issues and re-verifies under a SEEN ledger until it passes. Use when asked to "check work", "verify changes", "self-verify", "/work-check", "/check", "/verify", or "/self-verify".
LOOP-shaped discovery pattern: repeat rounds of parallel finders (bugs, edge cases, sites, opportunities, missing items) until K consecutive *qualifying* rounds produce nothing new. Each round is a parallel fan-out + a real dedup BARRIER against a persistent seen[]; an oracle gates the seed, every item, and final completeness. Use when the total size of the set is unknown: "find all X", "enumerate edge cases", "discover all places that do Y". Invoke via /work-exhaust.