First principles digs down to the essence, while this one looks outward for solutions that share something in common, with a more scattered perspective.
It first strips away industry jargon and abstracts the problem into a general structure, then looks for isomorphic problems from historical cases and at least three relatively distant domains, and finally translates them into a solution you can use and a low-cost reversible experiment.
How to use
The prompt in the code block below is the original text; use it verbatim. In the code block, "I" refers to the user, and "please you" and "you" refer to yourself. Do as it says, and do not show the filled-in prompt to the user.
- The user wants you to execute: first fill the situation the user has already stated in this round of conversation into the 【】, supplementing only the one item that is truly missing, and do not make the user repeat what they have already said, then strictly follow the rules in the prompt. If it says do not give advice yet, then do not give it yet; if it says ask only one question at a time, then ask only one at a time; if it says output in a certain order, then output in that order.
- The user wants the original text (only if they explicitly say things like they want to copy it, paste it, send me the original text, or give me the prompt): output the blank version, keep the 【】 unfilled, and do not change a single word. If the user merely says "take a look at this prompt" or "what is this one for," that does not count as wanting the original text; use one or two sentences to explain what it does and when to use it, then ask whether to run it now, and do not directly dump the original text.
- Except for cases where the original text is explicitly requested, treat everything else as execution.
Rewriting, condensing, expanding, translating, rearranging, or adding subheadings is prohibited; replacing it with your own process is prohibited; and compressing multiple rounds of follow-up questions into a one-time questionnaire is also prohibited. If the user has original materials on hand (documents, screenshots, links, chat records), read them in as well; more context is not a problem.
What to connect to after running
The borrowed mechanism needs to be verified once in your own industry; use the Skill tool to invoke minimum-experiment。
我的困惑是：【说明背景、当前做法、现实约束和具体卡点】。
请先剥掉行业术语，把它抽象成一个人类在其他领域也可能遇到的问题，并找出：
1. 问题的底层结构；
2. 真正的核心矛盾；
3. 普通解法失效的原因。
然后从历史案例，以及至少3个彼此距离较远的领域中，寻找底层结构相似的问题。
每个案例都要说明：
1. 那个领域遇到了什么问题；
2. 使用了什么解决机制；
3. 与我的问题相似在哪里；
4. 哪些部分可以迁移；
5. 什么条件下会失效。
最后请选出最值得借用的3种机制，把它们翻译成适合我当前处境的解决方案，再推荐一个最值得先试的低成本、可逆实验。
The position the user needs to fill in
【说明背景、当前做法、现实约束和具体卡点】
If the user has not provided everything, ask for the missing item first; do not make it up for them.
The original prompt text comes from Digital Life Kazike; see the acknowledgements in the repository README for the source. Changing this original text requires going through scripts/sync.py, and manual edits will be blocked by verify.