conversation-ux

Provide design patterns for multi-conversation chat UX with branching and history-aware navigation.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/esperie/new-project --skill conversation-ux
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: conversation-ux
Source: https://github.com/esperie/new-project/tree/main/.claude/skills/22-conversation-ux
Command: npx skills add https://github.com/esperie/new-project --skill conversation-ux

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides structured guidance for implementing advanced Conversation UX patterns, enabling multi-conversation management, branching threads, context switching, and organized chat history.

Core Features & Use Cases

  • Multi-conversation management: orchestrate parallel discussions within a unified UI to keep contexts separate and searchable.
  • Branching and lineage: support for forking conversations at precise turns with parent-child relationships and visual cues.
  • Context switching and history: techniques to preserve, swap, and reference prior turns while maintaining user flow.
  • Design patterns and references: practical UI patterns, navigation metaphors, and implementation tips for enterprise chat tooling.

Quick Start

Use conversation-ux to bootstrap a multi-conversation workspace with branches starting from a specific turn and a tree-view navigation pattern.

Frequently Asked Questions about conversation-ux

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement branching in an AI chat interface to fork conversations at specific turns?

Branching in an AI chat interface is implemented by establishing parent-child relationships at precise turns, using visual cues to indicate lineage and enabling context inheritance to preserve prior thread history when forking conversations.

What are the best UX patterns for managing multiple parallel AI chat conversations in an enterprise application?

Multi-conversation management UX patterns utilize a unified interface with tree-view navigation, keeping contexts separate and searchable while enforcing best practices for seamless context switching across parallel discussions.

Does this conversation UX approach support persistent context and history-aware navigation for enterprise chat?

Yes, this conversation UX approach supports persistent context and history-aware navigation by providing techniques to preserve, swap, and reference prior turns while maintaining user flow in enterprise chat tooling.

How do I preserve chat history context when switching between different conversation threads?

Preserving chat history context when switching threads involves applying context inheritance techniques and tree-view navigation patterns that maintain user flow while swapping and referencing prior turns across conversations.

When should I use a tree-view navigation pattern for multi-conversation chat history?

Tree-view navigation is used for multi-conversation chat history when you need to visualize branch lineage and manage forking conversations, ensuring organized navigation across complex enterprise chat interfaces with persistent context.