search

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Searching Mobbin

搜索 Mobbin

Read best practices first. If the Mobbin

best-practices

skill hasn't been read in this conversation, invoke it before searching, since it says when a search should run at all and when another skill should run it.

A calling skill may set its own search rules, such as how many queries per problem or which mode to use. Where they differ from these, the calling skill's rule wins.

先阅读最佳实践。 如果本次对话中尚未读取 Mobbin

best-practices

skill，请在搜索前调用它，因为该 skill 会说明何时应执行搜索，以及何时应改用其他 skill。

调用方 skill 可以设置自己的搜索规则，例如每个问题执行多少次查询或使用哪种模式。如果这些规则与本文规则不同，以调用方 skill 的规则为准。

How search works

搜索的工作方式

Search matches meaning, not keywords. Describe what you would see.
Name an app only when the task needs it. Adding an app name to the query filters results to that app. But not every result is from that app, so check
```
app_name
```
and
```
site_name
```
before citing.
The query also sets a language filter on screens and flows when it names one ("Japanese banking app"). Name a language only when the task needs it.
When results are weak, change the query. Raising
```
limit
```
or resending the query as it was brings back the same matches. To get more results for a query that works, see A second pull.

搜索匹配的是含义，而不是关键词。 请描述你将会看到的内容。
仅在任务需要时指定 app。 在查询中加入 app 名称会将结果筛选至该 app。不过，并非所有结果都来自该 app，因此引用前请检查
```
app_name
```
和
```
site_name
```
。
当查询中写明语言时，查询还会对界面和流程设置语言筛选条件（"Japanese banking app"）。仅在任务需要时指定语言。
当结果质量不佳时，请更改查询。 提高
```
limit
```
或原样重新发送查询只会得到相同的匹配结果。要为一个有效查询获取更多结果，请参阅第二次拉取。

Choosing the tool

选择工具

Target	Tool
A screen or component in an app	`search_screens` with `platform`
A section of a marketing site (hero, pricing, feature grid, footer)	`search_sections` , which takes no `platform`
A journey, or one screen whose place in a journey matters (the verify-email step of sign-up)	`search_flows` with `platform` . For one screen, pick it from the flow's screens. Only some screens come with a preview; open the `image_url` of any other before citing it

platform

ios

web

, and it is the only filter you set. The tools have no Android, so an Android target searches

ios

. Say the references are iOS wherever you cite them.

目标	工具
app 中的界面或组件	搭配 `platform` 使用 `search_screens`
营销网站中的区块（hero、pricing、feature grid、footer）	`search_sections` ，无需设置 `platform`
用户旅程，或所在位置在旅程中很重要的单个界面（例如注册过程中的验证邮箱步骤）	搭配 `platform` 使用 `search_flows` 。对于单个界面，请从流程的 screens 中选择。只有部分 screens 附有预览；引用其他 screen 前，请打开其 `image_url` 。

platform

是

ios

或

web

，也是唯一需要设置的筛选条件。这些工具不支持 Android，因此以 Android 为目标时搜索

ios

。无论在何处引用参考资料，都应说明它们来自 iOS。

Choosing the mode

选择模式

mode

is on

search_screens

only.

deep
for a query with several parts ("paywall with lifetime option and a discount").
standard
for a lookup within one named app ("Calm paywall").
When unsure,
```
deep
```
.

deep

drops matches it scores as weak, so it can return fewer results than

limit

. A short pull means few close matches, not that Mobbin has none. Send a second pull or change the query before you say something is missing.

mode

仅适用于

search_screens

。

对于包含多个部分的查询（"paywall with lifetime option and a discount"），使用 deep
。
对于在某个指定 app 内进行的查找（"Calm paywall"），使用 standard
。
不确定时，使用
```
deep
```
。

deep

会过滤掉评分较低的匹配项，因此返回的结果可能少于

limit

。一次拉取仅返回少量结果，表示高度匹配项较少，并不表示 Mobbin 中没有相关内容。在声称某项内容不存在之前，请先发起第二次拉取或更改查询。

Writing the query

编写查询

One screen, flow or section per query, with at most three constraints. Start with the type, then add the state or step and the visible parts the task turns on. The type is the target. Each state, step or part is one constraint: "paywall with plan cards and a free trial button" has two. Length is not the limit. A long query about one target works as well as a short one, but too many constraints blur the results.

Rules:

Search at the target's level. A screen target searches the whole screen ("expense tracker home with no transactions"), never one card of it. A component target searches the screen it lives on.
When the task is choosing between options, name the part, not one of the options. The results need to show more than one way to solve it: "paywall with plan cards and a free trial button", not "paywall with a yearly toggle". Don't join options with "or", and don't put a fix in the query ("with a prompt to add", "placeholder bars"). When the task is finding that exact thing, name it ("banking app search tab with a text label").
Say each thing once. "Empty state", "no transactions yet" and "before any are added" are one state. Keep the shortest.
A fourth constraint goes in a second query. Don't add it to the first.

Don't	Do
"paywall where the trial button is buried below a long table" (the problem in the query)	"paywall with plan cards and a free trial button"
"expense tracker home overview in empty state with no transactions yet and prompt to add first expense" (the state said twice, a fix named)	"expense tracker home with no transactions"
"spending chart card with no data yet, placeholder bars or empty donut" (one card of a screen target, two options joined by "or")	"spending overview with no transactions"
"ios signup screen" (platform in the query)	"signup screen", with `platform` `ios`
"clean modern invoice list for Acme" (taste words, the user's product)	"invoice list with filter chips"
"login screen without Google sign in" (a negation boosts the thing negated)	"login screen with only email and password fields"
"onboarding paywall settings" (several screen types in one query)	one call per screen type
"toast" (one ambiguous word)	"toast notification confirming an item was saved"
"pricing page with hero, plans and FAQ" (several sections in one query)	"pricing section with three tiers and an annual toggle"
"invite teammates screen" (one screen, when the target is a journey)	"inviting teammates during workspace setup", on `search_flows`

Leave out the user's copy, data and brand, and instructions such as "examples of" or "best". Visual traits Mobbin tags can help when they matter:

dark mode

bottom sheet

modal

full-screen

card-based

When a pull returns products from outside the task's domain, search again with the domain's noun ("meditation app paywall with plan cards") instead of citing them. If you do cite a product from another domain, say it is there for its structure only.

每个查询只针对一个界面、流程或区块，并且最多包含三个约束条件。 先写类型，再添加任务所关注的状态或步骤以及可见部分。类型就是目标。每个状态、步骤或部分各算一个约束条件："paywall with plan cards and a free trial button" 包含两个约束条件。限制因素不是查询长度。围绕单一目标编写的长查询与短查询一样有效，但过多的约束条件会使结果变得模糊。

规则：

在目标的层级上搜索。 界面目标应搜索整个界面（"expense tracker home with no transactions"），而不是其中的一张卡片。组件目标应搜索它所在的界面。
当任务需要比较不同方案时，指定组成部分，而不是某一个具体方案。 结果需要展示多种解决问题的方式：使用 "paywall with plan cards and a free trial button"，而不是 "paywall with a yearly toggle"。不要用 "or" 连接不同方案，也不要在查询中写入解决方案（"with a prompt to add"、"placeholder bars"）。当任务需要查找某个确切元素时，应直接指定它（"banking app search tab with a text label"）。
每项内容只说一次。 "Empty state"、"no transactions yet" 和 "before any are added" 表达的是同一种状态。请保留最简洁的表述。
第四个约束条件应放入第二次查询。 不要将它添加到第一个查询中。

不要	应当
"paywall where the trial button is buried below a long table"（在查询中描述问题）	"paywall with plan cards and a free trial button"
"expense tracker home overview in empty state with no transactions yet and prompt to add first expense"（重复描述状态，并指定修复方案）	"expense tracker home with no transactions"
"spending chart card with no data yet, placeholder bars or empty donut"（界面目标中的一张卡片，并使用 "or" 连接两个方案）	"spending overview with no transactions"
"ios signup screen"（在查询中指定平台）	"signup screen"，并设置 `platform` 为 `ios`
"clean modern invoice list for Acme"（包含审美词和用户的产品名称）	"invoice list with filter chips"
"login screen without Google sign in"（否定表述会提高被否定元素的权重）	"login screen with only email and password fields"
"onboarding paywall settings"（一个查询中包含多种界面类型）	每种界面类型分别调用一次
"toast"（含义不明确的单个词）	"toast notification confirming an item was saved"
"pricing page with hero, plans and FAQ"（一个查询中包含多个区块）	"pricing section with three tiers and an annual toggle"
"invite teammates screen"（目标是用户旅程，却只搜索单个界面）	使用 `search_flows` 搜索 "inviting teammates during workspace setup"

省略用户的文案、数据和品牌，以及 "examples of" 或 "best" 之类的指令。在重要时，可以使用 Mobbin 已标记的视觉特征来帮助搜索：

dark mode

、

bottom sheet

、

modal

、

full-screen

、

card-based

。

如果一次拉取返回了任务领域之外的产品，请使用该领域的名词重新搜索（"meditation app paywall with plan cards"），而不是直接引用这些结果。如果确实要引用其他领域的产品，请说明引用它仅是因为其结构。

A second pull

第二次拉取

When a pull doesn't cover what you need, send the same query again with the tool's way of getting more results. That brings new results instead of the first ones reordered. Changing the query makes it a new search, even with exclusions.

```
search_screens
```
: the same query and
```
mode
```
, with every id already seen in
```
exclude_screen_ids
```
, up to 100.
```
search_sections
```
and
```
search_flows
```
: the next
```
page
```
, dropping results already seen. When
```
has_next_page
```
is false, there is no next page, so change the query instead.

当一次拉取未覆盖所需内容时，使用对应工具获取更多结果的方式，再次发送相同查询。这样可以返回新结果，而不是重新排列第一批结果。更改查询即使带有排除条件，也属于一次新搜索。

```
search_screens
```
：使用相同的查询和
```
mode
```
，并在
```
exclude_screen_ids
```
中包含所有已见过的 id，最多 100 个。
```
search_sections
```
和
```
search_flows
```
：请求下一页
```
page
```
，并排除已经看过的结果。当
```
has_next_page
```
为 false 时，不存在下一页，因此请更改查询。

When a search falls short

搜索结果不足时

Handle each case as below. When one still fails, say so in one line, where the calling skill reports a lost search or in the reply when there is none.

A named product doesn't come up, meaning it's in no result's

app_name

site_name

If the query spelled the name differently from the product, search again with the product's own spelling.
On sections, which have no name filter, ask for the next
```
page
```
while
```
has_next_page
```
is true. The site may rank past the first page.
On screens and flows, when the task isn't tied to one platform, try the other
```
platform
```
, since a product can be on Mobbin for iOS or web only. Cite what you find as that platform. Skip this step when the task is for one platform (an iOS redesign has no use for a web screen).

If it's still missing, carry on with the category search. Describe nothing about the product from memory, and don't let another product's screen stand in for it. A screenshot the user shared of it stays their reference.

Images don't open. Previews come as

webp

, which not every host can open. Call again with

image_format

set to

jpg

. If they still don't open, cite nothing from that call, since a screen you couldn't see is not a reference.

The tool refuses the call. Don't retry it or change the query, since every call will be refused. Stop searching and say so. An error about the input, such as an invalid argument, is different: fix the input and call again.

请按以下方式处理每种情况。如果仍未解决，用一行说明；调用方 skill 需要报告搜索失败时，将说明写入其中，否则写入回复。

未找到指定产品，即任何结果的

app_name

或

site_name

中都没有它：

如果查询中的名称拼写与产品名称不同，请使用产品自身的拼写重新搜索。
对于没有名称筛选条件的 sections，请在
```
has_next_page
```
为 true 时请求下一页
```
page
```
。该网站可能排在第一页之后。
对于 screens 和 flows，如果任务不限定单一平台，请尝试另一个
```
platform
```
，因为某个产品可能只收录在 Mobbin 的 iOS 或 web 端。引用找到的内容时，应注明对应平台。如果任务仅针对一个平台，则跳过此步骤（例如，iOS 重新设计无法使用 web 界面）。

如果仍未找到，请继续按类别搜索。不要根据记忆描述该产品，也不要用其他产品的界面代替它。用户分享的该产品截图仍应作为用户的参考资料。

图片无法打开。 预览以

webp

格式返回，并非所有主机都能打开。请再次调用，并将

image_format

设置为

jpg

。如果仍然无法打开，则不要引用该次调用返回的任何内容，因为无法看到的界面不能作为参考资料。

工具拒绝调用。 不要重试或更改查询，因为每次调用都会被拒绝。停止搜索并说明情况。输入错误（例如参数无效）属于不同情况：修正输入后再次调用。