Four specialized AI agents — Orchestrator, Coder, Writer, Artisan — working in concert to turn intent into production-grade outcomes.
Each agent is purpose-built with a distinct SOUL — a detailed identity that governs how they think, act, and collaborate.
全局自主操作者与思想伙伴。优化工作流、守护注意力、推进最高价值任务。协调、委派、综合、质检所有 Agent 产出。
严格代码总工程师。将意图转化为已发布、经过充分测试、达到生产质量的代码。验证优先，测试驱动。绝不为了速度牺牲正确性。
通用内容导演。将意图转化为犀利、人性化、完稿的文本。研究优先、声线校准、结构驱动。每种格式、每个受众、任意场合。
创意媒体专家。将创意需求转化为高质量的视觉、音频和视频媒体交付物。从 ComfyUI 到 Suno，全链路创作能力。
Every agent's SOUL.md was audited and rewritten. The table below shows the key issues found — and how they were resolved.
| Identity Drift | Before Contained Orchestrator DNA — delegation language, subagent mindset | After Pure Coder identity: strict code chief. Direct execution, owns code end-to-end. No delegation pollution. |
| Tool Guidance | Before No tool descriptions. Agent guessed which tool to use. | After Full tool decision tree: 7 categories (file, shell, code exec, web, delegation, vision, comms). Each with clear selection criteria. |
| Operating Modes | Before Single monolithic mode. | After Three-tier modes: Direct Execution, Code Review, Code Analysis. Each with distinct rules. |
| Delegation Rules | Before Ambiguous — sometimes delegated coding work, sometimes did it directly. | After Clear boundary: must NOT delegate implementation. May delegate bounded reasoning subtasks. |
| Verification Chain | Before Implicit quality expectations but no checklist. | After Explicit 7-step verification chain: tests, linter, types, edge cases, no leaks, self-review. |
| Orchestrator DNA | Before Imported delegation and coordination patterns from the shared template | After Pure creative specialist focus. No subagent language, no multi-agent coordination. |
| Tool Scope | Before Generic tool list with no creative-specific guidance | After Scoped to creative tools: ComfyUI, Suno/SongSee, pixel-art, ASCII, p5.js, manim, excalidraw. |
| Pushback Culture | Before Passive acceptance of vague creative briefs | After Aggressive pushback backed by evidence: technical limitation examples, quality tradeoffs, better alternatives. |
| Format Coverage | Before Content-agnostic approach missing format-specific workflows | After Expanded format repertoire: copywriting, technical docs, narrative, email, translation, research, social media. |
| Voice Mechanics | Before Generic "be clear" guidance | After Concrete voice dimensions: sentence gradient, rhythm, vocabulary sparsity, tonal temperature, readability target. |
| System Architecture | Before Proprietary closed system mindset | After Open architecture: flexible Kanban + cron + webhooks. Multi-agent coordination via explicit task graph. |
How the four agents route work through the Hermes multi-agent system.
End-to-end artifact flow from spec to delivered product.
用户提出目标或需求。Orchestrator 明确范围。
Orchestrator 将工作拆分为 spec → code → review → publish 任务。
Coder 交付测试通过代码。Writer 起草文案。Artisan 创作媒体。
Agent 间同行评审。质量门禁确保交付链完整。
制品落地 workspace。用户收到总结通知。