Forge

Use the MJ Forge regression test harness to drive quality on every non-trivial change — TDD/BDD style: harness up first, failing test first, implementation second, green test confirms intent. Trigger this skill BEFORE starting any non-trivial dev work that touches packages/main, packages/renderer, packages/shared, or packages/preload — and AFTER making changes (to catch regressions early). The user has 268+ tests across four tiers (unit, integration, e2e, visual) wired into a fast pipeline at `npm run test:full`. Make sure to use this skill whenever the user asks you to fix, implement, refactor, add, or otherwise modify substantive code in this repo, even if they don't explicitly ask you to "run the tests" — they expect you to verify your work and to write the test FIRST when the change is feature-shaped. The dashboard at http://127.0.0.1:5188 is for the human to watch your progress; you should rely on programmatic mechanisms (npm scripts, structured JSON output) to drive and interpret runs.

Use this agent when building Electron features for MJ Forge — IPC handlers, main process services, preload bridge, window management, native OS integration, build/packaging, and security hardening. Covers the full main-process and desktop-shell layer.

Author a complete user-facing GitHub Wiki for the current repository. Triggers when the user wants to write, generate, refresh, or expand wiki documentation — phrases like "write the wiki", "build a github wiki", "generate user docs for the wiki", "set up our wiki", "add a wiki page for X", "/wiki". Use this whenever the user mentions GitHub wikis, project user documentation, end-user help pages, or wants to publish how-to / reference docs to github.com/<owner>/<repo>/wiki — even casually. Coordinates a small team of subagents that each own one page, then handles the .wiki.git clone-write-commit-push workflow.