设计协作评论与提及界面
为协作产品规划评论锚点、讨论串、成员提及和解决流程,并补充导航、异常状态与无障碍交互。
完整提示词
<context>
Comments in collaborative tools work when each thread is clearly tied to what it is about and has a lifecycle. The usual failures: comments anchored to text that later changes, leaving orphaned threads; a long flat list nobody can scan; mentions that suggest people who cannot see the item, so the mention silently fails; no distinction between open and resolved threads; and no way to see "what needs my reply" across items. Good design picks an anchoring model, makes open threads easy to find and close, checks access when someone is mentioned, and keeps history after resolve.
</context>
<task>
<collaboration_context>
{{collaboration_context}}
</collaboration_context>
Design for {{platform}}. If the commented object is unknown, ask and stop. Other gaps become assumptions marked [confirm].
1. **Anchoring model.** Selection, region or pin, or whole-item comments; how the anchor is shown in the content; what happens when the anchored content is edited, moved or deleted (keep thread with a "content changed" or "orphaned" marker).
2. **Comment entry.** How to start a comment (selection toolbar, shortcut, comment mode), composer behaviour, formatting kept minimal, attachments if needed, drafts kept when the user clicks away.
3. **Thread anatomy.** Author, time, text, replies (one level or nested, with a reason), reactions, edited marker, and the actions menu.
4. **Mentions.** Trigger character, suggestion list order (recent collaborators first), mentioning someone without access (offer to share or warn), groups or teams, and what the mentioned person receives.
5. **Resolve and lifecycle.** Resolve, reopen, delete, who can do each, what resolved threads look like and where they go, and whether resolving notifies.
6. **Overview and navigation.** Comment panel with filters (open, resolved, mentions me, unread), counts, jumping between threads, and an inbox of threads awaiting the user's reply.
7. **Edge states.** Many threads on one spot, deleted author, permission removed, offline comment queued, comment on a read-only or locked version.
8. **Accessibility.** Comments reachable without pointer selection, anchors announced, focus moves into and out of threads predictably, unread state not shown by colour alone.
</task>
<constraints>
- Mentioning someone must never silently fail; show access problems at the moment of mention.
- Do not invent notification channel strategy beyond the entry points; note where it connects to notification settings.
- Keep resolved threads recoverable; do not design resolve as delete.
{{> output/uncertainty}}
</constraints>
<output_format>
## Anchoring model
## Comment entry
## Thread anatomy
## Mentions
## Resolve and lifecycle
| Action | Who can | Result | Notifies |
## Overview and navigation
## Edge states
| Situation | What the user sees | Action |
## Accessibility
</output_format>可替换内容
- {{collaboration_context}}
- {{platform}}
- {{> output/uncertainty}}
- [confirm]
分类与标签
设计创意、协作工具、评论面板、成员提及、交互设计