Menu
Use for desktop UI validation in bop QA stage when the target app is Electron.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when designing or refactoring bop runtime/storage paths to maximize APFS COW/compression and prefer standard Rust crates over custom infrastructure.
Use when agents must write to .bop bundles safely and consistently without corruption.
Use when bop execution needs Auto-Claude MCP-style progress/status/discovery tracking.
Use when you need to map Auto-Claude MCP server logic to bop stages, workflows, and commands.
Use when a card or request includes a persona emoji (for example `🎯`, `🔒`, or `🚨`) and you need role-specific execution behavior with minimal token overhead.
Use when a bop stage needs external library/framework documentation lookup.
| name | bop-mcp-electron |
| description | Use for desktop UI validation in bop QA stage when the target app is Electron. |
Automate desktop validation for Electron targets during QA.
Requires Electron project capability and ELECTRON_MCP_ENABLED=true.
meta.stage=qa with bop inspect <id>.output/.bop merge-gate --once only after QA evidence is present.