mb

Run a long-form goal with judge-verified completion.

Creates or updates repository specs, acceptance criteria, durable decisions, and documentation for new work. Use when adding a feature or defining an ambiguous slice, when making architectural decisions or changing contracts (game state, leaderboard, audio, settings), or when recording durable context (decisions, glossary, conventions) for future engineers and agents.

Audits the MEMORYBLOX codebase for dead TypeScript code, orphan files, and unused symbols, triages findings into live dead code or false positives, and optionally removes provably dead code with focused validation. Use when the user asks for a dead-code scan, unused-code audit, orphan-file scan, unused-symbol triage, or cleanup from analyzer findings.

Remove AI-generated code slop from the current branch diff. Use when the user asks to deslop, clean up AI slop, remove unnecessary comments, strip defensive cruft, or flatten needless nesting.

Runs a disciplined diagnosis loop for hard bugs and performance regressions. Reproduce, minimise, hypothesise, instrument, fix, and regression-test. Use when the user says "diagnose this", the bug is flaky or not yet reproducible, root cause is unknown after triage, or a performance regression needs measurement before fixing.

Extremely strict maintainability review hunting code-judo restructurings — abstraction quality, the 1k-line rule, and spaghetti growth. Use when asked to review code, do a code review, audit changes, check for issues, or review uncommitted/staged changes. Covers diff-first review of pending changes and broader codebase audit.

Transfer session state to a fresh agent as a minimal, lossless state-transfer document.

Surface architectural friction in a codebase, package it as a visual HTML report, and grill through the strongest deepening opportunity.

Surgical, behavior-preserving cleanup for the MEMORYBLOX repository. Use when the user asks to refactor — reduce complexity or make code easier to change without adding features.

Quality-gate execution for repository hygiene and release readiness. Use when the user asks to run a quality gate, clean all Problems panel issues, fix lint/test/coverage failures, or verify the branch meets strict 90%+ coverage thresholds without suppression.

Teach the user a new skill or concept over multiple sessions, using this workspace as a structured learning space.

Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.