transpose

Rethinks UX experiences for different platforms, devices, and interaction contexts.

Updated Aug 26, 2026
One-click install
npx skills add https://github.com/danieliudi/trackforge-os --skill transpose-danieliudi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: transpose
Source: https://github.com/danieliudi/trackforge-os/tree/main/.cursor/skills/transpose
Command: npx skills add https://github.com/danieliudi/trackforge-os --skill transpose-danieliudi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often treat cross-platform design as a layout problem, shrinking desktop interfaces to fit mobile screens. This Skill reframes platform adaptation as a UX problem, forcing a systematic rethink of interaction models, content priorities, and user context for each target platform. ## Core Features & Use Cases - Context Analysis Framework: Systematically evaluates input method, attention model, screen real estate, connectivity, environment, and session length for every source-to-target transposition. - Platform Convention Guidance: Provides specific UX conventions for iOS, Android, web, TV, kiosk, embedded widgets, and voice interfaces, including navigation patterns, input constraints, and native behaviors. - Cross-Device Continuity: Designs state preservation, handoff patterns (QR codes, magic links, cloud sync), and session continuity for users switching devices mid-task. - Use Case: When asked to "make the dashboard work on mobile," use this Skill to produce a context analysis matrix, a priority map showing what is primary versus removed on mobile, and platform-specific adaptation specs instead of a responsive reflow. ## Quick Start Ask the assistant to transpose your desktop checkout flow to mobile and TV, producing a context analysis and priority mapping for each platform.

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 touch input constraints, fragmented attention, and short sessions, 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, asking what the experience would look like if designed for that context first.

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

TV interfaces require D-pad navigation with unmistakable focus states, overscan safe zones, minimal text input, large high-contrast typography, and lean-back browsing patterns. Category browsing works better than search-first flows because remote text entry is painful.

How do I keep user state when switching between devices?

Cross-device continuity uses state preservation for drafts, carts, and playback position, plus handoff mechanisms like QR codes, magic links, and cloud sync. Notifications should target the device the user is likely using now, not the one they just left.

When should a feature be removed instead of adapted for a platform?

Remove a feature when it does not serve users in that context, such as complex multi-step workflows on kiosks or hover-dependent interactions on touch devices. The priority mapping step explicitly documents what gets cut per context and why.