Към всички skills

ao-desktop-dev

Untrivial-ai · Данни и AI

Launch, restart, or troubleshoot the real AO Electron desktop app from this repository; run a checkout against isolated or real local AO data; combine PR branches for local UI review; and diagnose stale Electron processes, port conflicts, or preload bridge mismatches. Use whenever asked to run, open, show, or visually verify AO frontend changes in the actual desktop app rather than ao preview, dev:web, or mock data.

Оригинален текст · няма потвърден превод на български

Теми: agent-fleet · agent-ide · agent-orchestration · agent-swarm · claude-code · codex-cli · git-worktrees · multi-agent · orchestration · orchestrator · parallel-agents · parallel-coding · skills

Първо прочетете инструкцията.

Файлът се зарежда от посочения източник само по ваше действие. Можете да го прочетете тук, да го копирате или да го запазите като .md.

Оригинален SKILL.md
GitHub хранилище
Звезди на репото
12 301
Лиценз
Apache-2.0
Последна проверка на записа
20.09.2026 г.

Добавете в своя инструмент.

Командата отваря избора на skills от репозитория. Прочетете файла и условията на автора преди изпълнение.

npx skills add Untrivial-ai/agent-orchestrator

Страницата копира текст. Не инсталира и не изпълнява нищо на устройството ви.

Откъс от SKILL.md

Началото на файла на автора, без превод.

AO Desktop Dev

Run the Electron application from the current checkout and verify it in the native window. Keep the dev daemon, renderer, Electron preload, and selected data mode explicit so the user never reviews a mock or stale build by accident.

Choose the data mode

Ask only when the request does not make the desired data source clear.

  • Use isolated mode by default for implementation and destructive testing. Electron uses port 3002, ~/.ao/dev/running.json, ~/.ao/dev/data, and ~/.ao/dev/electron.
  • Use real-data mode only when the user explicitly asks to see this machine's actual AO projects or sessions. Start the checkout's dev daemon on the isolated dev port/run file while pointing AO_DATA_DIR at the real AO data directory. This is a separate daemon process using real data; do not describe it as the installed app's daemon.
  • Never try to attach an unpackaged Electron app directly to a packaged daemon from another checkout. The supervisor intentionally rejects daemon identity mismatches.
  • Warn before actions in real-data mode that create, terminate, rename, or otherwise mutate sessions. Merely opening and inspecting the UI is expected.
  • Real-data mode reads the same database as the installed app, so both windows show the same projects and sessions. Quit the packaged app first where possible: two daemons sharing one SQLite database can cross-talk, and acting on the wrong window runs unmerged code against real sessions. The dev window is marked with an Agent Orchestrator (dev) title, the default Electron dock icon, and an in-app dev badge — verify those markers before acting.

Preflight

  1. Work from the repository root and inspect git status --short --branch.
  2. Read frontend/package.json, frontend/src/main.ts, and frontend/forge.config.ts when the launch behavior may have changed. Treat source as authoritative over this skill.
  3. Confirm Node/npm and the Go version required by backend/go.mod are available. Run npm ci in frontend/ only when dependencies are absent or inconsistent; do not reinstall on every launch.
  4. Check for an existing dev instance from this exact checkout before starting another. Do not kill by process name alone, and never terminate every Electron process.

On macOS/Linux, inspect checkout-scoped processes and listeners with finite commands:

Целият SKILL.md в GitHub