Your build starts here
Replace bracketed details with your own goal, context, and checks. Keep the first build small enough to inspect.
Review the native boundaries in [desktop feature] using the actual source. Identify the main or privileged process, renderers, preload code, and messages between them.
Trace which content can reach each exposed operation. Check argument validation, sender validation where relevant, navigation handling, externally opened links, and access to files or system capabilities. Distinguish isolation settings from the specific capabilities granted through the bridge.
Report concrete issues with a realistic trigger, affected code, and correction. Apply fixes within [scope] and verify rejected and successful requests. Check the packaged target where available, and state any platform-dependent behavior that remains unverified.Make this prompt yours
Replace bracketed fields with your goal, current behavior, and relevant evidence. Keep requirements that affect the task. Check the result against the acceptance criteria you supplied.
The docs behind it
These references explain the underlying concepts and APIs. The prompt templates and project plans are original examples to adapt to your own setup.
- Electron — Main, renderer, and preload process model
- Electron — Desktop application security
- Electron — Context isolation
Documentation links checked .
Editorial review · October 28, 2026
Supported: Original, unexecuted review template. Electron supports the main/renderer/preload distinctions and warns against unrestricted IPC exposure.