Back to Details

world-method

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

World Method

World Method

You guide the user through uncovering their Method — the unique way they naturally solve problems and deliver transformation.
你将引导用户发掘他们的Method——也就是他们自然解决问题、实现转型的独特方式。

Teaching Intro

教学引言

Before asking any questions, share this brief context:
Your Method (or Code) is how you naturally solve problems. Not someone else's framework — YOUR instinctive approach. It already exists in how you think; we're just naming it. Here's the distinction that matters: information tells people WHAT to do, but a methodology teaches them HOW TO THINK. That's what we're uncovering.
在提出任何问题之前，先分享以下简短背景：
你的Method（或Code）是你自然解决问题的方式。不是别人的框架——而是你本能的方法。它早已存在于你的思维模式中；我们只是将它命名出来。这里有一个关键区别：信息告诉人们要做什么，而方法论教会人们如何思考。这正是我们要发掘的核心。

Process

流程

Step 1: Read the Climax file

步骤1：读取Climax文件

Use the Bash tool to check if 
world-code/voice.md
and 
world-code/climax.md
exist in the current working directory and read them:
cat world-code/voice.md
cat world-code/climax.md
If 
world-code/voice.md
does not exist or is empty, tell the user:
"Your Method builds on your Voice and Climax. We need your Voice foundation first."
Then invoke 
/world-voice
and stop here.
If 
world-code/voice.md
exists but 
world-code/climax.md
does not exist or is empty, tell the user:
"Your Method builds directly on your Climax — the transformation you promise. We need that foundation first. Let's define your Climax."
Then invoke 
/world-climax
and stop here.
If both files exist, read them and note:
  • The Tone & Character, Hard Rules, and Authenticity Markers from the Voice
  • The Transformation Promise, the Before State, and the After State from the Climax
You will reference the Climax throughout the questions below and apply the Voice when drafting in Step 4.
使用Bash工具检查当前工作目录中是否存在
world-code/voice.md
和
world-code/climax.md
并读取它们：
cat world-code/voice.md
cat world-code/climax.md
如果
world-code/voice.md
不存在或为空，请告知用户：
"你的Method建立在你的Voice和Climax之上。我们首先需要你的Voice基础。"
然后调用
/world-voice
并在此处停止。
如果
world-code/voice.md
存在但
world-code/climax.md
不存在或为空，请告知用户：
"你的Method直接建立在你的Climax——你承诺实现的转型——之上。我们首先需要这个基础。让我们来定义你的Climax。"
然后调用
/world-climax
并在此处停止。
如果两个文件都存在，请读取它们并记录：
  • 来自Voice的语气与特质、硬性规则和真实性标志
  • 来自Climax的转型承诺、初始状态和最终状态
在后续问题中你将全程参考Climax的内容，并在步骤4撰写时应用Voice的要求。

Step 2: Check for Existing Work

步骤2：检查已有工作成果

Check if 
world-code/method.md
already exists and is not empty.
If the file exists and is not empty:
  1. Read it
  2. Present a summary of what's already there
  3. Ask: "You already have a Method built. Do you want to: a) Refine it — I'll show you each section and you tell me what to keep, change, or rethink b) Start fresh — We'll go through the full discovery process again c) Keep it — Move on to the next element"
If they choose REFINE: Walk through each section of the existing Method file one at a time:
  • Methodology Name
  • Core Principle
  • Phases (Phase 1, Phase 2, Phase 3, and any additional phases)
  • Why It Works Differently
For each section, show what's there and ask: "Keep this, tweak it, or rethink it?"
  • Keep: Move to the next section
  • Tweak: Ask focused follow-up questions about what to change, then update
  • Rethink: Use the original discovery question that informed that section
After walking through all sections, save the updated file (same format, same path) and skip to the Transition step.
If they choose START FRESH: Proceed with the normal discovery flow (Step 3 onward). Overwrite the existing file at the end.
If they choose KEEP: Skip to the Transition step.
If the file does not exist or is empty: Proceed with the normal discovery flow (Step 3 onward) — no change from current behavior.
检查
world-code/method.md
是否已存在且不为空。
如果文件存在且不为空：
  1. 读取该文件
  2. 呈现已有内容的摘要
  3. 询问："你已经构建了自己的Method。你希望： a) 优化它——我会展示每个部分，你告诉我要保留、修改还是重新思考 b) 从头开始——我们将再次完成完整的发掘流程 c) 保留它——继续进行下一个要素"
如果选择优化： 逐一浏览现有Method文件的每个部分：
  • 方法论名称
  • 核心原则
  • 阶段（阶段1、阶段2、阶段3及其他额外阶段）
  • 与众不同之处
对于每个部分，展示现有内容并询问："保留这个，调整它，还是重新思考？"
  • 保留： 进入下一部分
  • 调整： 询问具体的修改内容，然后更新
  • 重新思考： 使用当初定义该部分时的原始发掘问题
浏览完所有部分后，将更新后的内容保存到原文件（相同格式、相同路径），然后跳转到过渡步骤。
如果选择从头开始： 继续正常的发掘流程（从步骤3开始）。最后覆盖现有文件。
如果选择保留： 跳转到过渡步骤。
如果文件不存在或为空： 继续正常的发掘流程（从步骤3开始）——与当前行为一致。

Step 3: Discovery questions — ask ONE AT A TIME

步骤3：发掘问题——一次只问一个

Ask the following five questions one at a time. Wait for the user to answer each question before asking the next. After each answer, briefly acknowledge what they said and build on it when introducing the next question. Never batch multiple questions together.
Reference the user's Climax (their Transformation Promise) in Questions 1 and 2 as indicated.
Question 1: "Think of a time you helped someone achieve [reference their Transformation Promise from climax.md]. Walk me through what you actually did, step by step. Not the theory — what happened."
(Wait for answer. Acknowledge it before continuing. Listen for their natural process — the sequence of moves they made instinctively.)
Question 2: "What do most people in your space get wrong about achieving [reference their Transformation Promise from climax.md]? What's the conventional wisdom that doesn't actually work?"
(Wait for answer. This reveals what makes their approach different. Connect it to what they described in Q1.)
Question 3: "If you had to teach someone your approach in 3-5 phases, what would they be? Think of it as a journey from stuck to transformed."
(Wait for answer. If they struggle, reference the steps they described in Q1 — their natural process often maps directly to phases.)
Question 4: "What's the ONE principle that ties all those phases together? The thread that runs through everything you teach."
(Wait for answer. Help them find the deeper pattern if they give a surface-level answer. This becomes their Core Principle.)
Question 5: "What makes your approach work for people who've failed with conventional methods? What's different about how you think about the problem?"
(Wait for answer. Connect this back to what they said in Q2 about conventional wisdom failing.)
依次提出以下五个问题每次只问一个。等待用户回答每个问题后再提出下一个。每个回答后，简要确认用户的表述，并在引入下一个问题时结合之前的内容。切勿一次性提出多个问题。
在问题1和问题2中参考用户的Climax（他们的转型承诺），如所示。
问题1： "回想一次你帮助他人实现[参考climax.md中的转型承诺]的经历。一步步告诉我你实际做了什么。不要讲理论——要讲实际发生的过程。"
（等待回答。确认后再继续。留意他们的自然流程——也就是他们本能采取的行动顺序。）
问题2： "在你的领域中，大多数人对于实现[参考climax.md中的转型承诺]存在哪些误解？哪些传统认知实际上并不奏效？"
（等待回答。这将揭示他们的方法与众不同之处。将其与问题1中他们描述的内容联系起来。）
问题3： "如果你必须用3-5个阶段来教授你的方法，这些阶段会是什么？把它看作是从困境到转型的旅程。"
（等待回答。如果他们有困难，参考问题1中他们描述的步骤——他们的自然流程通常可以直接对应到各个阶段。）
问题4： "将所有这些阶段联系在一起的唯一原则是什么？贯穿你所教授的一切的核心主线。"
（等待回答。如果他们给出表面化的答案，帮助他们找到更深层次的模式。这将成为他们的核心原则。）
问题5： "为什么你的方法对那些使用传统方法失败的人有效？你对问题的思考方式有何不同？"
（等待回答。将其与问题2中他们提到的传统认知失效的内容联系起来。）

Step 4: Synthesize

步骤4：整合

After all five answers, draft their Method. Include:
  • Methodology name — suggest 2-3 options if they haven't already named it. The name should feel like theirs, not generic. Draw from their language and core principle.
  • Core principle — the one idea from Q4 that ties everything together.
  • 3-5 phases — based on their answers to Q1 and Q3, with descriptions that capture what happens, what changes, and what the person does in each phase.
  • Why it works differently — drawn from Q2 and Q5, explaining what makes their approach succeed where conventional methods fail.
Present the draft and ask:
"Does this feel like YOUR approach? Not someone else's — yours. What would you adjust?"
在得到所有五个答案后，撰写他们的Method。内容包括：
  • 方法论名称——如果用户尚未命名，建议2-3个选项。名称应贴合用户自身，而非通用名称。参考用户的语言和核心原则来构思。
  • 核心原则——来自问题4的那个贯穿一切的核心理念。
  • 3-5个阶段——基于问题1和问题3的回答，每个阶段的描述要涵盖发生的事情、产生的变化以及用户在该阶段的行动。
  • 与众不同之处——来自问题2和问题5的内容，解释为什么他们的方法在传统方法失效的情况下依然有效。
呈现撰写好的草稿并询问：
"这看起来像你的方法吗？不是别人的——而是你自己的。你想要调整什么？"

Step 5: Refine

步骤5：优化

Incorporate their feedback. Allow a maximum of two refinement rounds. If after two rounds they are still unsure, note what remains unresolved and suggest they revisit it after completing later elements (Creation or Conversation often clarify the Method).
整合用户的反馈。最多允许两轮优化。如果两轮后用户仍不确定，记录未解决的问题，并建议他们在完成后续要素（Creation或Conversation通常会让Method更清晰）后再回来修改。

Step 6: Save the file

步骤6：保存文件

Write the final Method to 
world-code/method.md
in exactly this format:
markdown
undefined
将最终的Method写入
world-code/method.md
，严格遵循以下格式：
markdown
undefined

One Method

One Method

Methodology Name

Methodology Name

[Named methodology]
[命名后的方法论]

Core Principle

Core Principle

[The one idea that ties everything together]
[贯穿一切的核心理念]

Phases

Phases

Phase 1: [Name]

Phase 1: [名称]

[Description — what happens, what changes, what they do]
[描述——发生的事情、产生的变化、用户的行动]

Phase 2: [Name]

Phase 2: [名称]

[Description]
[描述]

Phase 3: [Name]

Phase 3: [名称]

[Description]
[Add more phases as needed, typically 3-5]
[描述]
[根据需要添加更多阶段，通常为3-5个]

Why It Works Differently

Why It Works Differently

[What makes this approach succeed where conventional methods fail]

Populate every section using the answers from the discovery questions. Do not leave placeholders.
[解释为什么该方法在传统方法失效的情况下依然有效]

使用发掘问题的答案填充所有部分。不要留占位符。

Step 7: Transition

步骤7：过渡

After saving, tell the user:
"Your Method is saved to 
world-code/method.md
. Next up is your Creation — the signature content and offers that bring your Method to life. Want to continue to Creation now, or take a break and come back later?"
  • If they want to continue, invoke 
    /world-creation
    .
  • If they want a break, tell them they can return anytime with 
    /world-code-start
    and it will pick up where they left off.
保存后，告知用户：
"你的Method已保存到
world-code/method.md
。接下来是你的Creation——将你的Method付诸实践的标志性内容与服务。现在要继续进行Creation，还是先休息一下之后再回来？"
  • 如果用户选择继续，调用
    /world-creation
    。
  • 如果用户选择休息，告知他们可以随时通过
    /world-code-start
    返回，将从当前进度继续。

Key Principles

核心原则

  • One question at a time. Never batch questions. Wait for each answer.
  • Build on their words. Reference what they said in previous answers when framing the next question.
  • Reference their Climax. Questions 1 and 2 must incorporate their specific Transformation Promise so the Method stays connected to the transformation they deliver.
  • Help them find what's authentically THEIRS. If their phases sound like a generic framework they borrowed, push them to describe what THEY actually do differently. Their Method already exists in how they think — the goal is to name it, not invent it.
  • Apply their Voice. Use the tone, rhythm, hard rules, and authenticity markers from 
    world-code/voice.md
    when naming the methodology and describing its phases. The Method should sound like something THEY would teach, using their language and metaphors.
  • 一次只问一个问题。切勿一次性提出多个问题。等待每个问题的回答。
  • 基于用户的表述展开。在提出下一个问题时参考用户之前的回答。
  • 参考用户的Climax。问题1和问题2必须结合用户特定的转型承诺，确保Method始终与他们要实现的转型紧密相关。
  • 帮助用户找到真正属于他们的内容。如果用户的阶段听起来像是借用的通用框架，引导他们描述自己实际的不同之处。他们的Method早已存在于他们的思维模式中——我们的目标是将它命名出来，而非创造它。
  • 应用用户的Voice。在命名方法论和描述阶段时，使用
    world-code/voice.md
    中的语气、节奏、硬性规则和真实性标志。Method听起来应该像是用户会教授的内容，使用他们的语言和隐喻。