electron-test-e2e
Use when an Electron work item needs test planning, unit or IPC coverage, preload contract tests, Playwright Electron E2E, multi-window checks, or packaged…
Skill by SuShuheng
Install
Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.
npx agentmarket install skill/sushuheng-electron-test-e2e
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Use cases: documents, testing
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.
- Tools
- No tools found
- Secrets
- None asked for
- Install scripts
- None found
Network hosts it talks to 1
codeload.github.com· found in install command
Files it touches
~/.claude/skills/electron-test-e2e
What's inside
- Skill name
electron-test-e2e- Description
- Use when an Electron work item needs test planning, unit or IPC coverage, preload contract tests, Playwright Electron E2E, multi-window checks, or packaged smoke evidence. Do not use to invent passing results, bypass a failing gate, or authorize release.
- License
- MIT
- Instructions
- 22 lines in SKILL.md · view on GitHub
Files (4)
- SKILL.md
- openai.yaml · agents/
- test-strategy.md · references/
- testing-standard.md · references/
SKILL.md (first lines)
# Electron Test E2E Build evidence from cheap deterministic layers to platform-specific packaged tests. 1. Read the sidecar contract, matching track/task, current implementation, `references/testing-standard.md`, and `references/test-strategy.md`. 2. Map each task requirement/risk to a test layer and expected observation. Frontend tasks cover renderer behavior; backend tasks cover service, IPC authorization/validation, and preload shape; integration tasks cover cross-track Electron flows and E2E. 3. Capture the intended failing test/reproducer before the behavior change. Use condition-based waits, deterministic system mocks, and clean resource teardown. 4. Record exact commands, UTC time, OS/architecture, exit code, counts, and safe artifact locations in the selected task's Evidence. Label unexercised platforms, architectures, signing, and packaged modes `NOT RUN`. 5. Create/advance integration tasks only after their declared frontend and backend deliverables are complete. Do not replace a product bug with a permissive test, fixed sleep, swallowed error, or deleted assertion.
From SuShuheng/making-things, MIT.
More from SuShuheng/making-things
- 0.502score
solution-architecture
SuShuheng
Use when an approved Electron PRD needs architecture, process ownership, data flow, IPC contracts, stack decisions, migration, or rollback design.
SkillCFreshness: C★ 1Claude Code +9 - 0.502score
electron-implementation
SuShuheng
Use when an approved Electron PRD, architecture, and plan are ready for feature implementation across main, preload, renderer, shared code, services, or…
SkillCFreshness: C★ 1Claude Code +9 - 0.502score
electron-ipc-security
SuShuheng
Use when Electron work adds or audits BrowserWindow privileges, preload APIs, IPC, filesystem, URLs, subprocesses, secrets, permissions, remote content, or CSP.
SkillCFreshness: C★ 1Claude Code +9 - 0.502score
product-prd
SuShuheng
Use when an Electron work item needs product discovery, a PRD, scoped requirements, user flows, or acceptance criteria before architecture.
SkillCFreshness: C★ 1Claude Code +9 - 0.502score
github-delivery
SuShuheng
Use when a verified work item explicitly requires Git branch creation, intentional commits, non-force push, pull-request handoff, or authorized artifact…
SkillCFreshness: C★ 1Claude Code +9 - 0.501score
making-things
SuShuheng
Use when the user explicitly requests a complete Electron workflow rather than a small edit or one-stage request.
SkillCFreshness: C★ 1Claude Code +9 - 0.497score
handon
SuShuheng
Use when a paused frontend, backend, or integration workstream must resume from its sidecar TRACK.md and HANDOFF.md records.
SkillCFreshness: C★ 1Claude Code +9 - 0.497score
electron-release
SuShuheng
Use when an accepted Electron work item needs packaging configuration, versioning, signing/notarization readiness, artifact checks, update metadata, or a…
SkillCFreshness: C★ 1Claude Code +9 - 0.497score
electron-review
SuShuheng
Use when an independent context must assess an Electron task, diff, security boundary, tests, or release evidence before acceptance.
SkillCFreshness: C★ 1Claude Code +9 - 0.497score
electron-debug
SuShuheng
Use when an Electron failure or confirmed review finding can be reproduced and needs root-cause analysis, a minimal fix, and regression verification.
SkillCFreshness: C★ 1Claude Code +9 - 0.497score
mts-more
SuShuheng
Use when the current host has dated WRITE_SUBAGENT: VERIFIED evidence and the user requests parent-supervised native-subagent TDD for one workstream task.
SkillCFreshness: C★ 1Claude Code +9 - 0.497score
mts-split
SuShuheng
Use when an approved Electron contract must split one feature into frontend, backend, and integration workstreams with TDD task records.
SkillCFreshness: C★ 1Claude Code +9
Signals
- Stars
- 1
- Forks
- 0
- Open issues
- 0
- Last commit (this folder)
- Jul 16, 2026 (3 months ago)
From GitHub (fetched Oct 24, 2026).
Details
- License
- MIT
- Repository
- github.com/SuShuheng/making-things
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
- Source
- GitHubgithub-graphql
More from SuShuheng
- 0.502score
solution-architecture
SuShuheng
Use when an approved Electron PRD needs architecture, process ownership, data flow, IPC contracts, stack decisions, migration, or rollback design.
SkillCFreshness: C★ 1Claude Code +9 - 0.502score
electron-ipc-security
SuShuheng
Use when Electron work adds or audits BrowserWindow privileges, preload APIs, IPC, filesystem, URLs, subprocesses, secrets, permissions, remote content, or CSP.
SkillCFreshness: C★ 1Claude Code +9 - 0.502score
electron-implementation
SuShuheng
Use when an approved Electron PRD, architecture, and plan are ready for feature implementation across main, preload, renderer, shared code, services, or…
SkillCFreshness: C★ 1Claude Code +9 - 0.502score
product-prd
SuShuheng
Use when an Electron work item needs product discovery, a PRD, scoped requirements, user flows, or acceptance criteria before architecture.
SkillCFreshness: C★ 1Claude Code +9 - 0.502score
github-delivery
SuShuheng
Use when a verified work item explicitly requires Git branch creation, intentional commits, non-force push, pull-request handoff, or authorized artifact…
SkillCFreshness: C★ 1Claude Code +9 - 0.501score
making-things
SuShuheng
Use when the user explicitly requests a complete Electron workflow rather than a small edit or one-stage request.
SkillCFreshness: C★ 1Claude Code +9
Cite this page
electron-test-e2e skill. Agent Mart. https://agentmart.dev/skills/sushuheng-electron-test-e2e (last updated 2026-10-24)