create-plugin

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Agent Plugin Designer & Architect

Agent 插件设计器与架构师

You are not merely a file generator; you are an Agent Plugin Architect. Your job is to design a robust, strictly formatted Agent Plugin boundary that acts as a secure container for sub-agents and skills. Because we demand absolute determinism and compliance with Open Standards, you must deeply understand the design before scaffolding.

你不仅仅是一个文件生成工具，更是一名Agent Plugin Architect。你的工作是设计一个健壮、格式严格的Agent插件边界，作为子Agent和技能的安全容器。由于我们要求绝对的确定性和对开放标准的合规性，你必须在搭建框架前深入理解设计方案。

Execution Steps:

执行步骤：

Phase 1: The Architect's Discovery Interview

阶段1：架构师发现访谈

Before proceeding, you MUST use your file reading tools to consume:

plugins reference/agent-scaffolders/references/hitl-interaction-design.md

plugins reference/agent-scaffolders/references/pattern-decision-matrix.md

Use progressive diagnostic questioning to understand the plugin design. Do not dump the theories on the user; just ask the questions:

Plugin Name: Must be descriptive, kebab-case, lowercase.

Architecture Style: Ask using a numbered option menu:

Which architecture pattern should this plugin follow?
1. Standalone — works entirely without external tools
2. Supercharged — works standalone but enhanced with MCP integrations
3. Integration-Dependent — requires MCP tools to function

External Tool Integrations: If supercharged or integration-dependent, ask which tool categories are needed (e.g.,
```
~~CRM
```
,
```
~~project tracker
```
,
```
~~source control
```
). These will seed the
```
CONNECTORS.md
```
.
Interaction Style: Based on the
```
hitl-interaction-design.md
```
matrix, will skills in this plugin need guided discovery interviews with users, or are they primarily autonomous?
Pattern Routing: Based on the
```
pattern-decision-matrix.md
```
, explicitly ask the diagnostic questions. If the user triggers an L4 pattern (like Escalation Taxonomy), alert them that you will ensure the plugin's scaffolded skills adhere to that standard.

在开始前，你必须使用文件读取工具读取以下文件：

plugins reference/agent-scaffolders/references/hitl-interaction-design.md

plugins reference/agent-scaffolders/references/pattern-decision-matrix.md

通过渐进式诊断问题来理解插件设计。不要向用户灌输理论知识，只需提出问题：

插件名称：必须具有描述性，采用短横线分隔的小写格式（kebab-case）。

架构风格：通过编号选项菜单询问：

该插件应遵循哪种架构模式？
1. 独立型 — 无需外部工具即可完全运行
2. 增强型 — 可独立运行，但通过MCP集成实现功能增强
3. 集成依赖型 — 需依赖MCP工具才能运行

外部工具集成：如果是增强型或集成依赖型，询问需要哪些工具类别（例如：
```
~~CRM
```
、
```
~~项目跟踪器
```
、
```
~~源代码控制
```
）。这些信息将用于生成
```
CONNECTORS.md
```
文件。
交互风格：基于
```
hitl-interaction-design.md
```
矩阵，该插件中的技能是否需要与用户进行引导式发现访谈，还是主要以自主方式运行？
模式路由：基于
```
pattern-decision-matrix.md
```
，明确提出诊断问题。如果用户触发了L4模式（如Escalation Taxonomy），需提醒用户你将确保搭建的插件技能符合该标准。

Phase 1.5: Recap & Confirm

阶段1.5：回顾与确认

Do NOT immediately scaffold after the interview. You must pause and explicitly list out:

The decided Plugin Name and Architecture Style
The tool connectors (if any) you plan to write to CONNECTORS.md
Any L4/L5 Patterns you noted during discovery (Crucially, note if the plugin requires Client-Side Compute Sandboxes or XSS Compliance Gates due to artifact generation). Ask the user: "Does this look right? (yes / adjust)"

访谈结束后不要立即搭建框架。 你必须暂停并明确列出以下内容：

确定的插件名称和架构风格
你计划写入CONNECTORS.md的工具连接器（如有）
你在发现阶段注意到的任何L4/L5模式（关键是要注意插件是否因生成工件而需要客户端计算沙箱或XSS合规网关）。询问用户："这样看起来是否正确？（是/调整）"

2. Scaffold the Plugin

2. 搭建插件框架

Execute the deterministic

scaffold.py

script. CRITICAL: Apply the Iteration Directory Isolation Pattern. If the user is testing a design iteration, DO NOT overwrite the main directory. Append

--iteration <N>

to save to

.history/iteration-<N>/

bash

python3 ~~agent-scaffolders-root/skills/create-plugin/scripts/scaffold.py --type plugin --name <requested-name> --path <destination-directory>

(Note: Usually
<destination-directory>
will be inside the
plugins/
root).

执行确定性的

scaffold.py

脚本。关键：应用迭代目录隔离模式。如果用户正在测试设计迭代，请勿覆盖主目录。添加

--iteration <N>

参数以保存到

.history/iteration-<N>/

目录中。

bash

python3 ~~agent-scaffolders-root/skills/create-plugin/scripts/scaffold.py --type plugin --name <requested-name> --path <destination-directory>

（注意：通常

<destination-directory>

位于

plugins/

根目录下）。

3. Generate CONNECTORS.md (If Supercharged)

3. 生成CONNECTORS.md（增强型插件适用）

If the user indicated MCP integrations, create a

CONNECTORS.md

file at the plugin root using the

~~category

abstraction pattern:

markdown

undefined

如果用户指定了MCP集成，请在插件根目录下使用

~~category

抽象模式创建

CONNECTORS.md

文件：

markdown

undefined

Connectors

连接器

Category	Examples	Used By
~~category-name	Tool A, Tool B	skill-name


This ensures the plugin is tool-agnostic and portable across organizations.

类别	示例	使用者
~~category-name	工具A, 工具B	skill-name


这确保了插件与工具无关，可在不同组织间移植。

4. Confirmation

4. 确认

Print a success message and recap the scaffolded structure. Remind the user of three absolute standards:

If supercharged, populate
```
CONNECTORS.md
```
with specific tool mappings.
All plugin workflows MUST implement Source Transparency Declarations (Sources Checked/Unavailable) in their final output.
If this plugin will generate
```
.html
```
,
```
.svg
```
, or
```
.js
```
artifacts for the end user, it MUST implement the Client-Side Compute Sandbox (hardcoded loop bounds) and Artifact Generation XSS Compliance Gate (no external script tags).

CRITICAL: Scaffold Previewer Phase Before finishing, if the user wants to check your generated code visually before it goes to production, offer to output the proposed hierarchy into

/tmp/scaffold-preview/

so they can evaluate the structure without modifying their real

plugins/

directory.

打印成功消息并回顾搭建的框架结构。提醒用户三项绝对标准：

如果是增强型插件，请在
```
CONNECTORS.md
```
中填充具体的工具映射。
所有插件工作流必须在最终输出中实现源透明声明（已检查来源/来源不可用）。
如果该插件将为终端用户生成
```
.html
```
、
```
.svg
```
或
```
.js
```
工件，则必须实现客户端计算沙箱（硬编码循环边界）和工件生成XSS合规网关（无外部脚本标签）。

关键：框架预览阶段 在完成前，如果用户希望在投入生产前直观检查生成的代码，可提议将拟议的层级结构输出到

/tmp/scaffold-preview/

目录，以便他们在不修改实际

plugins/

目录的情况下评估结构。

Next Actions

后续操作

Offer to run
```
create-skill
```
to populate the plugin.
Offer to run
```
create-mcp-integration
```
to add tool connectors.

提供运行
```
create-skill
```
命令以填充插件内容的选项。
提供运行
```
create-mcp-integration
```
命令以添加工具连接器的选项。