Mixed 代码优化
- 作者仓库星标 108
- 许可证 MIT
- 作者仓库 ai-design-skills
Mixed-Initiative Flow
Mixed-initiative interaction is when both the human and the AI can take the lead. The designer decides who drives at each moment — and how control transfers between them.
Initiative Spectrum
Interactions sit on a spectrum:
- User-driven: The user gives instructions, the AI executes. The user controls pace, direction, and scope.
- AI-driven: The AI leads — asking questions, making suggestions, guiding the user through a process.
- Shared: Both parties contribute. The AI proposes, the user edits. The user starts, the AI finishes. Most AI products default to user-driven. The interesting design space is in shared and AI-driven modes.
Designing Initiative Handoffs
The moment control shifts from one party to the other is where most interactions fail. Design these transitions:
- Explicit handoff: "I've drafted three options. Which direction do you want to go?" — the AI clearly passes control.
- Implicit handoff: The AI stops generating and waits, signalling the user's turn through UI affordance.
- Negotiated handoff: "I could take this further or stop here for your input. What do you prefer?"
- Forced handoff: The AI encounters a decision it can't make and must hand back to the human.
When the AI Should Lead
The AI should take initiative when:
- The user is uncertain or exploring and needs guidance
- The task has a known best-practice sequence the AI can walk through
- The user has explicitly asked for help or coaching
- Proactive suggestions would save time without being intrusive
When the User Should Lead
The user should retain control when:
- The task involves subjective judgment or creative direction
- Stakes are high and errors are costly
- The user has strong domain expertise
- Privacy or consent decisions are involved
Anti-Patterns
- Initiative whiplash: Control bouncing back and forth too rapidly
- Passive AI: Never taking initiative even when it would help
- Overbearing AI: Taking over when the user wants control
- Unclear ownership: Neither party knows whose turn it is
Design Artefacts
- Initiative maps showing who leads at each stage
- Handoff trigger definitions (what causes a transfer of control)
- Autonomy level specifications per feature area
- 流狐分类
- 通用
- 作者声明 Agent
- 未找到明确声明；不据此推断已兼容或已测试
- 静态检查
- 94 / 100 · 启发式扫描，不代表运行安全
- 作者 / 版本 / 许可
- @Owl-Listener · MIT
- 流狐 Token 估算
- 低消耗
- 流狐接入估算
- 需简单配置
- 是否需要外部 API Key
- 未发现要求
- 检测到的系统要求
- 未声明
- 底层运行要求
- 未声明
- 检测到的文件与系统行为
-
- 只读
- Shell 执行
- 检测到的网络行为
- 仅限本地
- 安装命令数
- 无（仅作为资料）
档案由构建时根据 SKILL.md 与安装命令自动衍生，可能与作者实际意图存在差异。
需要注意： 未限定 allowed-tools，默认拥有全部工具权限。
作者没有在当前 SKILL.md 中定义固定输出样例。Interactions sit on a spectrum: User-driven: The user gives instructions, the AI executes. The user controls pace, direction, and scope. AI-driven: The AI leads — asking questions, making suggestions, guiding the user through a process.
The moment control shifts from one party to the other is where most interactions fail. Design these transitions: Explicit handoff: "I've drafted three options. Which direction do you want to go?" — the AI clearly passes control.
The AI should take initiative when: The user is uncertain or exploring and needs guidance The task has a known best-practice sequence the AI can walk through
The user should retain control when: The task involves subjective judgment or creative direction Stakes are high and errors are costly
Initiative whiplash: Control bouncing back and forth too rapidly Passive AI: Never taking initiative even when it would help Overbearing AI: Taking over when the user wants control
Initiative maps showing who leads at each stage Handoff trigger definitions (what causes a transfer of control) Autonomy level specifications per feature area
# Mixed-Initiative Flow
Mixed-initiative interaction is when both the human and the AI can take the lead. The designer decides who drives at each moment — and how control transfers between them.
## Initiative Spectrum
Interactions sit on a spectrum:
- **User-driven**: The user gives instructions, the AI executes. The user controls pace, direction, and scope.
- **AI-driven**: The AI leads — asking questions, making suggestions, guiding the user through a process.
- **Shared**: Both parties contribute. The AI proposes, the user edits. The user starts, the AI finishes.
Most AI products default to user-driven. The interesting design space is in shared and AI-driven modes.
## Designing Initiative Handoffs
The moment control shifts from one party to the other is where most interactions fail. Design these transitions:
- **Explicit handoff**: "I've drafted three options. Which direction do you want to go?" — the AI clearly passes control.
- **Implicit handoff**: The AI stops generating and waits, signalling the user's turn through UI affordance.
- **Negotiated handoff**: "I could take this further or stop here for your input. What do you prefer?"
- **Forced handoff**: The AI encounters a decision it can't make and must hand back to the human.
## When the AI Should Lead
The AI should take initiative when:
- The user is uncertain or exploring and needs guidance
- The task has a known best-practice sequence the AI can walk through
- The user has explicitly asked for help or coaching
- Proactive suggestions would save time without being intrusive
## When the User Should Lead
The user should retain control when:
- The task involves subjective judgment or creative direction
- Stakes are high and errors are costly
- The user has strong domain expertise
…作者原文负责流程事实；流狐只索引当前章节、要点、文件与命令。
章节 -> Initiative Spectrum → Designing Initiative Handoffs → When the AI Should Lead → When the User Should Lead → Anti-Patterns → Design Artefacts
要点 -> User-driven · AI-driven · Shared · Explicit handoff · Implicit handoff · Negotiated handoff · Forced handoff · Initiative whiplash
文件/命令 -> 原文未列出明确文件或命令
内容 SHA-256 -> ae69c0b6e67b
方法与流程
适用与边界
原文中的明确线索