transpose

Adapts user experiences across platforms by rethinking interaction models, priorities, and context.

Updated Jul 21, 2026
One-click install
npx skills add https://github.com/rakedzior/rootine --skill transpose-rakedzior
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: transpose
Source: https://github.com/rakedzior/rootine/tree/main/agent/skills/transpose
Command: npx skills add https://github.com/rakedzior/rootine --skill transpose-rakedzior

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Moving a product from desktop to mobile, TV, kiosk, or voice is not a layout problem — shrinking a desktop design produces broken experiences. This Skill forces a systematic rethinking of interaction models, content priorities, and user context for each target platform instead of relying on responsive reflow. ## Core Features & Use Cases - Context Analysis Framework: Systematically compares input methods, attention models, screen real estate, connectivity, environment, and session length between source and target platforms. - Platform Convention Guidance: Provides specific UX conventions for iOS, Android, web, TV, kiosk, embedded widgets, and voice interfaces. - Priority Mapping & Cross-Device Continuity: Documents what content is primary, secondary, or removed per context, and designs handoff patterns (QR codes, magic links, cloud sync) for users switching devices mid-task. - Use Case: When a stakeholder says "just make the dashboard work on mobile," use this Skill to produce a context analysis matrix and priority map showing which features belong on mobile, which should be removed, and how the mobile experience should be reconceived. ## Quick Start Ask the assistant to transpose your desktop dashboard experience for mobile and TV, producing a context analysis matrix and per-platform priority mapping.

Frequently Asked Questions about transpose

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

FAQPage Schema
How do I adapt a desktop app design for mobile?

Adapting desktop to mobile requires rethinking the interaction model, not just reflowing layout. Analyze input method (touch vs mouse), attention model (fragmented vs focused), and session length, then remap content priorities so only the primary action and essential information appear first.

What is the difference between responsive design and cross-platform UX?

Responsive design is a layout concern handled with CSS breakpoints. Cross-platform UX (transposition) rethinks interaction models, information priority, and user context per platform — for example, sidebar navigation on desktop may become bottom tabs on mobile or hub-and-spoke on TV.

How do I design a user interface for TV or 10-foot experiences?

TV interfaces require D-pad navigation where everything is reachable with directional keys, unmistakable focus states, overscan safe zones, minimal text input, and large high-contrast typography for lean-back viewing. Browsing categories works better than search-first patterns.

How do I handle users switching devices mid-task?

Design explicit handoff patterns: QR codes to continue on phone, magic links with deep links to exact state, or transparent cloud sync. Preserve drafts, cart contents, and playback position, and send continuity notifications to the device the user is likely using now.

When should a feature be removed on a specific platform?

Remove features when the context does not serve them — kiosks should expose only the single task, voice interfaces should avoid features needing persistent visual feedback, and mobile should defer complex multi-step workflows. Document removals explicitly in a per-context priority matrix.