القائمة
Surgical, behavior-preserving cleanup for the MixJam Electron (MJE) 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 المهني
Structured design critique across usability, hierarchy, consistency, and accessibility. Use when the user shares a Figma link, screenshot, mockup, or asks for design feedback ("review this design", "critique this screen", "what do you think of this UI?"). Use after design-router when a theme has been selected and applied.
Runs a disciplined ablation workflow for MixJam Electron (MJE) bugs to prove which changed files or layers are actually required for a fix. Use when an MJE import, playback, or UI bug has a known pass/fail check but several edits may be involved, or when the user asks which change actually fixed it, what can be removed, or for the smallest proven fix.
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 (API, persistence, import, playback), or when recording durable context (glossary, conventions, trade-offs) for future engineers and agents.
Audits the MixJam Electron (MJE) codebase for dead TypeScript code, orphan files, and unused symbols across main and renderer processes, triages findings into live dead code or false positives, and optionally removes provably dead code with focused validation. Use for a dead-code audit, or for cleanup explicitly requested from analyzer findings.
Routes a requested UI visual direction to one bundled design theme. Use when building or restyling an interface that needs an explicit aesthetic.
Remove AI slop from every file in the repository while preserving behavior and genuine information.
| name | refactor |
| description | Surgical, behavior-preserving cleanup for the MixJam Electron (MJE) 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):
AudioContext state transitions (suspended/resumed)
must be handled asynchronously; simplifying AudioNode creation patterns
can leak nodes or break schedulingDelete 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.)