gather

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Gather

This skill collects inspiration before a design is built or reworked. It searches the user's own saves first, then wider sources, and returns one board where every reference links back and names what to take.

该 skill 会在设计开发或改版前收集灵感。它会先搜索用户自有的收藏内容，再扩展到更广泛的来源，最终返回一个看板，其中每条参考素材都可链接回原始来源，并注明可借鉴的部分。

Evidence for a choice, not a style to copy

为选择提供依据，而非照搬风格

A reference shows how one part could work. Taking a whole app's look when the user asked for its top bar is a finding. With no number given, gather at least 20 references from at least three sources.

Use it when the user asks for inspiration, references or "inspo", or says a screen looks bad and asks how to improve it. Building variants from the board belongs to

prototype

. Rebuilding one reference value for value belongs to

match

参考素材展示了某个部分可以如何实现。用户只要求顶部栏，却照搬整个应用的外观，就属于一项问题。未指定数量时，至少收集来自三个来源的 20 条参考素材。

当用户索要灵感、参考素材或“inspo”，或表示某个界面不好看并询问如何改进时，使用该 skill。基于看板构建不同变体应使用

prototype

。逐项复刻某一个参考素材则应使用

match

。

1. Name the brief

1. 明确需求概述

Write one line naming the surface, its platform and what to look for: layout, navigation, density, type, colour, motion or overall taste. A search with no target is

gather-name-the-brief

Search on the same platform as the work. A desktop or web app takes web and desktop references. Mobile screens for a desktop app is

gather-same-platform

用一行说明界面类型、目标平台和关注点：布局、导航、信息密度、字体、配色、动效或整体审美。搜索时没有明确目标，属于

gather-name-the-brief

。

在与目标作品相同的平台上搜索。桌面端或 Web 应用应收集 Web 和桌面端参考。为桌面端应用使用移动端界面，属于

gather-same-platform

。

2. Start with what the user gave

2. 先处理用户提供的内容

Open the tabs, screenshots, links and design files already in the thread before searching anywhere. Searching a pattern library while the user's screenshots sit open in the browser is

gather-start-with-given

在搜索任何内容之前，先打开当前对话中已有的标签页、截图、链接和设计文件。当用户的截图已在浏览器中打开，却先去搜索模式库时，属于

gather-start-with-given

。

3. Search the user's own taste first

3. 优先搜索用户自有素材

Search the user's own library and boards before public sources. Their saves already reflect their taste. Starting from a public library when their own library holds matching saves is

gather-own-library-first

. If none of the user's sources are connected, stop and name each choice: Are.na, Cosmos, Pinterest, Mobbin and Pond. A prompt that drops one of those names is

gather-list-the-sources

. How to reach each source is in sources.md.

先搜索用户自有素材库和收藏板，再搜索公共来源。用户已有的收藏本就体现了其审美。如果用户自有素材库中有匹配的收藏，却从公共素材库开始搜索，则属于

gather-own-library-first

。如果用户尚未连接任何素材来源，应停止操作并逐一列出可选来源：Are.na、Cosmos、Pinterest、Mobbin 和 Pond。如果提示词中遗漏了其中任何一个名称，则属于

gather-list-the-sources

。访问各来源的方式见 sources.md。

4. Go wide

4. 扩大来源范围

Pull from at least three sources. Pattern libraries show flows and screens. Boards and saves show taste: type, colour, photography and mood. A board drawn from one app is

gather-go-wide

Gather the number asked for. When the user asks for more, return new references and leave out those already shown. Repeats under "50 more" is

gather-enough-to-choose

至少从三个来源收集素材。模式库展示操作流程和界面；收藏板与收藏内容体现审美偏好：字体、色彩、摄影和氛围。如果一个看板中的素材全部来自同一个应用，则属于

gather-go-wide

。

按照用户指定的数量收集。用户要求更多时，应返回新的参考素材，并排除已经展示过的内容。在“再给 50 个”的要求下重复返回已有内容，属于

gather-enough-to-choose

。

5. Note the part and the link

5. 注明借鉴部分和来源链接

Each reference gets one line naming the part to take, such as "the top bar" or "the empty state". A reference with no note is

gather-name-the-part

. Each one keeps its source link, so the user can open the original. An image with no link is

gather-link-every-reference

每条参考素材用一行注明要借鉴的部分，例如“顶部栏”或“空状态”。未作说明的参考素材属于

gather-name-the-part

。每条素材都应保留来源链接，方便用户打开原始页面。没有链接的图片属于

gather-link-every-reference

。

6. Build one board and open it

6. 构建一个看板并打开

Copy board.html to

.gather/<brief>/index.html

, an ignored folder and never the source tree. Write

board.js

beside it in the shape its header comment shows, with images in

img/

, then open it. Links pasted in chat instead of a board is

gather-one-board

The board's look ships with the skill, so write data only. A page with its own markup or styles is

gather-shipped-board

Name each group in two or three words of Title Case, such as "Agent Activity", and put the detail in its note. A group named like a sentence is

gather-short-group-names

将 board.html 复制到

.gather/<brief>/index.html

。该目录应被版本控制忽略，且绝不能位于源代码目录树中。按照

board.js

头部注释所示的结构编写

board.js

，将图片放在

img/

中，然后打开它。在聊天中粘贴链接而未创建看板，属于

gather-one-board

。

看板的视觉样式随 skill 一同提供，因此只应写入数据。自行编写页面标记或样式的看板页面，属于

gather-shipped-board

。

每个分组使用 2 至 3 个单词的 Title Case 名称，例如“Agent Activity”，并把详细信息放在其备注中。名称像完整句子的分组，属于

gather-short-group-names

。

7. Save what the user keeps

7. 保存用户选中的内容

The user marks picks with Keep on the board and pastes them back with Copy Picks. When the user asks to save the picks, send them where they say: their library, a channel or a board. Read the destination's naming first and match it. A new channel named "FW 26 🔥" beside

fashion / inspiration / 2026 / fall winter

gather-match-the-naming

Check for each item before adding it. A second copy of a saved item is

gather-no-duplicates

. When a source needs a login or a CAPTCHA, stop and say which one. Working around a login is

gather-ask-at-login

用户会在看板上用 Keep 标记入选项，再用 Copy Picks 将这些内容粘贴回来。当用户要求保存入选项时，将其发送到用户指定的位置：其素材库、频道或看板。先读取目标位置的命名方式，并与之保持一致。在

fashion / inspiration / 2026 / fall winter

旁边新建名为“FW 26 🔥”的频道，属于

gather-match-the-naming

。

添加每项内容前，先检查是否已存在。已保存的内容再次添加，属于

gather-no-duplicates

。当某个来源要求登录或处理 CAPTCHA 时，应停止操作并明确指出是哪一个来源。绕过登录属于

gather-ask-at-login

。

The pair

成对规则

Every check is a pair. The broken line sits beside the line that replaces it.

Rule	Broken	Replacement
`gather-name-the-brief`	"Searching settings pages"	"Desktop settings page, looking for grouping and density"
`gather-same-platform`	iOS screens for a desktop app	`platform: "web"` and desktop apps
`gather-start-with-given`	A pattern-library search while the user's tabs are open	The open tabs read first
`gather-own-library-first`	A public library searched first	The user's library searched first, then wider
`gather-list-the-sources`	"Connect your accounts, or download Pond"	Are.na, Cosmos, Pinterest, Mobbin and Pond, each named
`gather-go-wide`	Twenty screens from one app	Saves, boards and a pattern library
`gather-enough-to-choose`	"50 more" returns the first 20 again	50 new references, earlier ids excluded
`gather-name-the-part`	A screenshot with no note	"Take the grouped list, not the colours"
`gather-link-every-reference`	An image with no source	The image linked to its original
`gather-one-board`	Twenty links pasted in chat	`.gather/settings/index.html` opened, grouped by idea
`gather-shipped-board`	A board page written from scratch	`board.html` copied, only `board.js` written
`gather-short-group-names`	"Activity: thinking, tool calls and steps"	"Agent Activity"
`gather-match-the-naming`	A new channel named "FW 26 🔥"	`fashion / inspiration / 2026 / fall winter`
`gather-no-duplicates`	The same pin added twice	Existing items checked and skipped
`gather-ask-at-login`	A login worked around	"Pinterest needs you to sign in"

每项检查都是一对：错误示例与替代方案并列显示。

规则	错误示例	替代方案
gather-name-the-brief	“正在搜索设置页面”	“桌面端设置页面，关注分组和信息密度”
gather-same-platform	为桌面端应用使用 iOS 界面	`platform: "web"` 和桌面端应用
gather-start-with-given	用户标签页已打开时却去搜索模式库	先阅读已打开的标签页
gather-own-library-first	先搜索公共素材库	先搜索用户自有素材库，再扩大搜索范围
gather-list-the-sources	“连接你的账户，或下载 Pond”	逐一列出 Are.na、Cosmos、Pinterest、Mobbin 和 Pond
gather-go-wide	来自同一个应用的 20 个界面	收藏内容、收藏板和模式库
gather-enough-to-choose	“再给 50 个”却再次返回最初的 20 个	50 条新参考素材，并排除之前的 id
gather-name-the-part	没有说明借鉴部分的截图	“采用分组列表，而不是配色”
gather-link-every-reference	没有来源链接的图片	图片链接到原始页面
gather-one-board	在聊天中粘贴 20 个链接	打开 `.gather/settings/index.html` ，并按思路归类
gather-shipped-board	从零编写看板页面	复制 `board.html` ，仅编写 `board.js`
gather-short-group-names	“活动：思考、工具调用和步骤”	“Agent Activity”
gather-match-the-naming	新建名为“FW 26 🔥”的频道	`fashion / inspiration / 2026 / fall winter`
gather-no-duplicates	同一个 Pin 被添加两次	检查已有项目并跳过
gather-ask-at-login	绕过登录	“Pinterest 需要你登录”

Reporting

报告

Severity.

HIGH

is a whole look copied when one part was asked for, or items saved twice or under the wrong name.

MEDIUM

is the wrong platform, one source only, a board with no links, a hand-written board or a public search that skipped the ask.

LOW

is a reference with no note on what to take, or a long group name.

Format. One finding per root cause, citing the request when no file applies:

file:line - [rule-id] what is wrong
request 2 - [rule-id] what is wrong

Then a

Rule | Count | Severity

summary.

Block

when any

HIGH

remains,

Approve

otherwise. Mark every source you could not reach as

Not verified

严重程度。 在用户只要求借鉴某个部分时却照搬整套视觉，或内容被重复保存、以错误名称保存，属于

HIGH

。平台错误、仅使用一个来源、看板没有链接、手写看板，或未先询问便进行公共搜索，属于

MEDIUM

。参考素材未注明可借鉴部分，或分组名称过长，属于

LOW

。

格式。 每个根本原因只报告一项问题；没有对应文件时，引用用户请求：

file:line - [rule-id] 问题描述
request 2 - [rule-id] 问题描述

随后提供

Rule | Count | Severity

汇总。只要仍存在任何

HIGH

，结果即为

Block

；否则为

Approve

。将每个无法访问的来源标记为

Not verified

。