start

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Start a Tailr review session

启动Tailr评审会话

The user invoked this with: $ARGUMENTS

Carry this out now. Do not summarize it back or ask whether to proceed.

用户通过以下内容调用此功能：$ARGUMENTS

请立即执行。不要复述总结，也不要询问是否继续。

1. Find the dev server

1. 查找开发服务器

$ARGUMENTS

names a URL, use it. Otherwise work out where this project's dev server runs — check

package.json

scripts, the framework's default port, or whatever is already listening — and start it if it is not up. Ask only if you genuinely cannot determine it.

如果

$ARGUMENTS

指定了URL，则直接使用该URL。否则请找出本项目开发服务器的运行地址——检查

package.json

中的脚本、框架的默认端口，或任何正在监听的服务——如果服务器未启动则将其启动。仅当你确实无法确定地址时再询问用户。

2. Start Tailr against it

2. 针对该服务器启动Tailr

As a long-running background process. It has to stay up, so do not block your turn waiting on it:

npx -y @gcrft123/tailr --target <dev server url>

It proxies the app on its own port (usually 4100) and injects its overlay. Nothing in the project's source is modified, and hot reload keeps working.

If it reports the port is taken by an existing session, that session is already serving — use the URL it names rather than starting a second one.

以长期运行的后台进程方式启动。它需要持续运行，因此不要阻塞你的流程来等待它：

npx -y @gcrft123/tailr --target <dev server url>

它会在自己的端口（通常是4100）上代理应用，并注入其覆盖层。项目源码不会被修改，热重载功能也可正常使用。

如果它提示端口已被现有会话占用，说明该会话已经在运行中——请使用它给出的URL，不要重复启动新会话。

3. Hand over the URL and start watching

3. 提供URL并开始监听

In the same message, do both:

Tell the reviewer the review URL Tailr printed, and that they should use it instead of the original dev server port. Tell them to hold their marking key — Alt, unless they have set another with
```
/tailr:config
```
— and click an element to comment, right-click to mark it for removal, double-click text to edit it, and Shift-click to mark a spot — then press Send.
Call the
```
tailr_wait
```
MCP tool, or run
```
npx -y @gcrft123/tailr wait
```
as a background process.

wait

stays quiet until Send is pressed and then returns — that return is how you find out a batch has arrived, so the reviewer never has to tell you.

在同一条消息中完成以下两项操作：

告知评审者Tailr输出的评审URL，说明他们应该使用该URL而非原始的开发服务器端口。告诉他们按住标记键——Alt键，除非他们通过
```
/tailr:config
```
设置了其他按键——点击元素可添加评论，右键点击可标记删除，双击文本可编辑，Shift+点击可标记位置——然后按下发送键。
调用
```
tailr_wait
```
MCP 工具，或者以后台进程方式运行
```
npx -y @gcrft123/tailr wait
```
。

wait

命令会保持静默，直到按下发送键后才会返回——通过该返回值你可以得知有一批标记已到达，因此评审者无需专门告知你。

4. Then follow the review skill

4. 随后遵循评审技能规范

From there the loop is

wait

→

pull

→

progress

per mark →

done

fail

. The

review

skill in this plugin carries the full rules; follow it for the rest of the session.

此后的流程为循环执行

wait

→

pull

→ 逐个标记执行

progress

→

done

或

fail

。本插件中的

review

技能包含完整规则；会话剩余部分请遵循该规则执行。