transpose

Name: transpose
Author: ghaida

516installs8forks

How to install transpose?

ghaida/intent/transpose

$npx -y skills add ghaida/intent --skill transpose

Installs into the current project.

Summary

Rethinks experiences for different platforms and contexts — not just resizing, but reconceiving. Part of the Intent design strategy system. When an experience moves from desktop to mobile, web to TV, consumer app to kiosk, or visual interface to voice, the interaction model, info

Files · 1

View on GitHub

SKILL.md

1	# Transpose — Adapt Across Contexts
2
3	## Overview
4
5	Responsive design is a layout concern. Transposition is a UX concern.
6
7	When an experience moves from desktop to mobile, from web to TV, from consumer app to kiosk, from visual interface to voice — the interaction model, information priority, and user context all change. A dashboard that works beautifully on a 27-inch monitor doesn't become a mobile experience by reflowing into a single column. A checkout flow designed for keyboard and mouse doesn't become a TV experience by adding focus states.
8
9	Transposition means rethinking the experience for each context, not shrinking it to fit. It asks: what would this experience look like if it were designed for this context first? What would we add? What would we never have included? What interaction patterns are native to this platform, and which are we forcing from somewhere else?
10
11	When to activate this skill: Moving a product to a new platform, planning multi-device strategy, auditing cross-platform UX, designing for non-standard contexts (TV, kiosk, voice, embedded), or anytime someone says "just make it responsive" and the problem is bigger than layout.
12
13	---
14
15	## Skill family
16
17	Transpose works alongside the full Intent skill system:
18
19	- `/journey`: Your flows need to work across the contexts transpose identifies. A checkout flow on desktop is not the same journey on mobile or voice — journey designs the sequence, transpose ensures it fits the context.
20	- `/organize`: Navigation structure may fundamentally change per context. Sidebar navigation on desktop might become bottom tabs on mobile, a hub-and-spoke on TV, or a flat menu on a kiosk. Organize provides the IA; transpose adapts it.
21	- `/include`: Cross-context design IS inclusive design. Designing for the constraints of a small screen, a noisy environment, one-handed use, or a 10-foot viewing distance is designing for real human situations. Include ensures accessibility; transpose ensures contextual fit.
22	- `/fortify`: Different contexts have different failure modes. Mobile loses connectivity. TV remotes run out of batteries. Kiosks get touched by greasy fingers. Fortify maps the failure modes; transpose maps the contexts where they occur.
23	- `/blueprint`: System architecture must support multi-context delivery. APIs need to serve different data shapes. State sync needs infrastructure. Blueprint maps the system; transpose defines what each context needs from it.
24	- `/philosopher`: A cross-cutting cognitive mode for sitting with transposition problems before jumping to solutions. Invoke when: you're tempted to copy-paste interaction patterns across platforms, something feels forced, or you need the question: "What if this experience was born on mobile? What would we never have added?"
25
26	---
27
28	## Core capabilities
29
30	### 1. Context analysis framework
31
32	For every source-to-target transposition, systematically analyze what changes. This is not a checklist to glance at — it's a forcing function that makes you confront the real differences between contexts.
33
34	Input method:
35	- Desktop: mouse + keyboard, precise targeting, hover states, right-click, keyboard shortcuts, drag-and-drop
36	- Mobile: touch, imprecise targeting (minimum 44px), gestures (swipe, pinch, long-press), no hover, virtual keyboard covers half the screen
37	- TV: D-pad remote, focus-based navigation, no direct pointing, limited text input, voice remote on some devices
38	- Voice: no pointing, no visual feedback loop, conversational turn-taking, confirmation through re-prompting
39	- Kiosk: touch-only (no hover, no keyboard unless on-screen), large targets, often gloved or wet hands
40	- Embedded/widget: constrained input matching host app, possibly no dedicated input at all
41
42	Attention model:
43	- Desktop: focused, multi-window, long sessions, user is "at work" (even for personal tasks)
44	- Mobile: fragmented, interruption-prone, multitasking, micro-sessions interspersed with life
45	- TV: lean-back, passive, shared screen, low cognitive effort tolerance
46	- Kiosk: goal-directed, time-pressured, public environment, zero learning curve expected
47	- Embedded: ambient, secondary to primary task, glanceable
48
49	*Screen real estate:

People who liked this also viewed

6 picks

Type

transpose

516installs8forks

View on GitHub

How to install transpose?

ghaida/intent/transpose

$npx -y skills add ghaida/intent --skill transpose

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Transpose — Adapt Across Contexts
2
3	## Overview
4
5	Responsive design is a layout concern. Transposition is a UX concern.
6
7	When an experience moves from desktop to mobile, from web to TV, from consumer app to kiosk, from visual interface to voice — the interaction model, information priority, and user context all change. A dashboard that works beautifully on a 27-inch monitor doesn't become a mobile experience by reflowing into a single column. A checkout flow designed for keyboard and mouse doesn't become a TV experience by adding focus states.
8
9	Transposition means rethinking the experience for each context, not shrinking it to fit. It asks: what would this experience look like if it were designed for this context first? What would we add? What would we never have included? What interaction patterns are native to this platform, and which are we forcing from somewhere else?
10
11	When to activate this skill: Moving a product to a new platform, planning multi-device strategy, auditing cross-platform UX, designing for non-standard contexts (TV, kiosk, voice, embedded), or anytime someone says "just make it responsive" and the problem is bigger than layout.
12
13	---
14
15	## Skill family
16
17	Transpose works alongside the full Intent skill system:
18
19	- `/journey`: Your flows need to work across the contexts transpose identifies. A checkout flow on desktop is not the same journey on mobile or voice — journey designs the sequence, transpose ensures it fits the context.
20	- `/organize`: Navigation structure may fundamentally change per context. Sidebar navigation on desktop might become bottom tabs on mobile, a hub-and-spoke on TV, or a flat menu on a kiosk. Organize provides the IA; transpose adapts it.
21	- `/include`: Cross-context design IS inclusive design. Designing for the constraints of a small screen, a noisy environment, one-handed use, or a 10-foot viewing distance is designing for real human situations. Include ensures accessibility; transpose ensures contextual fit.
22	- `/fortify`: Different contexts have different failure modes. Mobile loses connectivity. TV remotes run out of batteries. Kiosks get touched by greasy fingers. Fortify maps the failure modes; transpose maps the contexts where they occur.
23	- `/blueprint`: System architecture must support multi-context delivery. APIs need to serve different data shapes. State sync needs infrastructure. Blueprint maps the system; transpose defines what each context needs from it.
24	- `/philosopher`: A cross-cutting cognitive mode for sitting with transposition problems before jumping to solutions. Invoke when: you're tempted to copy-paste interaction patterns across platforms, something feels forced, or you need the question: "What if this experience was born on mobile? What would we never have added?"
25
26	---
27
28	## Core capabilities
29
30	### 1. Context analysis framework
31
32	For every source-to-target transposition, systematically analyze what changes. This is not a checklist to glance at — it's a forcing function that makes you confront the real differences between contexts.
33
34	Input method:
35	- Desktop: mouse + keyboard, precise targeting, hover states, right-click, keyboard shortcuts, drag-and-drop
36	- Mobile: touch, imprecise targeting (minimum 44px), gestures (swipe, pinch, long-press), no hover, virtual keyboard covers half the screen
37	- TV: D-pad remote, focus-based navigation, no direct pointing, limited text input, voice remote on some devices
38	- Voice: no pointing, no visual feedback loop, conversational turn-taking, confirmation through re-prompting
39	- Kiosk: touch-only (no hover, no keyboard unless on-screen), large targets, often gloved or wet hands
40	- Embedded/widget: constrained input matching host app, possibly no dedicated input at all
41
42	Attention model:
43	- Desktop: focused, multi-window, long sessions, user is "at work" (even for personal tasks)
44	- Mobile: fragmented, interruption-prone, multitasking, micro-sessions interspersed with life
45	- TV: lean-back, passive, shared screen, low cognitive effort tolerance
46	- Kiosk: goal-directed, time-pressured, public environment, zero learning curve expected
47	- Embedded: ambient, secondary to primary task, glanceable
48
49	*Screen real estate:

People who liked this also viewed

6 picks

Type