/relationship-design

name: Agentic UX Design - Relationship-Centric Interfaces
description: Design AI-first interfaces that build ongoing relationships through memory, trust evolution, and collaborative planning, not just isolated screen interactions
when_to_use: when user explicitly requests agentic UX design, relationship-centric design, or mentions designing for memory, trust evolution, or long-term user relationships; ONLY use when specifically asked, not for general UI/UX tasks
version: 1.0.0

Agentic UX Design - Relationship-Centric Interfaces

Overview

**The paradigm shift from screen-centric to relationship-centric design.**

Traditional UX optimizes individual screens and isolated interactions. Agentic UX designs for ongoing relationships where systems learn, remember, and evolve alongside users across sessions, devices, and contexts.

**Core principle:** Every interaction builds on learned preferences and user history. Systems don't just respond—they develop understanding that compounds over time.

**Announce at start:** "I'm using the Relationship Design skill to create an agentic, memory-aware interface that builds long-term relationships with users."

When to Use

Use this skill when:

• Designing AI-powered applications, chatbots, or agent systems
• Building interfaces with repeated user interactions over time
• Creating systems that should learn from user behavior
• Rethinking traditional dashboards or SaaS products for the AI era
• Users complain about "starting over" every session
• You need to measure relationship quality, not just conversion rates
• Designing for trust evolution from transparency to autonomy
• Building collaborative planning features (human + AI co-creation)

**When NOT to use:**

• Simple one-time transactions with no user accounts
• Static content websites with no personalization needs
• Systems where memory/learning creates privacy concerns
• Interfaces where consistency > adaptation (e.g., medical equipment)

The Five Pillars of Agentic UX

1. Memory Revolution: From Static Preferences to Contextual Intelligence

**Old model:** Store static preferences (theme: dark, language: EN)

**New model:** Maintain dynamic, evolving relationship models

**Design for:**

• **Behavioral patterns:** Not just "user clicked X" but "user spends 20 min frustrated searching for Y on Tuesday evenings"
• **Emotional context:** Recognize frustration, urgency, exploration, decision-making modes
• **Temporal evolution:** How preferences change over weeks/months
• **Cross-session continuity:** Seamless continuation across devices and time

**Key question:** What would this experience look like if it remembered everything and got better over time?

2. Trust as a Design Material: The Three-Stage Evolution

Design interfaces that earn autonomy through graduated trust:

**Stage 1: Transparency Phase**

• Show all reasoning, decision processes, confidence levels
• Explain why the system suggests actions
• Reveal data sources and logic paths
• User wants to see everything

**Stage 2: Selective Disclosure Phase**

• Show reasoning only for important/uncertain decisions
• Quiet confidence for routine actions
• System learns when to show work vs. act confidently
• User trusts but verifies

**Stage 3: Autonomous Action Phase**

• Act independently with subtle confirmation patterns
• Clear escalation paths for mistakes
• User delegates entire decision categories
• Trust through consistent, aligned behavior

**Design patterns:**

• Progressive disclosure controls (let users adjust transparency level)
• Confidence indicators (system certainty visualization)
• Trust recovery protocols (clear undo/correction paths)
• Explain-on-hover for autonomous actions

**Key question:** How might users develop trust with this system gradually?

3. Relationship-Centric Architecture

**Design ongoing partnerships, not isolated transactions.**

**From:** User logs in → completes task → logs out → system forgets

**To:** System maintains continuous awareness of:

• User's ongoing goals and projects
• Communication preferences and patterns
• Learning from what works for this individual
• Relationship depth over time

**Implementation patterns:**

• **Memory visualization:** Show what system remembers (preferences, goals, patterns)
• **Context indicators:** Subtle cues showing how past interactions influence current suggestions
• **Forgetting controls:** User agency over what gets remembered vs. forgotten
• **Relationship timeline:** Visual representation of how the relationship evolved

**Key question:** What goals are users really trying to achieve, and how could an agentic system help them get there more effectively?

4. Systems That Plan Their Own Path

**From:** Design every possible user path explicitly

**To:** Design goal-alignment mechanisms where system dynamically constructs paths

**Agentic systems:**

• Maintain awareness of underlying user objectives
• Adapt interaction patterns based on what works
• Learn from imperfect demonstrations and natural language feedback
• Construct custom workflows for individual users

**Design for:**

• **Goal continuity:** Persistent awareness of user objectives across sessions
• **Proactive nudging:** Gentle next-step suggestions without intrusion
• **Collaborative planning:** Human + AI jointly developing approaches
• **Adaptive interfaces:** UI elements that evolve based on usage patterns

**Key question:** Can the system help users achieve goals they haven't fully articulated yet?

5. New Success Metrics: Beyond Conversion Rates

Traditional UX metrics (session duration, conversion rates, clicks) miss the point for agentic experiences.

**Measure instead:**

**Relationship Quality**

• Trust scores and delegation comfort
• User confidence in system decisions
• How often users second-guess the system
• Comfort with autonomous actions

**Compounding Value**

• Experience improvement over time
• Increasingly complex problems solved
• Better outcomes thr