AI Agent & Automation Workflows

Use when building an Electrobun app for distribution, setting up code signing, understanding platform-specific build requirements, or diagnosing build failures. Covers dev/canary/stable environments, all three platforms, toolchain prerequisites, artifact output, and CI/CD setup.

The complete electrobun.config.ts field reference. Use when editing config, looking up a specific option, understanding defaults, or configuring platform-specific behaviour.

Use when working on any Electrobun desktop app — BrowserWindow, BrowserView, events, app lifecycle, ApplicationMenu, Tray, and electrobun.config.ts. Activates automatically when editing Electrobun project files.

Use when running Electrobun in development mode — electrobun dev, --watch flag, hot reload, CEF devtools, debugging the renderer, or understanding the dev build cycle.

Use when scaffolding a new Electrobun project, choosing a template, or understanding what each template provides. Activates on electrobun init, new project setup, or template questions.

Use when working with the Electrobun Kitchen Sink testing app — running tests, understanding the feature manifest, navigating the test runner UI, operating playground windows, or adding new test coverage. Also activates for questions about the defineTest() pattern, AUTORUN mode, or the manifest generator/validator scripts.

Use when building Electrobun features for the milady-ai/milady project, submitting PRs that will be reviewed by milady's agent-review system, or understanding how the electrobun-dev SDLC pipeline integrates with milady's trust scoring, CI/CD, and automated reviewer. Covers trust tiers, code quality standards, PR format requirements, Biome compliance, and the milady release-electrobun.yml workflow.

The master index for the electrobun-dev Claude Code plugin. Use when starting a new Electrobun project, unsure which skill or command to use, wanting a full overview of what the plugin provides, or onboarding to the plugin ecosystem. Lists all 15 skills, 13 commands, and 11 agents with when-to-use guidance and decision trees.

Use when distributing Electrobun apps, configuring auto-updates, uploading artifacts, understanding update channels, or integrating the Updater API. Covers artifact naming, update.json format, bsdiff patch generation, upload targets, and the full Updater lifecycle.

Use when working with Electrobun's RPC system — defineElectrobunRPC, Electroview.defineRPC, ElectrobunRPCSchema types, bun-to-renderer and renderer-to-bun communication. Activates automatically when RPC code is present.

Use when building any complete Electrobun feature from idea to documentation. Explains the 8-stage agent pipeline — researcher, architect, planner, dev squad, QA engineer, test writer, alignment agent, docs agent — and how to orchestrate them with or without Claude Code agent teams.

Use when orchestrating multi-agent Electrobun feature development. Explains the electrobun-feature-team architecture — UI agent (views, RPC contract) followed by backend agent (bun-side wiring) — the RPC contract handoff format, and how to run the team using CLAUDECODEEXPERIMENTALAGENTTEAMS=1.

Use when writing Electrobun tests, adding test coverage to the Kitchen Sink, implementing the defineTest() pattern, generating new test suites, understanding what the kitchen sink tests, or reverse-engineering component behaviour from test source. Activates on test authoring, test framework, or test-driven development questions.

Use when working with WebGPU in Electrobun — GpuWindow, WGPUView, WGSL shaders, KEEPALIVE pattern, render loops, FFI pointer management, and GPU buffer serialization.

The master Electrobun development lifecycle guide. Use for any Electrobun project to understand where you are in the pipeline and what comes next. Links all stages together.

Use whenever a user wants to register or buy a custom domain for an Eliza Cloud app — including in the same request as building the app (\"build me X and put it on Y.com\"). Uses cloudflare as registrar, no human in the loop, paid from the user's existing cloud credit balance. Pairs with build-monetized-app (build first, then buy domain) and eliza-cloud-manage-domain (post-purchase: list, edit dns records, detach). Skip when the user is fine with the auto-assigned .apps.elizacloud.ai subdomain.

Use after a domain has been purchased through Eliza Cloud (via the eliza-cloud-buy-domain skill) when the user wants to look at, edit, or remove a domain or its DNS records. Covers org-wide domain listing, per-app DNS record CRUD on cloudflare-managed zones, status re-sync, external-attachment verification, and detaching a domain from an app. Use this skill any time the user references domains they already own (my domains, edit dns for myapp.com, delete that A record, is myapp.com still pointing at my app).

Use when spawning a Claude Code, Codex, Gemini, Aider, or other CLI task agent whose work needs parent Eliza runtime context.