conversation-ux
Skill0 starsChanged 8 months agoApache-2.0View on GitHub
Conversation UX patterns for AI applications including multi-conversation management, branching threads, context switching, and chat history organization. Use when asking about 'conversation UX', 'multi-conversation', 'chat threads', 'conversation branching', 'chat history', 'context switching', 'Lark-style chat', 'conversation management', or 'thread navigation'.
In this repository37 other files it gives its agents.
- .claude/rules/agents.mdAGENTS.md
- .claude/guides/claude-code/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- core-sdkSkill
- dataflowSkill
- nexusSkill
- kaizenSkill
- kailash-mcpSkill
- cheatsheetsSkill
- development-guidesSkill
- nodes-referenceSkill
- workflow-patternsSkill
- deployment-gitSkill
- frontend-integrationSkill
- testing-strategiesSkill
- architecture-decisionsSkill
- code-templatesSkill
- enterprise-infrastructureSkill
- validation-patternsSkill
- gold-standardsSkill
- security-patternsSkill
- flutter-patternsSkill
- interactive-widgetsSkill
- enterprise-ai-uxSkill
- uiux-design-principlesSkill
- value-auditSkill
- ai-interaction-patternsSkill
- eatp-referenceSkill
- coc-referenceSkill
- 29-pactSkill
- claude-code-patternsSkill
- error-troubleshootingSkill
- kailash-mlSkill
- kailash-alignSkill
- co-referenceSkill
- managementSkill
- projectSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 177
Use this skill when:
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Conversation UX Patterns
Production-ready UX patterns for managing complex conversational interfaces including multi-thread management, branching conversations, and context switching.
Overview
Conversation UX patterns for:
- Multi-conversation management
- Thread branching and navigation
- Context switching strategies
- History organization
- Session persistence
Reference Documentation
Multi-Conversation Patterns
- multi-conversation-patterns - Lark-style conversation UX
- Research insights
- Design patterns
- Implementation strategies
- Navigation patterns
Quick Patterns
Conversation List Structure
class ConversationList extends StatelessWidget {
@override
Widget build(BuildContext context) {
return ListView.builder(
itemBuilder: (context, index) {
return ConversationTile(
title: conversation.title,
preview: conversation.lastMessage,
timestamp: conversation.updatedAt,
unreadCount: conversation.unreadCount,
isPinned: conversation.isPinned,
avatar: conversation.avatar,
);
},
);
}
}Branching Conversation Model
class Conversation {
final String id;
final String? parentId; // null for root conversations
final List<Message> messages;
final DateTime createdAt;
final String title;
final ConversationState state;
// Branch from a specific message
Conversation branch(Message fromMessage) {
return Conversation(
parentId: this.id,
branchPoint: fromMessage.id,
messages: [fromMessage.copy()], // Copy message as new root
);
}
}Context Switching Pattern
class ConversationProvider extends ChangeNotifier {
Conversation? _active;
final List<Conversation> _recent = [];
void switchTo(Conversation conversation) {
if (_active != null) {
_addToRecent(_active!);
}
_active = conversation;
notifyListeners();
}
// Quick switch maintains context
void quickSwitch(int recentIndex) {
if (recentIndex < _recent.length) {
final target = _recent[recentIndex];
_recent.removeAt(recentIndex);
switchTo(target);
}
}
}Navigation Layout (Lark-Style)
┌───────────────┬─────────────────────────────────────────────┐
│ │ │
│ SIDEBAR │ CONVERSATION │
│ │ │
│ ┌───────────┐ │ ┌─────────────────────────────────────┐ │
│ │ + New │ │ │ Context: Project Alpha │ │
│ └───────────┘ │ └─────────────────────────────────────┘ │
│ │ │
│ PINNED │ ┌─────────────────────────────────────┐ │
│ ├─ Project A │ │ User: How do I... │ │
│ └─ Important │ └─────────────────────────────────────┘ │
│ │ │
│ TODAY │ ┌─────────────────────────────────────┐ │
│ ├─ Chat 1 │ │ AI: Here's how... │ │
│ └─ Chat 2 │ │ │ │
│ │ │ [Branch from here] │ │
│ YESTERDAY │ └─────────────────────────────────────┘ │
│ └─ Chat 3 │ │
│ │ ┌─────────────────────────────────────┐ │
│ OLDER │ │ [Input Area] │ │
│ └─ Archive │ └─────────────────────────────────────┘ │
│ │ │
└───────────────┴─────────────────────────────────────────────┘Thread Branch Indicator
class BranchIndicator extends StatelessWidget {
final int branchCount;
final VoidCallback onTap;
@override
Widget build(BuildContext context) {
if (branchCount == 0) return SizedBox.shrink();
return GestureDetector(
onTap: onTap,
child: Container(
padding: EdgeInsets.symmetric(horizontal: 8, vertical: 4),
decoration: BoxDecoration(
color: Colors.blue.withOpacity(0.1),
borderRadius: BorderRadius.circular(12),
),
child: Row(
mainAxisSize: MainAxisSize.min,
children: [
Icon(Icons.call_split, size: 14),
SizedBox(width: 4),
Text('$branchCount branches'),
],
),
),
);
}
}Conversation States
| State | Description | Visual Indicator |
active | Currently selected | Highlighted background |
recent | Used in last 24h | Normal styling |
archived | Older conversations | Muted styling |
pinned | User-marked important | Pin icon + top section |
branched | Has child threads | Branch icon |
CRITICAL Gotchas
| Rule | Why |
| ❌ NEVER lose conversation context | User frustration |
| ✅ ALWAYS auto-save drafts | Prevent message loss |
| ❌ NEVER force linear navigation | Allow quick switching |
| ✅ ALWAYS show branch points | Navigation clarity |
When to Use This Skill
Use this skill when:
- Building multi-conversation chat apps
- Implementing conversation branching
- Designing chat history management
- Creating context-aware navigation
- Building Slack/Discord-style interfaces
Related Skills
- 20-interactive-widgets - Widget systems
- 21-enterprise-ai-ux - Enterprise patterns
- 19-flutter-patterns - Flutter implementation
Support
For conversation UX questions, invoke:
uiux-designer- UX decisionsflutter-specialist- Flutter implementationreact-specialist- React/web implementation
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

