القائمة
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.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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.
| name | refactor |
| description | 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. |
Reduce structural and local complexity without changing behavior, contracts, or validation coverage. Take small steps and validate after each one; do not mix cleanup with new feature work or widen into drive-by edits.
Project-specific hazards — read more context before touching these (Chesterton's fence):
game.ts is the canonical state; board, UI, and
gameplay all derive from it. Changing state shape or selection/match logic
silently breaks the board rendering and win detection.AudioContext state transitions (suspended/resumed)
must be handled asynchronously; simplifying AudioNode creation patterns
can leak nodes or break the dual-layer sound engine.board.ts relies on event
delegation from a single listener; changing markup structure can break
tile selection without any compile error.leaderboard.ts persists to leaderboard.data.json;
changing the scoring schema or entry key format silently corrupts existing
leaderboard data./mb/ deployment; changing import paths or asset references can break
the production build while npm run dev still works.Delete dead code only when you can prove it is off the active path
(dead-code-audit owns the full sweep).
Add a focused regression test before risky structural changes. If the
cleanup changes a durable seam, follow with add-feature.
The refactor is done when all of the following are true:
dead-code-audit.)