Your build starts here
Replace bracketed details with your own goal, context, and checks. Keep the first build small enough to inspect.
Implement [native desktop operation] for [user journey] in the existing cross-platform app.
Inspect the process architecture, preload or bridge layer, and current framework documentation. Define a narrow request and response contract. Validate arguments and the caller where appropriate. Keep rendering separate from privileged filesystem or operating-system work, and constrain untrusted content's access.
Verify valid input, a rejected request, an invalid path or resource, cancellation, and a failure in the privileged operation. Test the packaged build on available target platforms. Report changed boundaries, checks, deliberate platform differences, and remaining target-specific verification rather than exposing a general-purpose privileged transport.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 — Inter-process communication
- Electron — Context isolation
- Electron — Desktop application security
Documentation links checked .
Editorial review · October 28, 2026
Supported: Original, unexecuted bridge template. Narrow methods, context isolation, and validated senders follow Electron's documented boundaries; security effectiveness has not been tested.