菜单
Autonomous UX improvement waves — launch 4 parallel agents per wave, audit every 5 waves, commit fixes. For Queen UI chat & network polish.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | ux-wave |
| description | Autonomous UX improvement waves — launch 4 parallel agents per wave, audit every 5 waves, commit fixes. For Queen UI chat & network polish. |
You are an autonomous UX improvement engine. DO NOT ASK — JUST DO.
User says: "как проснешься подумай как улучшить" or /ux-wave
swift build 2>&1 | grep -E "^(Build|error:)" — must be cleanEach agent gets:
cd /Users/playra/trinity-w1/apps/queen && swift build 2>&1 | tail -20run_in_background: truegit add ... && git commit -m "fix(queen): ..."ChatScreen.swift (~6500 LOC) — main chat UI, extracted sub-viewsChatClient.swift (~2600 LOC) — streaming, retry, failoverChatSidebar.swift (~1500 LOC) — thread list, filters, exportThreadStore.swift (~1000 LOC) — persistence, search, archiveChatThread.swift (~290 LOC) — data modelsModelProvider.swift (~360 LOC) — models, Ollama, failoverNetworkLog.swift (~380 LOC) — metrics, circuit breakerMarkdownTextView.swift (~1100 LOC) — markdown rendererTheme.swift (~150 LOC) — adaptive colors, appearance modeTrinity Bridge manual — architecture, endpoints, commands, patterns for Perplexity-Railway-Mac-Claude Code channel. Reference for all AI agents.
Generate Zig or Verilog code from VIBEE specifications. Use when creating or updating .tri specs and regenerating code.
GOD MODE — Agent monitoring dashboard. Shows swarm status, task queue, pipeline compliance, circuit breakers, git activity, and rule violations.
Generate Zig or Verilog code from VIBEE specifications. Use when creating or updating .tri specs and regenerating code.
HEALER — diagnose, heal, commit dirty files, monitor junk & docs & duplicates, report honestly. Every loop = action + proof.
Agent swarm development dashboard — live Railway containers, issue queue, PR pipeline, JSONL events, pool utilization, and queue drain status. Use when checking agent dev tasks, spawning status, or monitoring issues #315-#319.