transpose

Develop cross-platform UX strategy and context analysis for mobile, web, TV, kiosk, and voice.

116|9|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/ghaida/intent --skill transpose
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: transpose
Source: https://github.com/ghaida/intent/tree/main/skills/transpose
Command: npx skills add https://github.com/ghaida/intent --skill transpose

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Designing for multiple platforms is not just resizing; it requires rethinking interaction models and priorities across contexts.

Core Features & Use Cases

  • Context analysis framework: formalizes input methods, attention models, screen real estate, connectivity, and environment across platforms.
  • Platform-specific UX conventions: provides guidelines for iOS, Android, Web, TV, kiosk, embedded, and voice contexts.
  • Cross-context priority mapping: defines content priority shifts per desktop, mobile, TV, kiosk, and voice.
  • Cross-device journey continuity: outlines state transfer, handoff patterns, and session continuity between devices.
  • Progressive disclosure strategy per context: enables context-aware information density and task focus.

Quick Start

Draft a cross-context plan for a new feature, identifying the primary context, required conventions, and shoulder content.

Frequently Asked Questions about transpose

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

FAQPage Schema
How do I adapt UX design for multiple platforms like mobile, web, and TV?

A cross-platform UX strategy formalizes input methods, attention models, and screen real estate per device. It defines content priority shifts and platform-specific conventions for mobile, web, TV, and voice contexts instead of simply resizing layouts.

What is context analysis in cross-device UX design?

Context analysis in cross-device UX evaluates input methods, attention models, connectivity, environment, and session length across platforms. This framework enables progressive disclosure and context-aware information density for products spanning mobile, web, TV, kiosk, and voice.

How do I map content priority shifts across desktop, mobile, and kiosk interfaces?

Mapping content priority shifts requires defining primary tasks and shoulder content for each platform. A cross-context priority mapping strategy defines how information density and task focus change between desktop, mobile, TV, kiosk, and voice interfaces.

Does this approach support cross-device journey continuity and session state transfer?

Yes, cross-device journey continuity outlines state transfer, handoff patterns, and session continuity between devices. It ensures users maintain task progress when transitioning across mobile, web, TV, kiosk, and voice contexts within a single product ecosystem.

Can I use this framework to define UX conventions for embedded and voice contexts?

Yes, the framework provides platform-specific UX conventions for embedded and voice contexts. It defines how to handle varying input methods, attention models, and screen real estate constraints specific to voice interactions and embedded systems.

When should I not use responsive resizing for multidevice product design?

Responsive resizing is insufficient when products span mobile, web, TV, kiosk, and voice. You need a cross-context adaptation strategy when interaction models, input methods, attention spans, and connectivity environments fundamentally differ across target platforms.