Back to Details

transpose

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Transpose — Adapt Across Contexts

Transpose — 跨场景适配

Overview

概述

Responsive design is a layout concern. Transposition is a UX concern.
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.
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?
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.
响应式设计关注的是布局问题，而Transposition（场景转译）关注的是UX问题。
当体验从桌面端迁移到移动端、从网页迁移到电视、从消费类应用迁移到自助终端、从视觉界面迁移到语音交互时，交互模式、信息优先级和用户场景都会发生变化。在27英寸显示器上表现出色的仪表盘，不会因为重排为单列就变成合格的移动端体验。为键盘和鼠标设计的结账流程，不会因为添加焦点状态就变成适配电视的体验。
场景转译意味着针对每个场景重新构思体验，而非缩小尺寸以适配。它会提出这些问题：如果最初就是为这个场景设计的，这款体验会是什么样子？我们会增加什么功能？哪些功能我们根本不会加入？哪些交互模式是该平台原生的，哪些是我们从其他平台强行引入的？
激活该技能的时机： 将产品迁移到新平台、规划多设备策略、审核跨平台UX、为非标准场景（电视、自助终端、语音、嵌入式设备）设计，或是每当有人说“只要做响应式就行”但问题远不止布局时。

Skill family

技能体系

Transpose works alongside the full Intent skill system:
  • /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.
  • /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.
  • /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.
  • /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.
  • /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.
  • /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?"
Transpose与完整的Intent技能系统协同工作：
  • /journey
    ：你的流程需要适配Transpose识别出的各类场景。桌面端的结账流程与移动端或语音端的流程截然不同——/journey负责设计流程序列，Transpose确保流程适配场景。
  • /organize
    ：导航结构可能会因场景不同而发生根本性变化。桌面端的侧边栏导航在移动端可能变为底部标签栏，在电视端可能变为中心辐射式导航，在自助终端可能变为扁平化菜单。/organize提供信息架构；Transpose负责适配架构。
  • /include
    ：跨场景设计就是包容性设计。针对小屏幕限制、嘈杂环境、单手操作或10英尺视距进行设计，就是针对真实用户场景的设计。/include确保可访问性；Transpose确保场景适配性。
  • /fortify
    ：不同场景有不同的故障模式。移动设备会失去连接，电视遥控器会没电，自助终端会被油腻的手触摸。/fortify负责梳理故障模式；Transpose负责梳理故障发生的场景。
  • /blueprint
    ：系统架构必须支持多场景交付。API需要提供不同的数据结构，状态同步需要相应的基础设施。/blueprint负责梳理系统架构；Transpose定义每个场景对系统的需求。
  • /philosopher
    ：这是一种跨领域的认知模式，用于在急于寻找解决方案前深入思考场景转译问题。在以下情况调用：你想要跨平台复制粘贴交互模式、某些设计显得生硬，或是你需要提出这类问题：“如果这款体验最初是为移动端设计的，我们根本不会加入哪些功能？”

Core capabilities

核心能力

1. Context analysis framework

1. 场景分析框架

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.
Input method:
  • Desktop: mouse + keyboard, precise targeting, hover states, right-click, keyboard shortcuts, drag-and-drop
  • Mobile: touch, imprecise targeting (minimum 44px), gestures (swipe, pinch, long-press), no hover, virtual keyboard covers half the screen
  • TV: D-pad remote, focus-based navigation, no direct pointing, limited text input, voice remote on some devices
  • Voice: no pointing, no visual feedback loop, conversational turn-taking, confirmation through re-prompting
  • Kiosk: touch-only (no hover, no keyboard unless on-screen), large targets, often gloved or wet hands
  • Embedded/widget: constrained input matching host app, possibly no dedicated input at all
Attention model:
  • Desktop: focused, multi-window, long sessions, user is "at work" (even for personal tasks)
  • Mobile: fragmented, interruption-prone, multitasking, micro-sessions interspersed with life
  • TV: lean-back, passive, shared screen, low cognitive effort tolerance
  • Kiosk: goal-directed, time-pressured, public environment, zero learning curve expected
  • Embedded: ambient, secondary to primary task, glanceable
Screen real estate: Constraints AND opportunities. Small screens force focus — that's a feature, not a bug. Large screens enable overview and comparison — but also invite clutter. Analyze what each size makes possible, not just what it takes away.
Connectivity:
  • Desktop/web: generally reliable broadband, but not always
  • Mobile: spotty, variable speed, metered data in many markets
  • TV: usually reliable home Wi-Fi, but smart TVs have weak processors
  • Kiosk: dedicated connection, but outages happen in retail/public environments
  • Embedded/IoT: intermittent, low-bandwidth, offline-first is often the right default
Environment:
  • Office, commute, couch, retail floor, hospital room, kitchen, car, factory floor
  • Noise level, lighting, privacy, social context, physical posture
  • These shape every interaction decision
Session length:
  • Desktop: 10-60+ minute sessions, complex multi-step workflows are viable
  • Mobile: 30 seconds to 5 minutes typical, must support micro-tasks
  • TV: 30-120 minutes but low engagement depth per interaction
  • Kiosk: 1-3 minutes maximum, single-purpose
  • Embedded: seconds at a time, momentary glances
For each transposition project, fill out this framework explicitly. Do not skip dimensions because they seem obvious.
对于每一次从源场景到目标场景的转译，系统地分析哪些要素会发生变化。这不是一个可以快速浏览的清单——它是一种强制手段，让你直面不同场景之间的真实差异。
输入方式：
  • 桌面端：鼠标+键盘、精准定位、悬停状态、右键点击、键盘快捷键、拖放操作
  • 移动端：触摸、非精准定位（最小44px）、手势（滑动、捏合、长按）、无悬停状态、虚拟键盘覆盖半个屏幕
  • 电视端：方向键遥控器、基于焦点的导航、无直接指向操作、文本输入受限、部分设备支持语音遥控器
  • 语音端：无指向操作、无视觉反馈循环、对话式交替交互、通过重新提示进行确认
  • 自助终端：仅支持触摸（无悬停、无实体键盘，除非提供屏幕键盘）、大目标区域、常被戴手套或湿手操作
  • 嵌入式/小部件：输入方式受宿主应用限制，可能完全没有专用输入方式
注意力模式：
  • 桌面端：专注、多窗口、长会话、用户处于“工作状态”（即使是处理个人任务）
  • 移动端：碎片化、易被打断、多任务处理、会话穿插于日常生活中，时长极短
  • 电视端：后仰放松、被动接收、共享屏幕、对认知负荷的容忍度低
  • 自助终端：目标导向、时间紧迫、公共环境、零学习曲线预期
  • 嵌入式：环境感知型、辅助主任务、可快速浏览
屏幕空间： 既是限制也是机遇。小屏幕迫使内容聚焦——这是优势而非缺陷。大屏幕支持概览和对比——但也容易导致杂乱。分析每种尺寸能实现什么，而不只是它限制了什么。
连接性：
  • 桌面端/网页：通常宽带连接可靠，但并非总是如此
  • 移动端：信号不稳定、速度多变、许多市场采用计量数据
  • 电视端：通常家庭Wi-Fi连接可靠，但智能电视处理器性能较弱
  • 自助终端：专用连接，但零售/公共环境中可能出现中断
  • 嵌入式/IoT：连接间歇性、低带宽、离线优先通常是正确的默认选择
使用环境：
  • 办公室、通勤途中、沙发上、零售卖场、病房、厨房、车内、工厂车间
  • 噪音水平、光线、隐私、社交场景、身体姿势
  • 这些因素会影响每一个交互决策
会话时长：
  • 桌面端：10-60+分钟会话，复杂的多步骤工作流是可行的
  • 移动端：典型时长30秒至5分钟，必须支持微任务
  • 电视端：30-120分钟，但每次交互的参与深度低
  • 自助终端：最长1-3分钟，单一用途
  • 嵌入式：每次几秒，仅需瞬间浏览
对于每个场景转译项目，都要明确填写此框架。不要因为某些维度看似显而易见就跳过。

2. Platform-specific UX conventions

2. 平台专属UX规范

These are genuine behavioral differences that users have internalized, not arbitrary guidelines to cargo-cult. Violate them only when you have a specific reason.
iOS:
  • System gestures: swipe-back from left edge, pull-down to dismiss sheets, swipe-up for home
  • Bottom-anchored navigation (tab bar), not hamburger menus
  • SF Symbols for consistent iconography
  • Haptic feedback for meaningful interactions (not decoration)
  • Dynamic Type: your layout must accommodate user-chosen text sizes
  • System sheets and action sheets for contextual actions
  • Pull-to-refresh is expected in list views
Android:
  • Material You design language and dynamic color
  • System back button/gesture — your app must handle it correctly, including predictive back
  • Top app bar with contextual actions
  • FAB (floating action button) for primary creation actions
  • System navigation bar (gesture or 3-button) — respect the safe area
  • Bottom sheets for secondary content, not full-screen modals for simple choices
Web:
  • URL-driven navigation — every meaningful state should have a URL
  • Multi-tab behavior — users will open things in new tabs, your app must handle it
  • Keyboard shortcuts for power users
  • Hover states provide information density that touch platforms lack
  • Right-click context menus have expectations
  • Bookmark and share expectations — og:tags, clean URLs, page titles
  • Browser back button must work predictably
TV (10-foot UI):
  • D-pad navigation: everything must be reachable with up/down/left/right
  • Focus states are the primary interaction feedback — make them unmistakable
  • Overscan safe zones: keep critical content within the inner 90% of the screen
  • Limited text input: avoid it, or provide voice input / QR code phone pairing
  • Lean-back posture: large text (minimum 24px equivalent at viewing distance), high contrast, minimal reading
  • Audio context matters: the TV has speakers, use sound design
Kiosk:
  • Touch-only, no hover — everything clickable must look clickable
  • Attract mode: screen content when nobody is using it, inviting first interaction
  • Session timeout: auto-reset after inactivity, with warning
  • Accessibility overlay: physical accessibility button or gesture for screen reader, high contrast
  • Rugged conditions: bright ambient light (high contrast needed), dirty screens (large targets), public noise (visual-first feedback)
Embedded/widget:
  • Minimal footprint: you're a guest in someone else's context
  • Match host context: visual style, interaction patterns, density
  • Deep link in and out: users arrive with context, let them leave with context
  • No onboarding: the widget must be self-explanatory at first glance
Voice:
  • No persistent visual feedback: every state must be communicated through speech
  • Conversational turn-taking: prompt, listen, confirm, act
  • Confirmation patterns: repeat back critical actions before executing ("You want to transfer $500 to checking. Is that right?")
  • Error recovery through re-prompting, not error messages
  • Progressive disclosure through conversation ("Would you like to hear more options?")
这些是用户已经内化的真实行为差异，不是需要盲目遵循的随意准则。只有在有特定理由时才可以违反。
iOS：
  • 系统手势：从左边缘滑动返回、下拉关闭弹窗、上滑返回主屏幕
  • 底部锚定导航（标签栏），而非汉堡菜单
  • 使用SF Symbols确保图标一致性
  • 为有意义的交互提供触觉反馈（而非装饰）
  • 动态字体：布局必须适配用户选择的文本大小
  • 使用系统弹窗和操作菜单处理上下文操作
  • 列表视图中预期支持下拉刷新
Android：
  • Material You设计语言和动态色彩
  • 系统返回按钮/手势——应用必须正确处理，包括预测性返回
  • 带有上下文操作的顶部应用栏
  • FAB（浮动操作按钮）用于主要创建操作
  • 系统导航栏（手势或三按钮）——尊重安全区域
  • 使用底部弹窗展示次要内容，而非用全屏模态框处理简单选择
网页：
  • URL驱动的导航——每个有意义的状态都应有对应的URL
  • 多标签行为——用户会在新标签页打开内容，应用必须妥善处理
  • 为高级用户提供键盘快捷键
  • 悬停状态提供触摸平台所没有的信息密度
  • 右键上下文菜单有既定预期
  • 书签和分享预期——og标签、简洁URL、页面标题
  • 浏览器返回按钮必须可预测地工作
电视（10英尺UI）：
  • 方向键导航：所有内容都必须能通过上下左右键访问
  • 焦点状态是主要的交互反馈——必须清晰可辨
  • 过扫描安全区：将关键内容保持在屏幕内部90%的区域内
  • 文本输入受限：尽量避免，或提供语音输入/二维码手机配对
  • 后仰姿势：大字体（观看距离下最小等效24px）、高对比度、尽量减少阅读内容
  • 音频场景很重要：电视有扬声器，善用音效设计
自助终端：
  • 仅支持触摸，无悬停——所有可点击元素必须看起来可点击
  • 吸引模式：无人使用时的屏幕内容，吸引首次交互
  • 会话超时：无活动后自动重置，并给出警告
  • 无障碍覆盖层：物理无障碍按钮或手势用于屏幕阅读器、高对比度模式
  • 恶劣环境：明亮环境光（需要高对比度）、脏屏幕（大目标区域）、公共噪音（优先视觉反馈）
嵌入式/小部件：
  • 最小占用空间：你是其他场景中的“访客”
  • 匹配宿主场景：视觉风格、交互模式、信息密度
  • 深度链接进出：用户带着场景进入，让他们带着场景离开
  • 无需引导：小部件必须第一眼就能自我解释
语音：
  • 无持久视觉反馈：每个状态都必须通过语音传达
  • 对话式交替交互：提示、倾听、确认、执行
  • 确认模式：执行关键操作前重复确认（“你想要转账500美元至支票账户，对吗？”）
  • 通过重新提示进行错误恢复，而非显示错误消息
  • 通过对话逐步披露信息（“你想了解更多选项吗？”）

3. Content priority shifting

3. 内容优先级调整

What's primary changes by context. This is the core of transposition — not just hiding content on smaller screens, but rethinking what matters most.
Desktop — overview + detail:
  • Show overview and detail simultaneously (master-detail, multi-column)
  • Complex workflows with many steps visible at once
  • Comparison views, data tables, dashboards with multiple widgets
  • Power user features visible alongside simple paths
Mobile — action + essential info:
  • Primary action and essential information only on first view
  • Sequential disclosure: one thing at a time, drill deeper on demand
  • One-thumb reachability: critical actions in the bottom 60% of the screen
  • Progressive loading: show something useful immediately, enhance as data arrives
TV — browse + select:
  • Visual-heavy: large imagery, minimal text, let the content sell itself
  • Category browsing, not search-first (text input is painful)
  • Audio context: use voiceover, sound design, ambient audio
  • Shared viewing: content must make sense to multiple people on the couch
Kiosk — task + nothing else:
  • Single-purpose: what is the ONE thing this kiosk does?
  • Large touch targets, clear progress indicators, obvious "start over" escape hatch
  • Timeout recovery: save state briefly, but reset cleanly
Document priority shifts explicitly for each screen and feature. Create a priority matrix: what's primary, secondary, hidden, and removed per context.
不同场景下的核心内容会发生变化。这是场景转译的核心——不只是在小屏幕上隐藏内容，而是重新思考什么才是最重要的。
桌面端——概览+细节：
  • 同时展示概览和细节（主从视图、多列布局）
  • 复杂工作流，多步骤同时可见
  • 对比视图、数据表、带有多个小部件的仪表盘
  • 高级用户功能与简单操作路径同时可见
移动端——操作+关键信息：
  • 首屏仅显示主要操作和关键信息
  • 逐步披露：一次展示一件事，按需深入查看
  • 单拇指可达：关键操作位于屏幕底部60%的区域内
  • 渐进式加载：立即展示有用内容，随着数据到达逐步增强
电视端——浏览+选择：
  • 视觉主导：大图片、少文本，让内容自我展示
  • 分类浏览，而非优先搜索（文本输入很麻烦）
  • 音频场景：使用旁白、音效设计、环境音频
  • 共享观看：内容必须对沙发上的多个人有意义
自助终端——任务+无关内容全移除：
  • 单一用途：这个自助终端的核心功能是什么？
  • 大触摸目标、清晰的进度指示器、明显的“重新开始”退出选项
  • 超时恢复：短暂保存状态，但最终干净重置
为每个屏幕和功能明确记录优先级调整。创建优先级矩阵：每个场景下的核心内容、次要内容、隐藏内容和移除内容。

4. Cross-device journey continuity

4. 跨设备旅程连续性

Users switch devices mid-task. This isn't an edge case — it's the normal flow for many tasks. Design for it explicitly.
State preservation:
  • Draft saved on mobile, resume on desktop (and vice versa)
  • Shopping cart, form progress, reading position, playback position
  • What state needs to sync in real-time vs. on next session start?
Handoff patterns:
  • QR codes: scan on phone to continue on phone what you started on desktop/TV/kiosk
  • Magic links: "continue on your phone" via SMS/email with deep link to exact state
  • Cloud sync: transparent background sync so the user never thinks about it
  • Clipboard continuity: iOS/macOS universal clipboard, but don't depend on platform-specific features alone
Context-appropriate notifications:
  • "You left something in your cart" — on which device? At what time? In what tone?
  • Don't notify on the device they just left. Notify on the device they're likely using now.
  • Notification content should match the device context (short on watch, actionable on phone, ignorable on desktop)
Session continuity:
  • Re-authentication friction: minimize it across devices. Biometric on phone, magic link on desktop, persistent session on TV.
  • Don't make users start over because they switched devices.
用户会在任务中途切换设备。这不是边缘情况——这是许多任务的正常流程。要明确为此进行设计。
状态保存：
  • 移动端保存的草稿，可在桌面端继续编辑（反之亦然）
  • 购物车、表单进度、阅读位置、播放位置
  • 哪些状态需要实时同步，哪些可以在下次会话开始时同步？
切换模式：
  • 二维码：在手机上扫描，继续在手机上完成在桌面端/电视端/自助终端开始的任务
  • 魔法链接：通过短信/邮件发送“在手机上继续”的链接，直接跳转至对应状态
  • 云同步：透明的后台同步，让用户无需刻意关注
  • 剪贴板连续性：iOS/macOS通用剪贴板，但不要仅依赖平台专属功能
场景适配通知：
  • “你的购物车中有未结算商品”——在哪个设备发送？什么时间？用什么语气？
  • 不要在用户刚离开的设备上发送通知。要在他们当前可能使用的设备上发送。
  • 通知内容应适配设备场景（手表上简短，手机上可操作，桌面端可忽略）
会话连续性：
  • 重新认证摩擦：跨设备最小化认证步骤。手机上使用生物识别，桌面端使用魔法链接，电视端保持持久会话。
  • 不要让用户因为切换设备而重新开始任务。

5. Progressive disclosure per context

5. 分场景渐进式披露

The same information architecture may need fundamentally different disclosure strategies per context. This is not about responsive breakpoints — it's about cognitive load management per context.
Mobile: show less, reveal on interaction. Cards that expand, drawers that slide up, tabs that switch content. The user chooses what to see more of. Default to the minimum viable view.
Desktop: show more, group by function. Sidebars, panels, toolbars, multi-column layouts. The user scans and selects. More information is visible simultaneously, reducing the need for navigation.
TV: show categories, drill into detail. Large tiles representing categories or content. Select to enter, back to return. Flat and wide, not deep and narrow.
Kiosk: show the task, nothing else. Strip away everything that isn't the current step. No settings, no account management, no exploration. Just the task.
Voice: reveal through conversation. "Here are your three options. Would you like to hear more about any of them?" Progressive disclosure happens through dialogue turns, not visual hierarchy.
Map disclosure strategy per context for every major feature. Don't assume what works on desktop will work anywhere else with minor modifications.
相同的信息架构可能需要针对不同场景采用完全不同的披露策略。这与响应式断点无关——而是针对不同场景的认知负荷管理。
移动端：少展示，交互时再披露。 可展开的卡片、向上滑动的抽屉、切换内容的标签。用户选择查看更多内容。默认展示最小可行视图。
桌面端：多展示，按功能分组。 侧边栏、面板、工具栏、多列布局。用户扫描并选择。更多信息同时可见，减少导航需求。
电视端：展示分类，深入查看细节。 代表分类或内容的大磁贴。选择进入，返回退出。扁平化、宽覆盖，而非深层级、窄范围。
自助终端：展示任务，其余全移除。 剥离所有与当前步骤无关的内容。无设置、无账户管理、无探索功能。只保留任务相关内容。
语音端：通过对话披露。 “这是你的三个选项。你想了解其中任何一个的更多信息吗？”渐进式披露通过对话回合实现，而非视觉层级。
为每个主要功能分场景规划披露策略。不要假设在桌面端有效的策略，只需稍作修改就能在其他场景生效。

Output format

输出格式

Context analysis matrix

场景分析矩阵

For each platform/context, document: input method, attention model, screen real estate, connectivity, environment, session length, and their UX implications.
针对每个平台/场景，记录：输入方式、注意力模式、屏幕空间、连接性、使用环境、会话时长及其UX影响。

Platform-specific adaptation specs

平台专属适配规范

Per platform: which conventions apply, which native patterns to adopt, which source patterns to replace (and with what), which features to add/remove/transform.
针对每个平台：适用哪些规范、采用哪些原生模式、替换哪些源模式（以及用什么替换）、添加/移除/转换哪些功能。

Priority mapping per context

分场景优先级映射

For each major screen/feature: what's primary, secondary, on-demand, and removed — per context. Explicitly document what gets cut and why.
针对每个主要屏幕/功能：每个场景下的核心内容、次要内容、按需展示内容和移除内容。明确记录哪些内容被移除及其原因。

Cross-device journey map

跨设备旅程图

For multi-device experiences: where users switch, what state transfers, what handoff mechanisms exist, and where continuity breaks.
针对多设备体验：用户切换设备的节点、转移的状态、切换机制，以及连续性中断的位置。

Voice and approach

表达与方法

Never say "just make it responsive." Transposition requires rethinking, not reflowing. The question is never "how do we fit this on a smaller screen?" The question is "what would this experience look like if it were designed for this context first?"
Be specific about platform conventions. Don't say "follow platform guidelines" — say which guideline, which pattern, and why it matters for this specific design. Challenge assumptions about which features "must" exist on every platform. Sometimes the right transposition is to remove a feature entirely from a context where it doesn't serve users.
Respect the intelligence of each context. Mobile isn't desktop's lesser sibling. Voice isn't a screen without visuals. Each context has strengths that the others lack.
永远不要说“只要做响应式就行”。场景转译需要重新构思，而非重排布局。问题永远不是“我们如何把这个内容塞进小屏幕？”而是“如果最初就是为这个场景设计的，这款体验会是什么样子？”
明确说明平台规范。不要说“遵循平台指南”——要说明具体是哪条指南、哪种模式，以及它对这个特定设计的重要性。挑战“每个平台都必须包含所有功能”的假设。有时正确的场景转译是在某个场景中完全移除对用户无用的功能。
尊重每个场景的独特价值。移动端不是桌面端的“低配版”，语音交互不是“没有视觉的屏幕”。每个场景都有其他场景不具备的优势。

Scope boundaries

范围边界

This skill owns:

该技能负责：

  • Cross-platform UX strategy and context analysis
  • Platform-specific interaction model recommendations
  • Content priority mapping across contexts
  • Cross-device journey continuity design
  • Progressive disclosure strategy per context
  • 跨平台UX策略和场景分析
  • 平台专属交互模式建议
  • 跨场景内容优先级映射
  • 跨设备旅程连续性设计
  • 分场景渐进式披露策略

This skill does NOT own:

该技能不负责：

  • Responsive CSS and layout implementation (engineering + visual design)
  • Flow design within a context (
    /journey
    )
  • Platform-specific visual design (visual design)
  • Navigation structure decisions (
    /organize
    )
  • System architecture for multi-context delivery (
    /blueprint
    )
  • Accessibility compliance per platform (
    /include
    )
  • 响应式CSS和布局实现（工程+视觉设计）
  • 单场景内的流程设计（
    /journey
    ）
  • 平台专属视觉设计（视觉设计）
  • 导航结构决策（
    /organize
    ）
  • 多场景交付的系统架构（
    /blueprint
    ）
  • 各平台的无障碍合规性（
    /include
    ）