| name | electron-implementation |
| description | Use when an approved Electron PRD, architecture, and plan are ready for feature implementation across main, preload, renderer, shared code, services, or workers. Do not use for discovery, independent final review, speculative debugging, packaging approval, or publishing. |
Electron Implementation
Implement one selected sidecar task in its declared workstream while keeping
process boundaries intact.
- Read sidecar PRD, contract, matching
TRACK.md, selected TASK.md, and
references/process-boundaries.md. Confirm current branch/worktree and
task scope before editing.
- Follow the selected
mts-one or capability-gated mts-more mode. Observe
the smallest intended failing test before the smallest Green change.
- For an IPC slice, define shared schema, privileged service/handler, narrow
preload capability, and renderer use in that order. Validate privileged
inputs and senders; constrain paths, URLs, subprocesses, size, timeout, and
cancellation.
- Run focused tests and applicable broader verification. Attach Red/Green,
review, and result evidence to the selected task only. Route security work
to
electron-ipc-security and cross-track tests to electron-test-e2e.
Never import privileged Node/Electron APIs in renderer code, expose raw
platform objects, weaken isolation, or hide an unrun check. The parent Agent
maintains task records and commits; host brand grants no authority.
