القائمة
Verifies nontrivial MixJam renderer changes against the built Chromium surface using pixels, computed styles, and canvas sampling.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | verify |
| description | Verifies nontrivial MixJam renderer changes against the built Chromium surface using pixels, computed styles, and canvas sampling. |
Verify renderer changes against the production bundle. Unit tests stub canvas, so theme, CSS, drawing, and tracker behavior need evidence from real Chromium.
ELECTRON_RUN_AS_NODE from the command environment when launching
Electron; the Chromium-only path is unaffected.npm run build and require a clean exit.out/renderer with node scripts/serve-static.mjs <port> in a
background process.tmp/verify-<slug>.mjs inside the repository so Playwright resolves
the local node_modules.tmp/verify-<slug>/.Inject a mock window.backendAPI with page.addInitScript before page.goto.
Copy its shape from tests/e2e/fixtures.ts and compare it with
src/shared/backend-api.ts. Assert the feature fed by each mocked method; app
boot alone does not prove the mock is complete.
page.locator('.theme-selector').selectOption('<key>').DragEvent('drop') on
.tracker-lane-canvas. Attach a DataTransfer whose
application/mixjam-sample value is serialized FooterSampleDetail.getComputedStyle(document.documentElement).getImageData; ignore pixels with alpha below
250 before comparing exact lowercased theme colors.rgb(...), not unresolved CSS
variables.devicePixelRatio when sampling coordinates.Verification is complete when the production build passes, the relevant user
states are driven in Chromium, every changed visual or interaction contract has
an objective assertion, screenshots and an evidence report exist under the
run-specific tmp/verify-<slug>/ directory, and the background server is
stopped. Report exact failed assertions without claiming verification passed.
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.