quasarframework/agent-skills

quasar-electron-development

Build, configure, secure, debug, test, package, and release Quasar desktop applications using Electron on Windows, macOS, and Linux.

View source
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

Quasar Electron Development

Use this skill with quasar-development for renderer UI and shared application concerns.

Map the process boundary

  1. Inspect quasar.config.* > electron, src-electron/electron-main.*, every preload script, IPC definitions, packaging tool, and updater strategy.
  2. Read the current Quasar Electron documentation and Electron security guidance.
  3. Add the mode with quasar mode add electron.
  4. Identify which code runs in main, preload, and renderer before editing.

Enforce Electron security

  • Keep contextIsolation enabled and renderer Node integration disabled.
  • Expose a narrow, typed preload API through contextBridge; never expose raw ipcRenderer, filesystem, shell, or process objects.
  • Validate IPC sender, channel, arguments, paths, URLs, and return data in the main process.
  • Do not enable the deprecated remote module.
  • Restrict navigation, new windows, permissions, protocols, and external URL opening. Allowlist schemes and destinations.
  • Apply a strong Content Security Policy and avoid loading remote executable content.
  • Treat renderer input as untrusted even when the app is local.
  • Resolve packaged assets with Quasar's supported Electron runtime helpers when applicable.

Package deliberately

  • Keep main/preload dependencies and native modules in the correct package scope.
  • Rebuild and test native modules for each target architecture.
  • Configure application identity, icons, file associations, protocols, signing, notarization, and artifact names for each OS.
  • Design auto-update signing, rollout, rollback, and migration behavior before enabling it.

Validate

  1. Run quasar dev -m electron and exercise main/preload/renderer interactions.
  2. Add tests around IPC validation and privileged operations.
  3. Build with quasar build -m electron using the configured packager.
  4. Install and launch packaged artifacts on every supported OS; test upgrade/uninstall behavior where relevant.
  5. Run tests, typecheck, lint, formatting, dependency audit, and inspect the packaged file set.
from this repository

More skills

All skills
quasarframework
Community

quasar-bex-development

Build, configure, secure, debug, test, and package browser extensions with Quasar BEX mode. Use for extension manifests, Manifest V3, background service workers, content scripts, injected page scripts, popup and options pages, permissions, cross-context messaging, BEX bridge, Chrome or Firefox targets, store packaging, and quasar dev or quasar build -m bex workflows.

installs
1
GitHub stars
1
Updated
Aug 19
quasarframework
Community

quasar-capacitor-development

Build, configure, debug, test, and release Quasar mobile applications using Capacitor for Android and iOS. Use for Quasar Capacitor mode, native projects, Capacitor plugins, permissions, deep links, app lifecycle, device testing, icons and splash screens, signing, stores, live updates, and quasar dev or quasar build -m capacitor workflows.

installs
1
GitHub stars
1
Updated
Aug 19
quasarframework
Community

quasar-development

Build, debug, test, and maintain Quasar Framework applications using Vue 3 and Quasar CLI with Vite. Use for Quasar components, composables, plugins, boot files, routing, state management, layouts, forms, theming, configuration, TypeScript, accessibility, testing, builds, dependency updates, and general Quasar application architecture. Pair with a mode-specific Quasar skill for SPA, SSR, SSG, PWA, Capacitor, Cordova, Electron, or BEX work.

installs
1
GitHub stars
1
Updated
Aug 19
quasarframework
Community

quasar-pwa-development

Build, configure, debug, test, and deploy Quasar Progressive Web Apps. Use for Quasar PWA mode, web app manifests, installability, service workers, Workbox GenerateSW or InjectManifest, offline behavior, caching, updates, push-related integration, icons, PWA with SSR or SSG, and quasar dev or quasar build -m pwa workflows.

installs
1
GitHub stars
1
Updated
Aug 19