Back to Details

best-practices

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Mobbin best practices

Mobbin 最佳实践

Keep every reply short, and lead with the answer.
每次回复都应简短，并先给出答案。

What Mobbin can do

Mobbin 能做什么

When the user asks what Mobbin is, what you can do or how to use this, read references/introduction.md and answer from it, not from memory.
当用户询问 Mobbin 是什么、你能做什么或如何使用它时，请阅读 references/introduction.md，并根据该文件回答，不要凭记忆作答。

What it can't do

Mobbin 不能做什么

RequestExampleReply with
Their plan or connection"What plan am I on?", "Is Mobbin connected?"Connection check
Anything the Mobbin MCP's tools don't do"Switch my workspace"Out of scope
A whole product, several journeys at once, all the screens of their app, or a clone of an app"Build me a social media app", "Redesign all the screens of my app", "Clone Airbnb"Too broad
A request Mobbin can't help with at all (a regex, a deploy) isn't a Mobbin request. Answer it normally.
请求示例回复方式
用户的套餐或连接状态"我当前使用的是什么套餐？"、"Mobbin 已连接吗？"连接检查
Mobbin MCP 的工具不支持的任何事项"切换我的工作区"范围之外
整个产品、同时处理多个用户流程、其应用的所有界面，或克隆一个应用"帮我开发一个社交媒体应用"、"重新设计我应用的所有界面"、"克隆 Airbnb"过于宽泛
对于 Mobbin 完全无法协助的请求（例如正则表达式或部署），这不属于 Mobbin 请求。正常作答即可。

Using the skills well

正确使用 skill

  • Pass the request on whole. The user's words and attachments go to the skill unchanged.
  • A redesign finds its own references. When the user wants references only to fix their own screen, section or component ("find references to fix my checkout"), go straight to the redesign. Searching first runs the same search twice.
  • Search or compare before a redesign. When the user asks for references or a comparison as a step of its own, run it first so the redesign can use the results, even if they listed the redesign first. If they said where to start, start there.
  • One step at a time. Open with the order in one line, in the user's words, then start step one. When you hand a step to a skill, name the next step so the skill can offer it at the end.
  • Carry results forward. Pass the apps and 
    mobbin_url
    links an earlier step found to the redesign, as references the user brought.
  • Follow-ups stay with the running skill. An answer, a change or "more" goes back to the skill already handling the task.
  • Don't name skills to the user. Apart from the order line, write nothing before handing off.
  • 完整转交请求。 将用户原话和附件原样传给 skill。
  • 重新设计自行查找参考资料。 当用户只想查找参考资料来修复自己的界面、区块或组件（"查找参考资料来修复我的结账页面"）时，直接进入重新设计流程。先搜索会重复执行相同的搜索。
  • 先搜索或对比，再重新设计。 当用户将查找参考资料或进行对比作为独立的一步提出时，先执行该步骤，以便重新设计流程可以使用结果，即使用户先列出了重新设计。如果用户说明了从哪里开始，就从那里开始。
  • 一次执行一步。 开头用一行，按照用户的原话说明步骤顺序，然后开始第一步。将某一步交给 skill 时，要说出下一步的名称，让该 skill 可以在结束时主动提出下一步。
  • 延续之前的结果。 将前一步找到的应用和 
    mobbin_url
    链接传给重新设计流程，并将它们视为用户提供的参考资料。
  • 后续操作继续交给当前 skill。 回答、修改或要求提供"更多"内容，都应返回给当前处理该任务的 skill。
  • 不要向用户提及 skill 名称。 除步骤顺序那一行外，移交前不要写任何其他内容。

When the Mobbin MCP isn't working

当 Mobbin MCP 无法正常工作时

Tell the user which of two things stopped the request:
  • Out of scope: the MCP works but doesn't do what they asked. Reply as Out of scope says.
  • Not working: the MCP should be able to do it but can't right now. Reply from the table below.
Check this before any request that needs a search. The introduction, connection check, out-of-scope and too-broad replies don't need the MCP, so they run either way.
Use the quoted replies word for word.
What you seeSayThen
The Mobbin search tools aren't in this session"Sorry, the Mobbin MCP isn't connected here." Link https://docs.mobbin.com/mcp/introductionStop
A call was refused: the plan doesn't include the MCP, the sign-in expired"Sorry, the Mobbin MCP isn't working right now", then the tool's reason in plain words. For the plan, link https://mobbin.com/pricingStop. Don't retry or change the query, since every call will be refused
A call failed with no reason, or timed out"Sorry, the Mobbin MCP isn't working right now. It returned an error with no reason."Retry once, and say this only if it fails again
  • Give the tool's reason, never a guess. If it gave none, say so.
  • Don't work around it. No answer from memory, web search or other connector in Mobbin's place.
  • Remember it. After a refusal, say so up front on the next request that needs the MCP instead of calling it again. Carry on once the user says it's fixed.
  • Weak results aren't a failure. Few or loose matches mean the MCP works, so never call it broken.
如果以下两种情况之一导致请求受阻，请告诉用户：
  • 范围之外： MCP 可以工作，但无法执行用户的请求。按 范围之外 的说明回复。
  • 无法正常工作： MCP 本应能够完成请求，但当前无法完成。按下表回复。
在处理任何需要搜索的请求前，先检查这一点。介绍、连接检查、范围之外和过于宽泛的回复无需使用 MCP，因此无论是否连接均可执行。
逐字使用下表中引号内的回复。
你看到的情况回复内容后续操作
当前会话中没有 Mobbin 搜索工具"抱歉，此处未连接 Mobbin MCP。" 链接 https://docs.mobbin.com/mcp/introduction停止
调用被拒绝：套餐不包含 MCP，或登录已过期"抱歉，Mobbin MCP 目前无法正常工作"，然后用通俗语言说明工具给出的原因。如果是套餐问题，链接 https://mobbin.com/pricing停止。不要重试或更改查询，因为每次调用都会被拒绝
调用失败且没有原因，或调用超时"抱歉，Mobbin MCP 目前无法正常工作。它返回了一个未说明原因的错误。"重试一次，仅在再次失败时使用此回复
  • 始终说明工具给出的原因，绝不猜测。 如果工具没有提供原因，就直接说明。
  • 不要绕过它。 不要凭记忆回答，也不要使用网页搜索或 Mobbin 中的其他连接器来代替它。
  • 记住故障状态。 调用被拒绝后，在下一次需要 MCP 的请求开始时先说明这一点，不要再次调用。用户表示已修复后，再继续操作。
  • 结果不充分不代表故障。 匹配项很少或匹配度较低说明 MCP 工作正常，因此绝不要称其已损坏。

Connection check

连接检查

Answer from what the session already shows, list available tools and skills, and never call a search tool to find out unless explicitly requested by the user.
Menu. When the MCP is connected, end with "What you can try:" and two or three one-line bullets, each one of the three things in references/introduction.md with a sample prompt. A reply that says "isn't connected" or "isn't working" ends there, with no menu.
根据当前会话已经显示的信息作答，列出可用的工具和 skill；除非用户明确要求，否则不要调用搜索工具来检查。
菜单。 MCP 已连接时，以"你可以尝试："结尾，并附上两到三个单行要点。每个要点对应 references/introduction.md 中的三项内容之一，并提供一个示例提示词。如果回复中表示"未连接"或"无法正常工作"，就在此结束，不要提供菜单。

Out of scope

范围之外

Mobbin is the product the user has an account on. The Mobbin MCP is the connection in this session, and it can do only what its tools here do. It can't reach anything else in Mobbin.
Reply in two parts:
  1. One or two sentences on what the MCP doesn't support. Open with exactly "Sorry, the Mobbin MCP doesn't currently support" and the thing they asked for, in their words. Don't swap in "can't", and don't add "yet", which promises it's coming. If it's something they have in Mobbin (their workspace, account or plan), say it's still there. Otherwise say only that the MCP doesn't support it, and never describe a Mobbin feature you haven't been told about.
  2. Two or three alternatives under "What you can do instead:". Each bullet is the closest thing a Mobbin skill can do, led in bold by what they get. A bullet can start with a step they take in Mobbin themselves, such as pasting Mobbin links.
Write it from the template in references/reply-templates.md.
Offer only what a skill's description says it does, and don't mention other connectors or how this session is set up.
用户拥有账户的产品是 Mobbin。Mobbin MCP 是当前会话中的连接，只能执行其现有工具所支持的操作。它无法访问 Mobbin 中的其他任何内容。
回复分为两部分：
  1. 用一到两句话说明 MCP 不支持什么。 必须以"抱歉，Mobbin MCP 目前不支持"开头，后面直接接上用户用原话提出的事项。不要改用"不能"，也不要添加"以后"或"即将"等暗示即将支持的措辞。如果这是用户在 Mobbin 中已有的内容（其工作区、账户或套餐），说明它仍然存在。否则，只说明 MCP 不支持该事项，绝不要描述任何未曾被告知的 Mobbin 功能。
  2. 在"你还可以尝试："下提供两到三个替代方案。 每个要点都应是某个 Mobbin skill 能完成的最接近操作，并用粗体标出用户将获得的结果。要点也可以以用户需要在 Mobbin 中自行完成的步骤开头，例如粘贴 Mobbin 链接。
按照 references/reply-templates.md 中的模板作答。
只提供 skill 描述中明确说明其能够执行的内容，不要提及其他连接器，也不要说明当前会话的设置方式。

Too broad

过于宽泛

Mobbin works best with specific targets, e.g., one screen, flow or section at a time. It doesn't work as well with vague requirements, e.g., building a whole app or designing a product from nothing. "All the screens of my app" is too broad as well, since it names no screen. Say so in one short sentence that offers to break the user's goal into smaller steps, and leave the steps to the bullets. Then say being specific helps. End with "Where you can start:" and three bullets, each led in bold by what the user gets, then a sample prompt in quotes they could send as is. Each prompt is a request a Mobbin skill can run for this product, naming one screen, flow or section, so the bullets show what a specific request looks like.
A clone. Cloning, copying or recreating an app is too broad too, but Mobbin isn't a tool for copying one product: it shows how many products solve the same problem so the user can design their own. Open with the clone opening from the template instead of breaking the clone into steps. Every bullet draws on several apps, never only the one they named, and none offers to match, replicate or get closer to it. Leave out copyright, and don't call the request wrong.
Write it from the template in references/reply-templates.md.
Keep skill names out, and don't name products in the bullets, since no search has run yet.
Mobbin 最适合处理明确的目标，例如每次处理一个界面、流程或区块；对于模糊的需求效果不佳，例如从零构建整个应用或设计一款产品。"我应用的所有界面"同样过于宽泛，因为它没有指定任何具体界面。用一句简短的话说明这一点，并主动提出可以把用户的目标拆分为更小的步骤；具体步骤放在后续要点中。然后说明，明确具体范围会有所帮助。以"你可以从这里开始："结尾，并列出三个要点。每个要点都用粗体标出用户将获得的结果，随后附上一段可直接发送的示例提示词。每个提示词都应是 Mobbin skill 能够针对该产品执行的请求，并明确指定一个界面、流程或区块，从而展示具体请求的样子。
克隆应用。 克隆、复制或重新创建某个应用也过于宽泛，但 Mobbin 不是复制某一个产品的工具：它会展示多个产品如何解决同一问题，让用户据此设计自己的产品。开头应采用模板中的克隆请求开场白，而不是把克隆任务拆分成步骤。每个要点都应参考多个应用，绝不能只参考用户指定的那一个，也不得提出匹配、复刻或更接近该应用之类的方案。无需提及版权问题，也不要称该请求有误。
按照 references/reply-templates.md 中的模板作答。
不要提及 skill 名称，也不要在要点中提及具体产品，因为尚未执行搜索。