5건 · 관련도순
Build workflows on OpenServ where multiple AI agents share tasks and pass results between steps. Examples cover research, writing, and image creation, with guidance on finding agents, setting dependencies, and connecting sequential or parallel work.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Use for AI-assisted Unity work that needs live repo discovery, project-derived routing, runtime-owner proof, runtime-visible output hard stops, runtime numeric proof for repeated visible-output failures, state-step guards, multi-agent scope ownership, modular C#/asmdef safety, UI/scene/visual asset gates, data-first content changes, validation, cleanup proof, or durable workflow rules. Best when agents must prove the actual folder/module/scene/prefab/runtime owner before editing, especially runtime UI, generated assets, code graphs, tutorial/state flows, guided selection/action flows, overlay/dim source-bound mistakes, coordinate conversions, focus/highlight/marker/HUD alignment, predictive lead aiming, ballistic trajectories, spatial IoU verification, or repeated "fix still not visible" failures.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build reusable agent workflow patterns — subagents with scoped briefs, event hooks, slash commands, and session management. Use when turning one-off agent tasks into repeatable, composable workflows.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when designing retryable or crash-resilient agent workflows, especially when tools can send, charge, publish, provision, or otherwise create duplicate side effects.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Chooses and designs developer surfaces for an agentic product: SDK, CLI, MCP, GUI, API, webhooks, and pd tube-style listener/sender workflows. Use when deciding why a user belongs in an SDK versus CLI/MCP/GUI, planning Python SDK parity, or making agent invocation easy across languages. NOT for implementing the full SDK, generic API docs, or UI visual design.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.