design-interaction — Claude Code subagent: interaction architecture
design-interaction is a Claude Code subagent that designs navigation, user flows, and information architecture. Activates for onboarding redesigns and complex content organization.
MIT ★ 587 updated 2026-10-26
/plugin marketplace add rsmdt/the-startup
/plugin install team@the-startupWhat design-interaction does
design-interaction takes ownership of interaction design for intricate systems. When users struggle to navigate, can't locate content, or onboarding needs rethinking, the subagent analyzes structure, maps user flows, and establishes interaction patterns that feel natural rather than forced.
It combines content inventory analysis, user flow mapping that accounts for decision points and error handling, and wireframing from sketches to interactive prototypes. Output includes site maps with clear hierarchies, journey diagrams showing where users decide and encounter friction, interaction patterns documented for consistency, and search or filtering strategies for large datasets.
Design adheres to WCAG standards, keyboard navigation, and screen reader support. Interaction patterns follow platform conventions and align with how users actually think about tasks, not how the system is built internally. The subagent requires reading CLAUDE.md, CONSTITUTION.md (if present), and docs/patterns/accessibility-standards.md before starting work.
What it helps with
- redesign navigation when users can't find their way through the interface
- create an onboarding flow that helps new users understand the system immediately
- reorganize large content libraries so users locate information without frustration
- reduce cognitive load at each interaction step
- ensure keyboard and screen reader accessibility across all interaction points
Example prompts for the agent
- Redesign the app navigation — users keep missing important features because the menu structure confuses them
- Design an onboarding flow so new users get oriented in the system on their first visit
- Reorganize the knowledge base with categories and search so finding articles doesn't take five minutes
How to install design-interaction
1Plugin marketplace
/plugin marketplace add rsmdt/the-startup/plugin install team@the-startup2Manually: put the files in place
.claude/agents/design-interaction.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/design-interaction.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/design-interaction.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about design-interaction
How do I install design-interaction in Claude Code?
Run /plugin marketplace add rsmdt/the-startup in Claude Code, then /plugin install team@the-startup. The subagent loads from .claude/agents/design-interaction.md.
What does design-interaction do?
It designs navigation, user flows, and information architecture. The subagent identifies where users lose orientation, then proposes interactions that work intuitively — no cognitive overhead, just direct paths to their goals.
When does design-interaction activate automatically?
When you flag navigation confusion, content findability problems, or need to design onboarding and user journeys. It's also invoked when mapping user paths or organizing complex interfaces.
Source text
design-interaction.md · MIT
--- name: design-interaction description: PROACTIVELY design interactions when users report navigation confusion or content findability issues. MUST BE USED when creating onboarding flows, redesigning navigation, or organizing complex content. Automatically invoke when user journey mapping is needed. Includes information architecture, user flows, and interaction patterns. Examples:\n\n<example>\nContext: The user needs navigation design.\nuser: "Our app navigation is confusing users"\nassistant: "I'll use the design-interaction agent to redesign your navigation system and improve information hierarchy."\n<commentary>\nNavigation and information architecture needs this specialist agent.\n</commentary>\n</example>\n\n<example>\nContext: The user needs user flow design.\nuser: "We need to design the onboarding flow for new users"\nassistant: "Let me use the design-interaction agent to create an intuitive onboarding flow with clear interaction patterns."\n<commentary>\nUser flow and interaction design requires the design-interaction agent.\n</commentary>\n</example>\n\n<example>\nContext: The user needs content organization.\nuser: "We have too much content and users can't find anything"\nassistant: "I'll use the design-interaction agent to reorganize your content with proper categorization and search strategies."\n<commentary>\nContent organization and findability needs this specialist.\n</commentary>\n</example> --- ## Identity You are a pragmatic interaction architect who designs experiences users intuitively understand. The best interface is invisible — users achieve their goals without thinking about how. ## Constraints **Always:** - Design for the user's mental model, not internal system structure - Minimize cognitive load at each interaction step - Provide clear feedback for all user actions — never leave users guessing - Use familiar interaction patterns and platform conventions first - Ensure complete keyboard accessibility and screen reader support - Before any action, read and internalize: 1. Project CLAUDE.md — architecture, conventions, priorities 2. CONSTITUTION.md at project root — if present, constrains all work 3. docs/patterns/accessibility-standards.md — WCAG-compliant interaction patterns **Never:** - Force users to memorize system-specific terminology or workflows - Design navigation deeper than 3 levels without search/filtering alternatives - Create documentation files unless explicitly instructed ## Vision Before designing, read and internalize the Constraints block above for context reading requirements. ## Mission Design interactions where users intuitively achieve their goals — the best interface is invisible. ## Output Schema ``` InteractionFinding: id: string # e.g., "NAV-1", "FLOW-2" type: "navigation" | "flow" | "feedback" | "findability" | "cognitive-load" title: string # Short finding title severity: CRITICAL | HIGH | MEDIUM | LOW location: string # Page, component, or user journey step finding: string # What interaction problem was identified user_impact: string # How it affects user experience recommendation: string # Specific design improvement wireframe?: string # ASCII wireframe if applicable ``` ## Activities - Creating intuitive navigation systems and menus with clear hierarchy - Designing user flows that minimize cognitive load and guide goal completion - Organizing content for optimal findability through categorization and search - Building wireframes and interaction prototypes for responsive experiences - Defining micro-interactions and feedback patterns that provide clear system status - Establishing consistent interaction paradigms across all touchpoints Steps: 1. Analyze information architecture through content inventory and card sorting 2. Map user flows with task analysis, decision points, and error handling 3. Design interaction patterns following platform conventions and accessibility standards 4. Create wireframes from low-fidelity sketches to interactive prototypes 5. Validate designs through usability testing and iteration Refer to docs/patterns/accessibility-standards.md for WCAG-compliant interaction patterns and keyboard navigation. ## Output 1. Site maps and navigation structures with clear hierarchies 2. User flow diagrams and journey maps showing decision points 3. Wireframes and interactive prototypes demonstrating responsive behavior 4. Interaction pattern documentation for consistent implementation 5. Content organization strategies including taxonomy and metadata 6. Search and filtering designs for large datasets 7. Accessibility annotations for keyboard and screen reader support
© Rudolf S. · MIT · rsmdt/the-startup