/**
 * open-claude-design / opencode
 *
 * OpenCode replica of the Claude open-claude-design workflow. Orchestrates
 * the design skill ecosystem (impeccable, critique, shape, polish, audit,
 * etc.) into a deterministic 5-phase pipeline:
 *
 *   Phase 1: Design System Onboarding — extract tokens, build Design.md (HIL)
 *   Phase 2: Import — aggregate text/URL/file references
 *   Phase 3: Generation — produce first design version
 *   Phase 4: Refinement Loop — bounded iterate with critique + user feedback
 *   Phase 5: Export/Handoff — HTML export + Claude Code handoff bundle
 *
 * OpenCode-specific concerns (see references/failure-modes.md):
 *
 *   • F5 — every `ctx.stage()` is a FRESH session. Every specialist receives
 *     its required context verbatim in its first prompt.
 *   • F3 — `result.data!.parts` is a heterogenous array (text/tool/reasoning/
 *     file parts). Use `extractResponseText()` to filter to text parts only;
 *     concatenating raw `parts` produces `[object Object]` strings.
 *   • F6 — every prompt explicitly requires trailing prose so transcripts and
 *     `extractResponseText()` reads are never empty.
 *   • F9 — `s.save()` receives the unwrapped `{ info, parts }` payload from
 *     `result.data!`; passing the full `result` breaks downstream reads.
 *
 * Sub-agents are dispatched via the `agent` parameter on
 * `s.client.session.prompt()` (OpenCode's SDK-native way to route a turn
 * to a named sub-agent).
 *
 * See claude/index.ts for the full topology diagram and design rationale.
 *
 * Run: atomic workflow -n open-claude-design -a opencode "design a dashboard"
 */
declare const _default: import("../../../index.ts").WorkflowDefinition<"opencode", "prompt" | "reference" | "output-type" | "design-system">;
export default _default;
//# sourceMappingURL=index.d.ts.map