菜单
This skill should be used when the user asks about the "electrobun development workflow", "electrobun pipeline", "electrobun lifecycle", "where am I in the electrobun pipeline", or needs guidance on what stage comes next in electrobun development.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
This skill should be used when the user asks to "build electrobun app", "electrobun build", "electrobun canary", "electrobun stable", "set up code signing", "electrobun distribution", or is diagnosing electrobun build failures. Covers dev/canary/stable environments, all three platforms, toolchain prerequisites, artifact output, and CI/CD setup.
This skill should be used when the user asks about "electrobun.config.ts", "electrobun config", needs the config field reference, wants to understand config defaults, or is configuring platform-specific electrobun behaviour.
This skill should be used when the user asks to "run electrobun dev", "electrobun development mode", "electrobun --watch", "hot reload electrobun", "CEF devtools", or is debugging the electrobun renderer or understanding the dev build cycle.
This skill should be used when the user is starting a new Electrobun project, is unsure which electrobun skill or command to use, wants an overview of the electrobun-dev plugin, or asks "which electrobun skill", "electrobun plugin guide", "electrobun overview". Lists all skills, commands, and agents with when-to-use guidance.
This skill should be used when the user asks to "electrobun init", "scaffold a new electrobun project", "new electrobun app", "electrobun template", or "start electrobun project". Activates on new project setup or template questions.
This skill should be used when the user asks about the "electrobun kitchen sink", "defineTest", "AUTO_RUN mode", "kitchen sink tests", "electrobun test runner", navigating playground windows, or wants to add new electrobun Kitchen Sink test coverage.
| name | electrobun-workflow |
| description | This skill should be used when the user asks about the "electrobun development workflow", "electrobun pipeline", "electrobun lifecycle", "where am I in the electrobun pipeline", or needs guidance on what stage comes next in electrobun development. |
| version | 1.0.0 |
┌──────────┐ ┌──────────┐ ┌──────────────┐ ┌───────────┐
│ INIT │ → │ DEV │ → │ BUILD │ → │ RELEASE │
│ │ │ │ │ │ │ │
│ template │ │ dev+watch│ │ canary/stable│ │ upload │
│ scaffold │ │ hot reload│ │ sign+notarize│ │ auto-update│
└──────────┘ └──────────┘ └──────────────┘ └───────────┘
Skill: Skill: Skill: Skill:
electrobun-init electrobun-dev electrobun-build electrobun-release
Command: (always-on) Command: Command:
/electrobun-init /electrobun-build /electrobun-release
When: Starting a new project from scratch.
Command:
electrobun init <project-name> --template=<template>
cd <project-name> && bun install
Success: bun start launches the template app.
→ Ready for Stage 2 when: Template runs, you've updated app.name and app.identifier.
Deep knowledge: See electrobun-init skill.
When: Building features — the majority of development time.
Commands:
bun run dev # → electrobun dev --watch
Success: App reloads automatically on save. Console output appears in terminal.
Key tools while in dev:
http://localhost:9222 (if using CEF renderer)view.openDevTools() for native WKWebView (macOS).ts lines→ Ready for Stage 3 when: Feature is complete, tested manually, and you're ready for a distributable build.
Deep knowledge: See electrobun-dev skill.
When: Creating a distributable build for testing (canary) or release (stable).
Commands:
# First time: set signing env vars
export ELECTROBUN_DEVELOPER_ID="Developer ID Application: ..."
export ELECTROBUN_APPLEID="you@example.com"
export ELECTROBUN_APPLEIDPASS="xxxx-xxxx-xxxx-xxxx"
export ELECTROBUN_TEAMID="XXXXXXXXXX"
# Canary (internal testing)
electrobun build --env=canary
# Stable (production)
electrobun build --env=stable
Success: artifacts/ contains .tar.zst, .patch, update.json, .dmg.
Skip signing for pipeline testing:
ELECTROBUN_SKIP_CODESIGN=1 electrobun build --env=canary
→ Ready for Stage 4 when: Artifacts are present and the built app runs correctly.
Deep knowledge: See electrobun-build skill.
When: Distributing the build to users and enabling auto-update.
Steps:
artifacts/ to release.baseUrlcurl <baseUrl>/macos-arm64-update.jsonSuccess: Users on the previous version get the update within their configured check interval.
Deep knowledge: See electrobun-release skill.
See electrobun-config skill for the complete electrobun.config.ts field reference.
app.version not bumped → Auto-updater won't detect a new release even after uploadbuild.views missing an entry → Renderer HTML loads but JS silently fails (Stage 2-3)bundleWGPU/bundleCEF not set for all platforms → Runtime crash on non-dev machine (Stage 3)release.baseUrl not set → No update.json generated, no patch created (Stage 3→4)update.json URL wrong → Auto-updater polls <baseUrl>/<os>-<arch>-update.json — no version in the filename| I want to... | Command | Skill |
|---|---|---|
| Start a new project | /electrobun-init | electrobun-init |
| Set up a new window with RPC | /electrobun-window | electrobun-rpc |
| Add WebGPU rendering | /electrobun-wgpu | electrobun-webgpu |
| Add an app menu | /electrobun-menu | electrobun |
| Check pipeline status | /electrobun-workflow | electrobun-workflow |
| Run a guided build | /electrobun-build | electrobun-build |
| Release to users | /electrobun-release | electrobun-release |
| Understand the full config | (auto) | electrobun-config |
| Debug a failure | (auto) | electrobun (debugger agent) |