kensaurus

Read-only backend-architecture audit and pattern advisor, gated by stack. Use when "audit backend architecture", "which pattern should I use", "am I over-engineering", or "sync vs event-driven". Enforced boundaries → enhance-arch-boundaries.

Read-only audit of payment and money-movement code, scoped from Stripe Checkout to in-house ledgers. Use when "audit payment system", "double charge / idempotency", "ledger / reconciliation", or "webhook / 3DS / PCI". IAP → audit-monetization-iap.

Audit and fix layouts at every breakpoint; desktop is not a wide phone. Use when "responsive audit", desktop looks stretched, there is no max-width, or 1440 looks like a phone. Touch-first build → design-mobile-first.

Cross-page UX audit of user stories, task completion, and IA. Use when "audit user flows", "IA audit", "can users find X", "navigation audit", or "funnel drop-off". Per-page heuristics → audit-ux.

Per-page UX audit with NN/g heuristics, microcopy review, and Google HEART. Use when evaluating usability, auditing microcopy, or assessing cognitive load. Cross-page flows/IA → audit-ux-journeys.

Audit an existing web app's motion, then apply one coherent, reduced-motion-safe pass. Use when "motion pass", "animate the app", or "add micro-interactions". One new animation → design-motion.

Measured fix pass on one screen or flow against seven Laws of UX: Fitts, Hick, Miller, Jakob, Zeigarnik, Goal-Gradient, Von Restorff. Use when "too many choices", "hard to tap", or "users drop off mid-flow". NN/g pass → enhance-web-ux.

NN/g-grounded fix of one existing page's flows. Use when "fix UX of /xxx" or "improve information density". Repo-wide slop plan → plan-antislop. Composition/type → enhance-web-ui. Reading level → enhance-readability. Heuristics only → audit-ux.

Plan-only GTM audit: detect monetization model, positioning, activation funnel, SEO/AEO and distribution, interview the founder one question at a time, emit a phased plan. Use when "GTM", "go-to-market", "get more users", "grow traffic", "should this be…

Read-only audit of where a repo is discovered: README first screen, npm / PyPI metadata and tarball, GitHub description, topics, social preview, plugin manifests, install one-liner. Use when "audit our npm listing", "README as landing page", "GitHub topics",…

Write honest bottom-funnel pages — "X vs Y", "alternatives to X", "migrate from X" — from verified facts, one unique page each, with a review date so they never rot into spam. Use when "comparison page", "vs page", "alternatives to", "competitor page",…

Versioned launch kit from the repo's real features: Show HN post, Product Hunt listing, Reddit / X / LinkedIn posts, article outline, release notes, calendar with UTM links. Use when "launch post", "Show HN", "Product Hunt listing", "announce this release",…

Apply-now growth loops on an existing product: "powered by" badge, shareable artifacts and templates, invite and referral credit, each with its own K-factor events. Use when "referral program", "viral loop", "powered by badge", "get users to invite".…

Apply-now lifecycle email driven by product events: activation nudges, trial-expiry track split by activated vs stalled, limit-reached upgrade, win-back — with exits, consent, and per-email events. Use when "onboarding emails", "trial expiry emails", "drip…

Apply-now activation pass: define the activation event, cut steps before first value, add empty-state templates, sample data, a short checklist; instrument signup→activated→habit. Use when "improve onboarding", "users sign up and leave", "time to value",…

Apply-now conversion pass for landing, pricing, and upgrade paths: hero matched to positioning, one CTA, real proof, tier packaging with anchor and annual toggle, upgrade prompts at value moments. Use when "pricing page", "improve conversion", "free to paid",…

End-to-end bug triage using Mushi MCP tools. Discover, investigate, and decide on fix dispatch — all without leaving your IDE.

Debug a Mushi Mushi install that is not working: SDK reports not arriving, MCP tools failing, LLM key exhaustion, story mapping or generated-test failures, or the auto-improve loop not running. Use when something in Mushi is broken or silent.

Set up and use Mushi Mushi, the bug mediator for AI-built apps: a user's bug report becomes a plain-English diagnosis and a paste-ready fix in Cursor or Claude Code over MCP. Use when installing the Mushi SDK, wiring the MCP server, managing Mushi keys, or…

Set up Mushi Mushi in a new project — install SDK, configure API keys, connect to the admin console, map user stories from a live app, and generate TDD tests. Use when the user asks to "set up mushi", "add mushi to my project", "connect mushi", "configure…

Pass/fail health check across a Mushi Mushi install: CLI credentials, API health, the report pipeline, the BYOK key pool and scheduled QA runs. Use when asked 'is mushi working', 'mushi health check', 'check mushi pipeline' or 'mushi deploy check', when the…

End-to-end Mushi Mushi smoke test: a report goes in, gets a plain-English diagnosis, then story mapping, test generation, approval, a QA run and the auto-improve loop are each exercised. Use when asked to test the Mushi integration, verify the full pipeline,…

Guided Mushi Mushi onboarding — install the right SDK for the detected framework, sign in, write env vars, and wire the MCP server into the editor. Use when "set up mushi", "install mushi", "add mushi to this project", "mushi onboarding", "wire mushi into…

Upgrade a host app's @mushi-mushi/* pin and apply the current SDK config surface (tunnel, ignoreErrors, beforeSend). Use when Dependabot or mushi upgrade --check reports drift, when MCP check_sdk_version returns outdated=true, or when ingest is ad-blocked.