help
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
Chinesehelp: route to the right skill
help:路由至合适的技能
Step 0: Preflight
步骤0:预检
Read and apply its Help exception. A Ready system
reads the "When you say X, I run Y" table in the founder's charter (AGENTS.md / CLAUDE.md).
Answer from it: name the ONE skill that fits what they described, say why in a sentence, and
give them the exact phrase to say. Two skills genuinely fit: name the order to run them in.
${CLAUDE_SKILL_DIR}/../../CONVENTIONS.mdResolve the two loaded collisions by intent. "Whether should we do/build/change this?" routes
to the gauntlet; "how do we execute the decision already made?" routes to plan. For pricing, "should
we change the price?" routes to the gauntlet; "how do we structure the approved price or offer?"
routes to offer. State the distinction in one sentence when the wording is ambiguous.
Complete the whole routing hop before naming the skill. For any offer, price, spend, or other
money move, inspect and matching initiatives. An unresolved whether-call,
an unapproved price/offer, or a BIG move without a current SURVIVES verdict routes directly to
the gauntlet. Offer is the destination only when the exact move is already approved and the founder is
asking how to structure it. Never send the founder offer → gauntlet for a gate help could see now.
wiki/business/offer.mdResolve parked prerequisites before the owner skill. If the exact initiative says , route first to the named measurement or recall action, then the gauntlet, then
offer after SURVIVES. If it says , route , then
offer after SURVIVES. An with no verdict routes to the gauntlet; a current SURVIVES verdict routes
to offer. Return the complete chain in three lines: , , .
PARKED: internal receipt missingPARKED: external receipt missingresearch → gauntletideaNowThenAfter the gateHelp answers the current prompt and stops. A new prompt replaces the prior routing task; help does
not start steward, review, or any unrelated audit before returning the route. For "I want to charge
1,500. Set it up" against a price initiative parked on delivery evidence, the answer starts with
that measurement, continues to the gauntlet, and reaches offer only after the gate survives.
Any Fresh, Partial, or Wrong-folder result points to (re-sync for Partial)
and stops there.
/co-founder:co-founder-setupAsk before you assert: never present a quantity, duration, sample size, date, or causal motive
in prose before asking the founder for it or citing a receipt for it.
阅读并应用其中的Help例外规则。就绪系统需阅读创始人章程(AGENTS.md / CLAUDE.md)中的“当你说X,我执行Y”表格。据此作答:指出一项符合用户描述的技能,用一句话说明原因,并告知用户需使用的准确表述。若有两项技能均符合,说明它们的执行顺序。
${CLAUDE_SKILL_DIR}/../../CONVENTIONS.md根据意图解决两种已加载的冲突。“我们是否应该做/构建/更改这件事?”路由至gauntlet;“我们如何执行已做出的决策?”路由至plan。对于定价问题,“我们是否应该调整价格?”路由至gauntlet;“我们如何构建已获批的价格或方案?”路由至offer。当表述模糊时,用一句话说明两者的区别。
在指定技能前完成整个路由流程。对于任何报价、定价、支出或其他资金操作,需查看及对应的行动计划。未解决的是否类请求、未获批的定价/报价,或未获得当前SURVIVES结论的重大操作,直接路由至gauntlet。只有当具体操作已获批,且创始人询问如何构建时,才将offer作为目标路径。绝不要让创始人先进入offer再转到gauntlet,因为当前的help即可识别出该走的路径。
wiki/business/offer.md在进入目标技能前,先解决已暂停的前置条件。若具体行动计划标注,则先路由至指定的评估或召回操作,再进入gauntlet,待通过SURVIVES后再进入offer。若标注,则路由顺序为,待通过SURVIVES后再进入offer。未得出结论的路由至gauntlet;已获得当前SURVIVES结论的路由至offer。用三行返回完整流程:、、。
PARKED: internal receipt missingPARKED: external receipt missingresearch → gauntletidea当前下一步通过关卡后Help仅响应当前请求并终止。新的请求会替代之前的路由任务;在返回路由结果前,help不会启动steward、review或任何无关的审核流程。例如,当用户提出“我想收取1500元,帮我设置”,但对应的定价行动计划因交付证据缺失而暂停时,回答应先指向该评估操作,接着是gauntlet,仅在通过关卡后才进入offer。
任何Fresh、Partial或Wrong-folder结果均指向(Partial状态需重新同步),并在此终止。
/co-founder:co-founder-setup先询问再断言: 在向创始人询问相关信息或引用凭证之前,切勿在文本中提及数量、时长、样本量、日期或因果动机。