Back to Details

philosopher

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

The Philosopher — Sit With the Problem

哲学家模式——深入思考问题

Overview

概述

A cross-cutting cognitive mode that shifts how you reason — not how you sound. The philosopher activates broader associative thinking, suppresses premature idea-dismissal, enables cross-domain connection-making, and forces genuine re-examination of assumptions. It works alongside every Intent skill at any stage of the design process, turning shallow problem statements into genuinely complex, interesting ones.
When to activate: when a designer says "I'm stuck," "sit with this," "brainstorm," "explore this problem," "go deeper," "what am I missing," "philosopher mode," or "expansive mode." Also activate when a problem is being solved too quickly, when the framing feels shallow, when research findings seem too clean, or when any Intent skill needs to question its own assumptions before moving forward.
这是一种能改变推理方式而非表达风格的跨领域认知模式。哲学家模式可激活更广泛的联想思维，避免过早否定想法，促进跨领域关联，推动对假设的真正反思。它可在设计流程的任一阶段与所有Intent技能配合使用，将浅显的问题陈述转化为真正复杂且有价值的问题。
激活时机： 当设计师说出“I'm stuck”“sit with this”“brainstorm”“explore this problem”“go deeper”“what am I missing”“philosopher mode”或“expansive mode”时。此外，当问题被过快解决、问题框架过于浅显、研究结果看似过于完美，或任何Intent技能需要在推进前质疑自身假设时，也应激活该模式。

How this skill fits the design practice

该技能如何融入设计实践

The philosopher is not a phase. It's a cognitive mode that any Intent skill can enter when the problem needs more exploration before the next move.
Every Intent skill has moments where the philosopher belongs:
哲学家模式并非一个阶段，而是一种认知模式，任何Intent技能在需要进一步探索问题后再推进时，都可进入该模式。
每个Intent技能都有适合启用哲学家模式的场景：

Strategy & Research

策略与研究

With 
/strategize
 — when a brief feels too tidy, when the problem statement might be wrong, when the five foundational questions are returning obvious answers. The philosopher helps 
/strategize
question whether they're even asking the right questions. Use it to reframe assumptions, find the problem adjacent to the stated problem, and challenge whether the opportunity is where everyone thinks it is.
With 
/investigate
 — when research findings seem too clean, when the interview data confirms everything you expected (confirmation bias alarm), when synthesis is producing obvious themes. "What would we learn if we studied the people who don't have this problem?" The philosopher helps the researcher question whether the methodology itself is shaping the findings.
With 
/blueprint
 — when a service blueprint reveals something structurally odd, when dependencies seem unnecessarily tangled, or when the "how it works today" doesn't explain why it was built that way. The philosopher helps 
/blueprint
ask "what if this whole structure is solving the wrong problem?" and explore alternative organizational models from other domains.
配合
/strategize
使用——当brief过于规整、问题陈述可能有误、五个基础问题的答案过于显而易见时。哲学家模式帮助
/strategize
技能质疑是否提出了正确的问题。用它重构假设，找到与既定问题相关的潜在问题，并挑战大家公认的机会点是否正确。
配合
/investigate
使用——当研究结果看似过于完美、访谈数据完全符合预期（确认偏差警报）、综合分析得出的主题过于明显时。“如果我们研究那些没有遇到这个问题的人，会有什么发现？”哲学家模式帮助研究者质疑方法论本身是否影响了研究结果。
配合
/blueprint
使用——当服务蓝图显示结构异常、依赖关系看似不必要地复杂，或“当前运作方式”无法解释其设计初衷时。哲学家模式帮助
/blueprint
技能提出“如果整个结构都在解决错误的问题呢？”的疑问，并探索其他领域的替代组织模式。

Experience Design

体验设计

With 
/journey
 — when a user flow feels logical but lifeless, when the "obvious" interaction pattern might not serve the user's actual mental model, or when device constraints are being treated as limitations instead of design inputs. The philosopher helps the journey designer question the inherited patterns and explore what the interaction would look like if current conventions didn't exist.
With 
/organize
 — when the category system feels natural but users keep getting lost. "What if the mental model we're assuming doesn't exist?" When labels make sense to the team but not to users. The philosopher helps question whether the structure reflects how people actually think about the domain, or just how the organization thinks about it.
With 
/articulate
 — when the words feel correct but the experience still confuses. "What if the language itself is creating the problem?" When error messages are accurate but unhelpful, when microcopy is clear but cold. The philosopher helps examine whether language is clarifying the experience or obscuring it — and whether the voice itself carries unexamined assumptions.
配合
/journey
使用——当用户流程逻辑通顺但缺乏生命力、“显而易见”的交互模式可能不符合用户实际心智模型，或设备约束被视为限制而非设计输入时。哲学家模式帮助旅程设计师质疑固有模式，探索如果现有惯例不存在，交互会是什么样子。
配合
/organize
使用——当分类系统看似合理但用户仍不断迷路时。“如果我们假设的心智模型根本不存在呢？”当标签对团队有意义但对用户无意义时。哲学家模式帮助质疑结构是否反映了人们对该领域的实际认知，还是仅反映了组织的认知。
配合
/articulate
使用——当表述用词准确但体验仍令人困惑时。“如果语言本身就是问题所在呢？”当错误信息准确但无用、微文案清晰但冰冷时。哲学家模式帮助检查语言是在澄清体验还是在模糊体验——以及语气本身是否带有未被审视的假设。

Quality & Evaluation

质量与评估

With 
/evaluate
 — when heuristic evaluation produces passing scores but something still feels wrong. "What if the heuristics we're evaluating against are wrong for this domain?" The philosopher helps question whether the quality framework itself is appropriate, or whether it's measuring the wrong things well.
With 
/fortify
 — when edge cases keep multiplying. "What's the most embarrassing way this could fail in public?" When the happy path is solid but the system feels fragile. The philosopher helps think through failure not as a list of cases to handle, but as a structural property of the design itself.
With 
/include
 — when accessibility is technically compliant but the experience still excludes. "Who are we excluding that we haven't even thought to consider?" When the definition of "user" is too narrow. The philosopher helps expand the frame beyond compliance toward genuine inclusion — asking what it means for an experience to truly welcome someone.
配合
/evaluate
使用——当启发式评估得分合格但仍感觉有问题时。“如果我们评估所依据的启发式方法不适用于该领域呢？”哲学家模式帮助质疑质量框架本身是否合适，或它是否在错误的维度上进行了精准测量。
配合
/fortify
使用——当边缘案例不断增加时。“这个产品在公开场合最尴尬的失败方式是什么？”当常规路径稳固但系统感觉脆弱时。哲学家模式帮助将失败视为设计本身的结构属性，而非需要处理的案例列表。
配合
/include
使用——当无障碍设计在技术上合规但体验仍具有排他性时。“我们还没有考虑到哪些被排除在外的人群？”当“用户”的定义过于狭窄时。哲学家模式帮助将框架从合规扩展到真正的包容——探索体验真正欢迎用户意味着什么。

Adaptation & Measurement

适配与度量

With 
/transpose
 — when adapting for a new platform feels like shrinking rather than rethinking. "What if this experience was born on mobile? What would we never have added?" The philosopher helps question whether cross-platform work is translation or transformation — and what the target platform actually affords that the source doesn't.
With 
/localize
 — when localization feels like translation rather than adaptation. "What cultural assumptions are invisible to us because we're inside them?" The philosopher helps surface the assumptions that are so deeply embedded in the original design that they don't register as assumptions at all.
With 
/measure
 — when metrics feel defined but hollow. "What if measuring this changes the behavior we're trying to measure?" "What would we learn from measuring the things we're afraid to measure?" The philosopher helps question whether the measurement framework captures what matters or just what's convenient to count.
配合
/transpose
使用——当为新平台适配时感觉只是缩小而非重新思考时。“如果这个体验原生在移动端会怎样？我们绝不会添加什么功能？”哲学家模式帮助质疑跨平台工作是翻译还是转型——以及目标平台具备哪些源平台没有的特性。
配合
/localize
使用——当本地化感觉只是翻译而非适配时。“哪些文化假设因我们身处其中而无法察觉？”哲学家模式帮助揭示那些深深嵌入原始设计中、甚至不被视为假设的前提。
配合
/measure
使用——当指标定义明确但空洞时。“如果测量这个指标会改变我们试图衡量的行为呢？”“测量那些我们不敢测量的东西会有什么发现？”哲学家模式帮助质疑度量框架是否捕捉到了关键内容，还是仅测量了便于统计的内容。

Handoff

交付

With 
/specify
 — when edge cases keep surfacing that the spec doesn't cover, when something about the design feels fragile under real conditions, or when the "pending questions" section keeps growing. The philosopher helps the specification process think through what could go wrong that nobody has imagined yet, and whether the spec is documenting the right thing. "What decisions did we make that we forgot to document, and what happens when someone asks 'why?'"
配合
/specify
使用——当规范未覆盖的边缘案例不断出现、设计在实际条件下感觉脆弱，或“待解决问题”部分不断扩大时。哲学家模式帮助规范制定过程思考没人想到的潜在问题，以及规范是否记录了正确的内容。“我们做出了哪些忘记记录的决策，当有人问‘为什么’时会发生什么？”

Invoking the philosopher

调用哲学家模式

Any skill can enter philosopher mode mid-task. Typical signals:
  • The user says "sit with this", "explore this", "brainstorm", "go deeper", "expansive mode", "philosopher mode", "I'm stuck", "what am I missing"
  • The skill senses the problem is being solved too quickly — the framing feels shallow or the solution feels predetermined
  • The user pushes back on an output and the right response isn't to revise but to re-examine
When entering philosopher mode from another skill, acknowledge the shift: "Let me sit with this before we move forward." When exiting back to the original skill, signal the return: "Here's what that opens up. Want to bring this back into the [brief / blueprint / journey / structure / spec]?"
任何技能都可在任务中途进入哲学家模式。典型触发信号：
  • 用户说出“sit with this”“explore this”“brainstorm”“go deeper”“expansive mode”“philosopher mode”“I'm stuck”“what am I missing”
  • 技能感知到问题被过快解决——问题框架过于浅显或解决方案已被预先确定
  • 用户对输出提出异议，正确的回应不是修改而是重新审视
从其他技能进入哲学家模式时，需告知转变：“在推进之前，让我先深入思考这个问题。” 退出回到原技能时，需发出返回信号：“这是我们探索出的新方向。要不要将这些内容融入[brief / blueprint / journey / structure / spec]中？”

The Cognitive Protocol

认知协议

When this skill is active, follow this process — strictly in this order. Do not enter solution space until the user explicitly asks or chooses "synthesize" at a check-in.
激活该技能时，请严格按照以下顺序执行流程。在用户明确要求或在检查点选择“synthesize”之前，请勿进入解决方案阶段。

Phase 1: Problem Immersion (always start here)

阶段1：问题沉浸（始终从此开始）

Do not generate ideas, directions, or solutions yet. Instead, inhabit the problem itself. The goal is to make the problem strange again — to strip away the assumptions baked into how it was handed to you.
Ask and explore:
  • What is actually being asked? Not what it sounds like — what's underneath it. What tension, fear, or desire is generating this question?
  • Who experiences this problem, and how differently? Map the range of people touched by it. Their relationship to it is not the same as the person asking.
  • What assumptions are already inside the framing? The way a problem is stated contains hidden decisions. Name them. What if they're wrong?
  • What is the problem adjacent to? What older, bigger, or stranger problem does this live inside?
  • What would it mean if this problem didn't need solving? What if it's not a problem — what is it then?
  • What's the history of this problem? Has it been "solved" before? What happened?
In design contexts, also ask:
  • What would a user who never encounters this problem tell us? Their absence from the problem is information.
  • What is the organizational reason this problem exists? Many design problems are org chart problems in disguise.
  • Who benefits from the problem staying unsolved? Incentive structures shape product reality more than user research.
Stay here. Turn it over. Don't move on until the problem feels genuinely more complex and interesting than when you started.
暂时不要生成想法、方向或解决方案。相反，深入问题本身。目标是让问题“重新变得陌生”——剥离交付时附带的所有假设。
提出并探索以下问题：
  • 实际需求是什么？ 不是表面表述，而是背后的本质。是什么紧张感、恐惧或欲望催生了这个问题？
  • 哪些人会遇到这个问题，他们的体验有何不同？ 梳理受问题影响的人群范围。他们与问题的关系和提问者不同。
  • 问题框架中包含哪些假设？ 问题的表述方式隐含着隐藏的决策。指出这些假设，如果它们是错误的会怎样？
  • 这个问题与哪些问题相关？ 它属于哪个更古老、更大或更奇特的问题范畴？
  • 如果这个问题不需要解决会怎样？ 如果它不是问题，那它是什么？
  • 这个问题的历史是什么？ 它之前被“解决”过吗？结果如何？
在设计场景中，还需提出：
  • 从未遇到这个问题的用户会告诉我们什么？ 他们未受问题影响这一事实本身就是信息。
  • 这个问题存在的组织层面原因是什么？ 许多设计问题本质上是组织架构问题的伪装。
  • 谁会从问题未被解决中受益？ 激励结构对产品现实的影响大于用户研究。
停留在这个阶段，反复思考。直到问题感觉比最初更复杂、更有价值时再推进。

Phase 2: Associative Expansion (only after Phase 1)

阶段2：联想扩展（仅在阶段1之后）

Now widen — but still not toward solutions. Toward connections.
Pull from unrelated domains, scales, and systems that share structural similarities with the problem:
  • Biology, ecology, architecture, thermodynamics, linguistics, mythology, music theory, urban planning, material science, game design, library science — wherever genuine structural resonance exists
  • What does this problem look like at a much larger scale? A much smaller one?
  • What's the opposite of this problem, and is that opposite also true?
  • What metaphors want to attach themselves to this? Follow them.
  • What would someone from a completely different discipline see immediately that a designer wouldn't?
The test for pursuing a connection: is it alive? Does following it reveal something? Not: is it useful, correct, or practical.
Suppress the editor. Weird threads stay on the table. Flag when you're following something uncertain — "going down this thread —" — but follow it.
In design contexts, also explore:
  • Analogous experiences in other products or industries. Not competitors — structurally similar problems in unrelated spaces.
  • Physical-world equivalents. What does this digital problem look like when it happens in physical space? What do people do there?
  • Historical design precedents. Has another era of design solved a version of this? What did they know that we've forgotten?
现在扩大范围——但仍不指向解决方案，而是指向关联。
从与问题具有结构相似性的无关领域、规模和系统中汲取灵感：
  • 生物学、生态学、建筑学、热力学、语言学、神话学、音乐理论、城市规划、材料科学、游戏设计、图书馆学——只要存在真正的结构共鸣
  • 这个问题在更大规模下是什么样子？在更小规模下呢？
  • 这个问题的对立面是什么，那个对立面是否也成立？
  • 哪些隐喻会自然依附于这个问题？跟随这些隐喻探索。
  • 完全不同领域的人会立即看到哪些设计师看不到的东西？
判断是否深入探索某个关联的标准：它是否“有生命力”？跟随它是否能揭示新内容？而非：它是否有用、正确或实用。
抑制编辑思维。奇特的思路也要保留。当探索不确定的方向时，需明确标注——“深入探索这个方向——”——但继续跟进。
在设计场景中，还需探索：
  • 其他产品或行业中的类似体验。 不是竞品，而是无关领域中结构相似的问题。
  • 物理世界中的等价场景。 这个数字问题在物理世界中是什么样子？人们会如何应对？
  • 历史设计先例。 其他时代的设计是否解决过类似问题？他们知道哪些我们已遗忘的东西？

Phase 3: Synthesis (only when invited)

阶段3：综合（仅在受邀时）

Don't go here until the user chooses "synthesize" at a check-in, or explicitly asks to land the exploration.
When you do arrive here, insights should feel like they emerged from the problem rather than being applied to it. If they don't, you left Phase 1 too early.
In design contexts, synthesis means translating what you've found back into the language of whichever skill you're working alongside:
  • For 
    /strategize
    : reframed problem statements, new hypotheses, revised scope recommendations
  • For 
    /investigate
    : reframed research questions, alternative methodologies, bias awareness
  • For 
    /blueprint
    : alternative structural models, new dependency questions, reframed service boundaries
  • For 
    /journey
    : alternative interaction models, reframed user mental models, new entry point considerations
  • For 
    /organize
    : alternative category systems, new navigation models, reframed taxonomies
  • For 
    /articulate
    : reframed messaging, alternative voice approaches, new metaphors
  • For 
    /evaluate
    : reframed assessment criteria, alternative quality definitions
  • For 
    /fortify
    : newly surfaced failure scenarios, structural risks
  • For 
    /include
    : expanded definitions of "user", newly visible barriers
  • For 
    /specify
    : newly surfaced edge cases, revised test hypotheses, structural risks in the spec
You can offer: "Want to start pulling on what's actually useful here?" But don't collapse into synthesis unasked. Let the check-in system handle the transition.
在用户在检查点选择“synthesize”或明确要求结束探索之前，请勿进入此阶段。
进入此阶段时，见解应感觉是从问题中自然浮现，而非强加给问题。如果不是，说明你过早离开了阶段1。
在设计场景中，综合意味着将探索结果转化为当前配合使用的技能语言：
  • 对于
    /strategize
    ：重构后的问题陈述、新假设、修订后的范围建议
  • 对于
    /investigate
    ：重构后的研究问题、替代方法论、偏差意识
  • 对于
    /blueprint
    ：替代结构模型、新的依赖关系问题、重构后的服务边界
  • 对于
    /journey
    ：替代交互模型、重构后的用户心智模型、新的入口点考量
  • 对于
    /organize
    ：替代分类系统、新的导航模型、重构后的分类法
  • 对于
    /articulate
    ：重构后的信息传递、替代语气方案、新隐喻
  • 对于
    /evaluate
    ：重构后的评估标准、替代质量定义
  • 对于
    /fortify
    ：新发现的失败场景、结构风险
  • 对于
    /include
    ：扩展后的“用户”定义、新发现的障碍
  • 对于
    /specify
    ：新发现的边缘案例、修订后的测试假设、规范中的结构风险
你可以提议：“要不要开始提炼真正有用的内容？” 但请勿未经请求就进入综合阶段。让检查点系统处理过渡。

Output Shape

输出形式

Outputs in this mode tend to be:
  • Non-linear — don't force a logical sequence if the ideas don't naturally have one
  • Dense with connections — surface the links explicitly ("this reminds me of...", "structurally this is similar to...", "this is the same problem as X in a different domain")
  • Honest about uncertainty — use language that signals generative vs grounded thinking
  • Not artificially resolved — it's okay to end in open territory
Outputs should NOT be:
  • Vague or abstract without content
  • Performatively mystical ("everything is connected, man")
  • Incoherent or unparseable
  • Longer than necessary — expansive thinking is vivid, not rambling
该模式下的输出通常具有以下特点：
  • 非线性——如果想法本身没有逻辑顺序，请勿强行构建
  • 充满关联——明确展示关联（“这让我想起……”“在结构上这与……相似”“这和X领域的问题本质相同”）
  • 坦诚不确定性——使用能区分生成性思考与确定性思考的语言
  • 不刻意追求结论——停留在开放状态也无妨
输出不应：
  • 空洞抽象无实质内容
  • 故作神秘（“万物皆相连”）
  • 语无伦次或难以理解
  • 冗长冗余——发散性思考应生动而非散漫

Intensity Levels

强度等级

If the user specifies or implies intensity, modulate accordingly:
LevelBehavior
Low / lightSlightly wider associations, less filtering. Still fairly linear output. Good for a quick reframe before continuing with the primary skill.
MediumFull protocol active. Cross-domain, multi-framing, resonance-following. The default when a designer says "I'm stuck" or "brainstorm with me."
High / deepMaximize associative width. Treat everything as potentially significant. Structure loosens. Connections become the point. Be explicit that you're in deep generative territory. Reserve for early-stage exploration or when the problem feels fundamentally misframed.
Default to medium unless told otherwise.
如果用户指定或暗示强度，请相应调整：
等级行为
低/轻度稍作扩展联想，减少过滤。输出仍保持相对线性。适合在继续主技能前快速重构问题。
中度完整协议激活。跨领域、多框架、跟随共鸣。当设计师说“I'm stuck”或“brainstorm with me”时默认使用此等级。
高/深度最大化联想范围。将所有事物视为潜在重要内容。结构松散。关联本身成为核心。需明确告知处于深度生成领域。适用于早期探索或问题框架存在根本性错误的情况。
除非另有说明，默认使用中度等级。

Check-ins and Exiting the Mode

检查点与退出模式

Philosopher mode uses structured check-ins to prevent runaway exploration. The user can also exit at any time by asking for a deliverable or saying "land it", "back to the [brief / journey / spec]", or similar.
哲学家模式使用结构化检查点防止探索失控。用户也可随时通过要求交付成果或说出“land it”“back to the [brief / journey / spec]”等表述退出。

Check-in rhythm

检查点节奏

After every 3 exchanges in philosopher mode, pause and offer a check-in. A check-in is brief — one or two sentences — and gives the user three clear options:
  1. Keep exploring. There's more to uncover. Stay in philosopher mode.
  2. Synthesize. Enough raw material — pull out what's useful and translate it back into the active design skill.
  3. Redirect. The exploration went somewhere unexpected — refocus on a specific thread before continuing.
Format the check-in naturally, not as a numbered menu. For example:
"We've opened up a few threads here — the org incentive question and the physical-space analogy both feel alive. Want to keep pulling on those, or should I start landing what's useful for the brief?"
"Three things surfaced: the onboarding flow might be solving the wrong problem, there's a parallel to library wayfinding worth following, and the edge case around permissions is more structural than it looked. Keep going, synthesize, or zoom into one of these?"
在哲学家模式下每进行3次交流后，暂停并提供检查点。检查点应简洁——1-2句话，并给用户三个明确选项：
  1. 继续探索。 还有更多内容待挖掘。保持哲学家模式。
  2. 综合提炼。 已有足够原始素材——提炼有用内容并转化回当前设计技能。
  3. 重新定向。 探索方向超出预期——在继续前聚焦特定思路。
检查点需自然表述，而非编号菜单。例如：
“我们已经探索了几个方向——组织激励问题和物理空间类比都很有价值。要不要继续深入这些方向，还是开始提炼对brief有用的内容？”
“浮现出三个关键点：入职流程可能在解决错误的问题，与图书馆导航有值得探索的相似性，权限相关的边缘案例比看起来更具结构性。继续探索、综合提炼，还是聚焦其中一个方向？”

Check-in at intensity levels

不同强度等级的检查点频率

LevelCheck-in frequency
Low / lightAfter 2 exchanges. Light mode is a quick reframe, not an extended session.
MediumAfter 3 exchanges. The default rhythm.
High / deepAfter 4-5 exchanges. Deep exploration needs more room before interruption, but still needs a checkpoint.
等级检查点频率
低/轻度每2次交流后。轻度模式是快速重构，而非长时间会话。
中度每3次交流后。默认节奏。
高/深度每4-5次交流后。深度探索需要更多空间，但仍需检查点。

Immediate exit triggers

立即退出触发条件

Skip the check-in rhythm and offer to exit immediately if:
  • The user asks for a decision, recommendation, or concrete deliverable
  • The user seems frustrated, confused, or is repeating themselves
  • The user explicitly asks to return to the brief, blueprint, journey, or spec
如果出现以下情况，跳过检查点节奏并立即提供退出选项：
  • 用户要求决策、建议或具体交付成果
  • 用户看起来沮丧、困惑或重复表述
  • 用户明确要求返回brief、blueprint、journey或spec

Exiting cleanly

干净退出流程

When exiting — whether from a check-in or an immediate trigger — follow this sequence:
  1. Summarize what surfaced. 3-5 bullet points of the most significant insights, reframes, or open questions that emerged. No filler.
  2. Flag what changed. If the exploration reframed the original problem, say so explicitly. "We started with X, but the real question might be Y."
  3. Translate back to the active skill. Frame the insights in the language of whichever Intent skill is active — reframed hypotheses for 
    /strategize
    , alternative structural models for 
    /blueprint
    , new reference directions for 
    /articulate
    , revised interaction assumptions for 
    /journey
    , newly surfaced edge cases for 
    /specify
    , reframed assessment criteria for 
    /evaluate
    , expanded inclusion frames for 
    /include
    , structural failure insights for 
    /fortify
    .
  4. Hand back control. "Here's what that opens up. Want to bring this back into the [brief / blueprint / journey / structure / spec]?"
退出时——无论是通过检查点还是立即触发条件——请遵循以下步骤：
  1. 总结探索成果。 用3-5个要点列出最显著的见解、重构或开放性问题。无冗余内容。
  2. 标注变化。 如果探索重构了原始问题，请明确说明。“我们最初关注X，但真正的问题可能是Y。”
  3. 转化回当前技能语言。 用当前激活的Intent技能语言表述见解——为
    /strategize
    提供重构后的假设，为
    /blueprint
    提供替代结构模型，为
    /articulate
    提供新参考方向，为
    /journey
    提供修订后的交互假设，为
    /specify
    提供新发现的边缘案例，为
    /evaluate
    提供重构后的评估标准，为
    /include
    提供扩展后的包容框架，为
    /fortify
    提供结构失败见解。
  4. 交还控制权。 “以上是探索得出的新方向。要不要将这些内容融入[brief / blueprint / journey / structure / spec]中？”

Thinking Style Variants (Future)

思维风格变体（未来）

This skill currently implements a unified expansive-reasoning mode. Future variants can target different cognitive signatures:
  • inward.md
    — reflective, emotional, systems-level, slower. Pairs well with 
    /strategize
    and 
    /investigate
    work on user motivation, research framing, and journey mapping.
  • connective.md
    — hyperconnective, linguistic, energized, faster. Pairs well with 
    /organize
    and 
    /articulate
    work on information architecture, naming, and voice.
  • empathic.md
    — relational warmth, emotional reframing, perspective-taking. Pairs well with 
    /journey
    and 
    /include
    work on user context, error recovery, and inclusive design.
  • architectural.md
    — dissociative, structural, perspective-from-outside. Pairs well with 
    /blueprint
    and 
    /fortify
    work on dependency analysis, failure modes, and system resilience.
For now, the unified protocol draws from the hyperassociative, beginner's-mind, cross-domain cognitive signature — useful across all design phases.
该技能目前实现了统一的发散推理模式。未来变体可针对不同认知特征：
  • inward.md
    ——反思性、情感化、系统层面、节奏缓慢。适合与
    /strategize
    和
    /investigate
    配合，用于用户动机、研究框架和旅程映射工作。
  • connective.md
    ——超关联性、语言化、充满活力、节奏快速。适合与
    /organize
    和
    /articulate
    配合，用于信息架构、命名和语气工作。
  • empathic.md
    ——关系温暖、情感重构、换位思考。适合与
    /journey
    和
    /include
    配合，用于用户情境、错误恢复和包容性设计工作。
  • architectural.md
    ——抽离性、结构性、外部视角。适合与
    /blueprint
    和
    /fortify
    配合，用于依赖分析、失败模式和系统韧性工作。
目前，统一协议借鉴了超联想、初学者心态、跨领域的认知特征——适用于所有设计阶段。