design-experience

Designs user experiences from product intent and constraints for multi-agent and single-agent products.

1|2|Updated Jun 29, 2026
One-click install
npx skills add https://github.com/AesopScott/central --skill design-experience
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-experience
Source: https://github.com/AesopScott/central/tree/main/local-client/app-content/mindshare/skills/archive/design-experience
Command: npx skills add https://github.com/AesopScott/central --skill design-experience

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of translating complex product requirements and constraints into actionable user journeys and interfaces.

Core Features & Use Cases

  • Multi-Agent Product Design: Support for designing experiences in multi-agent product environments.
  • Single-Agent Product Design: Facilitate design for single-agent products without an M layer.
  • Design Elements: Incorporates user journeys, surfaces, information architecture, interaction states, accessibility requirements, and system handoffs.
  • Use Case: Utilize this Skill when developing an AI system that requires converting product intent, orchestration, and constraints into user interfaces and interaction flows.

Quick Start

Run the 'design-experience' skill to begin designing the user journey for your product.

Frequently Asked Questions about design-experience

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

FAQPage Schema
How do I translate product intent into user journeys and interfaces?

To translate product intent into user journeys and interfaces, you need a clear product promise, audience understanding, and system requirements to map out interaction states and information architecture.

What is the best way to design user experience for multi-agent product environments?

Designing user experience for multi-agent product environments involves mapping orchestration and constraints into specific interaction flows, surfaces, and system handoffs tailored for systems with an M layer.

How do I map information architecture and interaction states from product requirements?

Mapping information architecture and interaction states requires defining surfaces and accessibility requirements based on system constraints, converting product intent into actionable user flows.

Can I use this approach for single-agent products without an M layer?

Yes, you can design for single-agent products without an M layer by applying the same principles of journey mapping and interface design to translate product constraints into interaction states.

What do I need to start designing user journeys for an AI system?

To start designing user journeys for an AI system, you must provide a clear product promise, audience understanding, and system requirements to ensure accurate experience orchestration.