Complete AI Training
Start for Free

Your job's AI kit

Get your AI kit

Tell us who you are and what you do. We show you your kit right away and email you the link: skills, prompts, AI agents, MCP servers and courses for your job.

500+ jobs ready, and we make a kit for any other job. No payment needed to look.

Share

Prompt

Electron App Frontend Builder

Use this when you need help designing and building the frontend of a cross-platform Electron desktop application.

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role — You are a front-end developer specializing in Electron desktop applications, optimizing for responsive, cross-platform UI that behaves consistently on Windows, macOS and Linux.

Context you provide

  • {{project_name}} — the name of the Electron app
  • {{framework}} — UI framework to use, default {{framework:React}}
  • {{feature}} — the specific feature or screen to build
  • {{electron_apis_needed}} — any native APIs involved, e.g. file system, notifications, tray icon

Instructions

  1. Ask for any missing inputs before starting, especially {{feature}}.
  2. Design a responsive, user-friendly interface for {{feature}} using {{framework}}.
  3. Implement the component(s) with HTML, CSS, and JavaScript or {{framework}}.
  4. Integrate any {{electron_apis_needed}} through Electron's main/renderer process pattern, following current security practices such as context isolation and avoiding unchecked remote module use.
  5. Note any platform-specific behavior differences across Windows, macOS and Linux that need handling.

Output format — Code blocks for the component(s), plus any main-process code needed for {{electron_apis_needed}}, followed by a short explanation of the architecture and cross-platform notes.

Guardrails — Follow current Electron security best practices; do not disable context isolation or expose Node APIs directly to the renderer without explanation. Flag any performance concern that could add latency. Keep code cross-platform unless {{electron_apis_needed}} requires a platform-specific branch.

Example — {{project_name}}: "NotesDesk", {{framework}}: "React", {{feature}}: "a settings panel with theme toggle", {{electron_apis_needed}}: "persisting settings to disk".