marketplace-builder

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Marketplace Builder

市场构建工具

A comprehensive guide to creating Claude Code marketplaces and plugins for distributing commands, agents, skills, hooks, and MCP servers.

一份关于创建Claude Code市场与插件的综合指南，用于分发命令、Agent、Skill、钩子及MCP服务器。

Quick Reference

快速参考

Marketplace vs Plugin Distinction

市场与插件的区别

Critical concept: These are NOT the same thing.

Concept	What It Is	Analogy
Marketplace	JSON catalog listing where plugins live	Library catalog
Plugin	Packaged collection of components	Book
Components	Commands, agents, skills, hooks, MCP servers	Chapters

Relationship: One marketplace → many plugins → many components per plugin

Key insight: Marketplaces don't HOST plugins. They INDEX them. Plugins can live anywhere (GitHub, GitLab, private git, local paths).

核心概念：二者并非同一事物。

概念	定义	类比
Marketplace	存放插件的JSON目录清单	图书馆目录
Plugin	打包的组件集合	书籍
Components	命令、Agent、Skill、钩子、MCP服务器	章节

关系：一个市场 → 多个插件 → 每个插件包含多个组件

核心要点：市场并不托管插件，而是为插件建立索引。插件可存储在任意位置（GitHub、GitLab、私有Git仓库、本地路径）。

JSON Schema Quick Reference

JSON Schema快速参考

Minimal marketplace.json:

json

{
  "name": "marketplace-name",
  "owner": {"name": "Owner Name"},
  "plugins": [
    {
      "name": "plugin-name",
      "source": "./path-to-plugin",
      "description": "What this plugin does",
      "version": "1.0.0"
    }
  ]
}

Minimal plugin.json (inside

.claude-plugin/

json

{
  "name": "plugin-name",
  "description": "What this plugin does",
  "version": "1.0.0"
}

Team settings.json (inside

.claude/

json

{
  "extraKnownMarketplaces": {
    "marketplace-name": {
      "source": {"source": "github", "repo": "owner/repo"}
    }
  },
  "enabledPlugins": {
    "plugin-name@marketplace-name": true
  }
}

最简marketplace.json:

json

{
  "name": "marketplace-name",
  "owner": {"name": "Owner Name"},
  "plugins": [
    {
      "name": "plugin-name",
      "source": "./path-to-plugin",
      "description": "What this plugin does",
      "version": "1.0.0"
    }
  ]
}

最简plugin.json（位于

.claude-plugin/

目录下）:

json

{
  "name": "plugin-name",
  "description": "What this plugin does",
  "version": "1.0.0"
}

团队settings.json（位于

.claude/

目录下）:

json

{
  "extraKnownMarketplaces": {
    "marketplace-name": {
      "source": {"source": "github", "repo": "owner/repo"}
    }
  },
  "enabledPlugins": {
    "plugin-name@marketplace-name": true
  }
}

Source Types

源类型

Type	Syntax	Best For
GitHub	`{"source": "github", "repo": "owner/repo"}`	Public plugins
Git URL	`{"source": "git", "url": "https://..."}`	Private/GitLab
Directory	`{"source": "directory", "path": "./path"}`	Monorepo
Relative	`"./path"`	Shorthand for directory

类型	语法	最佳适用场景
GitHub	`{"source": "github", "repo": "owner/repo"}`	公共插件
Git URL	`{"source": "git", "url": "https://..."}`	私有仓库/GitLab
Directory	`{"source": "directory", "path": "./path"}`	单仓多插件（Monorepo）
Relative	`"./path"`	目录的简写形式

Command Reference

命令参考

bash

undefined

bash

undefined

Add a marketplace

添加市场

/plugin marketplace add owner/repo /plugin marketplace add https://gitlab.com/org/repo.git /plugin marketplace add ./local-marketplace

List marketplaces

列出所有市场

/plugin marketplace list

Update marketplace catalog

更新市场目录

/plugin marketplace update marketplace-name

Browse and install plugins

浏览并安装插件

/plugin # Interactive browser /plugin install plugin-name@marketplace # Direct install

/plugin # 交互式浏览器 /plugin install plugin-name@marketplace # 直接安装

Manage plugins

管理插件

/plugin enable plugin@marketplace /plugin disable plugin@marketplace /plugin uninstall plugin@marketplace

Validate structure

验证结构

claude plugin validate .

---

claude plugin validate .

---

6-Phase Workflow

六阶段工作流程

Phase 1: Requirements Gathering

阶段1：需求收集

Use AskUserQuestion to understand the user's needs:

What are you distributing?
- Commands (slash commands)
- Agents (subagents)
- Skills (model-invoked capabilities)
- Hooks (event handlers)
- MCP servers (external tools)
- Mix of the above
How many plugins?
- Single plugin
- Multiple related plugins
- Large plugin collection
Who is the audience?
- Personal use (just me)
- Team (colleagues via git)
- Organization (company-wide)
- Public community
What hosting?
- GitHub (public or private)
- GitLab or other git service
- Self-hosted git
- Local development only

Document the answers before proceeding.

使用AskUserQuestion工具了解用户需求:

你要分发的内容是什么？
- 命令（斜杠命令）
- Agent（子代理）
- Skill（模型调用能力）
- 钩子（事件处理器）
- MCP服务器（外部工具）
- 以上内容的混合
需要多少个插件？
- 单个插件
- 多个相关插件
- 大量插件集合
目标受众是谁？
- 个人使用（仅自己）
- 团队使用（同事通过Git共享）
- 企业使用（全公司范围）
- 公共社区
使用何种托管方式？
- GitHub（公开或私有）
- GitLab或其他Git服务
- 自托管Git仓库
- 仅本地开发使用

在继续下一步前记录答案。

Phase 2: Architecture Decision

阶段2：架构决策

Based on requirements, recommend one of these patterns:

根据需求，推荐以下模式之一:

Pattern A: Basic Marketplace (Single Plugin)

模式A：基础市场（单插件）

Use when: One plugin, simple distribution

my-marketplace/
├── .claude-plugin/
│   ├── plugin.json
│   └── marketplace.json
├── commands/
└── agents/

适用场景：单个插件，简单分发

my-marketplace/
├── .claude-plugin/
│   ├── plugin.json
│   └── marketplace.json
├── commands/
└── agents/

Pattern B: Monorepo (Multiple Plugins, One Repo)

模式B：单仓多插件（Monorepo）

Use when: Related plugins, unified versioning, team ownership

company-plugins/
├── .claude-plugin/
│   └── marketplace.json
├── plugins/
│   ├── formatter/
│   │   ├── .claude-plugin/plugin.json
│   │   └── commands/
│   ├── linter/
│   │   ├── .claude-plugin/plugin.json
│   │   └── commands/
│   └── tester/
│       ├── .claude-plugin/plugin.json
│       └── agents/

适用场景：多个相关插件，统一版本控制，团队所有

company-plugins/
├── .claude-plugin/
│   └── marketplace.json
├── plugins/
│   ├── formatter/
│   │   ├── .claude-plugin/plugin.json
│   │   └── commands/
│   ├── linter/
│   │   ├── .claude-plugin/plugin.json
│   │   └── commands/
│   └── tester/
│       ├── .claude-plugin/plugin.json
│       └── agents/

Pattern C: Multi-Repo (Plugins in Separate Repos)

模式C：多仓分布（插件存于独立仓库）

Use when: Independent plugins, different owners, community collection

undefined

适用场景：独立插件，不同所有者，社区集合

undefined

Marketplace repo

市场仓库

my-marketplace/ └── .claude-plugin/ └── marketplace.json # Points to other repos

my-marketplace/ └── .claude-plugin/ └── marketplace.json # 指向其他仓库

Plugin repos (separate)

独立的插件仓库

tool-a/ ├── .claude-plugin/plugin.json └── commands/

tool-b/ ├── .claude-plugin/plugin.json └── agents/

undefined

tool-a/ ├── .claude-plugin/plugin.json └── commands/

tool-b/ ├── .claude-plugin/plugin.json └── agents/

undefined

Pattern D: Enterprise (Hybrid Private + Public)

模式D：企业级（私有+公有混合）

Use when: Mix of internal and external tools, strict access control

json

{
  "plugins": [
    {"name": "internal-tool", "source": {"source": "git", "url": "https://git.corp/..."}},
    {"name": "community-tool", "source": {"source": "github", "repo": "public/tool"}}
  ]
}

Decision tree:

Single plugin? → Pattern A
Multiple plugins, same team? → Pattern B
Plugins from different sources? → Pattern C
Enterprise with private + public? → Pattern D

适用场景：内部与外部工具混合，严格访问控制

json

{
  "plugins": [
    {"name": "internal-tool", "source": {"source": "git", "url": "https://git.corp/..."}},
    {"name": "community-tool", "source": {"source": "github", "repo": "public/tool"}}
  ]
}

决策树:

单个插件？ → 模式A
多个插件，同一团队？ → 模式B
插件来自不同源？ → 模式C
企业级私有+公有混合？ → 模式D

Phase 3: Plugin Creation

阶段3：插件创建

For each plugin, create this structure:

plugin-name/
├── .claude-plugin/
│   └── plugin.json         # Required: plugin manifest
├── commands/               # Optional: slash commands
│   └── my-command.md
├── agents/                 # Optional: subagents
│   └── my-agent.md
├── skills/                 # Optional: skills
│   └── my-skill/
│       └── SKILL.md
├── hooks/                  # Optional: event handlers
│   └── hooks.json
└── .mcp.json              # Optional: MCP servers

Write plugin.json:

json

{
  "name": "plugin-name",
  "description": "Clear description of what this plugin provides",
  "version": "1.0.0",
  "author": {
    "name": "Author Name",
    "email": "author@example.com"
  },
  "homepage": "https://docs.example.com",
  "repository": "https://github.com/owner/repo",
  "license": "MIT"
}

Naming conventions:

Plugin name:
```
kebab-case
```
(e.g.,
```
code-formatter
```
)
Version: Semantic versioning
```
MAJOR.MINOR.PATCH
```
Commands:
```
verb-noun.md
```
(e.g.,
```
format-code.md
```
)
Agents:
```
role-name.md
```
(e.g.,
```
code-reviewer.md
```
)

每个插件需创建如下结构:

plugin-name/
├── .claude-plugin/
│   └── plugin.json         # 必填：插件清单
├── commands/               # 可选：斜杠命令
│   └── my-command.md
├── agents/                 # 可选：子代理
│   └── my-agent.md
├── skills/                 # 可选：Skill
│   └── my-skill/
│       └── SKILL.md
├── hooks/                  # 可选：事件处理器
│   └── hooks.json
└── .mcp.json              # 可选：MCP服务器

编写plugin.json:

json

{
  "name": "plugin-name",
  "description": "Clear description of what this plugin provides",
  "version": "1.0.0",
  "author": {
    "name": "Author Name",
    "email": "author@example.com"
  },
  "homepage": "https://docs.example.com",
  "repository": "https://github.com/owner/repo",
  "license": "MIT"
}

命名规范:

插件名称：
```
kebab-case
```
（例如：
```
code-formatter
```
）
版本：语义化版本
```
MAJOR.MINOR.PATCH
```
命令：
```
verb-noun.md
```
（例如：
```
format-code.md
```
）
Agent：
```
role-name.md
```
（例如：
```
code-reviewer.md
```
）

Phase 4: Marketplace Creation

阶段4：市场创建

Create

.claude-plugin/marketplace.json

For monorepo (plugins in same repo):

json

{
  "name": "company-tools",
  "owner": {
    "name": "Company Name",
    "email": "team@company.com"
  },
  "metadata": {
    "description": "Company development tools",
    "version": "1.0.0",
    "pluginRoot": "./plugins"
  },
  "plugins": [
    {
      "name": "formatter",
      "source": "./plugins/formatter",
      "description": "Code formatting tools",
      "version": "1.0.0"
    },
    {
      "name": "linter",
      "source": "./plugins/linter",
      "description": "Code linting tools",
      "version": "1.0.0"
    }
  ]
}

For multi-repo (plugins in separate repos):

json

{
  "name": "community-collection",
  "owner": {
    "name": "Community",
    "email": "maintainers@example.com"
  },
  "plugins": [
    {
      "name": "tool-a",
      "source": {
        "source": "github",
        "repo": "community/tool-a"
      },
      "description": "Tool A description",
      "version": "2.1.0"
    },
    {
      "name": "tool-b",
      "source": {
        "source": "github",
        "repo": "community/tool-b"
      },
      "description": "Tool B description",
      "version": "1.3.0"
    }
  ]
}

创建

.claude-plugin/marketplace.json

单仓多插件场景（插件存于同一仓库）:

json

{
  "name": "company-tools",
  "owner": {
    "name": "Company Name",
    "email": "team@company.com"
  },
  "metadata": {
    "description": "Company development tools",
    "version": "1.0.0",
    "pluginRoot": "./plugins"
  },
  "plugins": [
    {
      "name": "formatter",
      "source": "./plugins/formatter",
      "description": "Code formatting tools",
      "version": "1.0.0"
    },
    {
      "name": "linter",
      "source": "./plugins/linter",
      "description": "Code linting tools",
      "version": "1.0.0"
    }
  ]
}

多仓分布场景（插件存于独立仓库）:

json

{
  "name": "community-collection",
  "owner": {
    "name": "Community",
    "email": "maintainers@example.com"
  },
  "plugins": [
    {
      "name": "tool-a",
      "source": {
        "source": "github",
        "repo": "community/tool-a"
      },
      "description": "Tool A description",
      "version": "2.1.0"
    },
    {
      "name": "tool-b",
      "source": {
        "source": "github",
        "repo": "community/tool-b"
      },
      "description": "Tool B description",
      "version": "1.3.0"
    }
  ]
}

Phase 5: Distribution Setup

阶段5：分发设置

For Personal Use

个人使用场景

No additional setup. Add marketplace locally:

bash

/plugin marketplace add ./path-to-marketplace

无需额外设置。本地添加市场:

bash

/plugin marketplace add ./path-to-marketplace

For Team Distribution

团队分发场景

Add to project's

.claude/settings.json

json

{
  "extraKnownMarketplaces": {
    "team-tools": {
      "source": {
        "source": "github",
        "repo": "company/claude-plugins"
      }
    }
  },
  "enabledPlugins": {
    "formatter@team-tools": true,
    "linter@team-tools": true
  }
}

How it works:

Team member clones project
Claude Code reads
```
.claude/settings.json
```
Prompts to trust configured marketplaces
Prompts to install enabled plugins
New team members get correct setup automatically

添加到项目的

.claude/settings.json

json

{
  "extraKnownMarketplaces": {
    "team-tools": {
      "source": {
        "source": "github",
        "repo": "company/claude-plugins"
      }
    }
  },
  "enabledPlugins": {
    "formatter@team-tools": true,
    "linter@team-tools": true
  }
}

工作原理:

团队成员克隆项目
Claude Code读取
```
.claude/settings.json
```
提示用户信任已配置的市场
提示用户安装已启用的插件
新团队成员自动获得正确的配置

For Public Distribution

公开发布场景

Push marketplace repo to GitHub

Document installation in README:

markdown

## Installation

Add the marketplace:
```bash
/plugin marketplace add owner/repo

Install plugins:

bash

/plugin install formatter@owner-tools

undefined

将市场仓库推送到GitHub

在README中记录安装步骤:

markdown

## 安装

添加市场:
```bash
/plugin marketplace add owner/repo

安装插件:

bash

/plugin install formatter@owner-tools

undefined

For Enterprise

企业级场景

Set up private git access (SSH keys or tokens)
Create internal marketplace with git URL sources
Configure
```
.claude/settings.json
```
in project templates
Document for IT/security review

配置私有Git访问（SSH密钥或令牌）
创建包含Git URL源的内部市场
在项目模板中配置
```
.claude/settings.json
```
编写文档供IT/安全团队审核

Phase 6: Validation and Testing

阶段6：验证与测试

Step 1: Validate JSON Syntax

步骤1：验证JSON语法

bash

undefined

bash

undefined

Validate marketplace structure

验证市场结构

claude plugin validate .

Manual JSON validation

手动验证JSON

python3 -c "import json; json.load(open('.claude-plugin/marketplace.json'))" python3 -c "import json; json.load(open('.claude-plugin/plugin.json'))"

undefined

python3 -c "import json; json.load(open('.claude-plugin/marketplace.json'))" python3 -c "import json; json.load(open('.claude-plugin/plugin.json'))"

undefined

Step 2: Test Marketplace Addition

步骤2：测试市场添加

bash

undefined

bash

undefined

Add marketplace locally

本地添加市场

/plugin marketplace add ./path-to-marketplace

Verify it appears

验证市场已添加

/plugin marketplace list

undefined

/plugin marketplace list

undefined

Step 3: Test Plugin Installation

步骤3：测试插件安装

bash

undefined

bash

undefined

Browse available plugins

浏览可用插件

/plugin

Install a plugin

安装插件

/plugin install plugin-name@marketplace-name

Verify components work

验证组件可用

/help # Check commands appear

undefined

/help # 检查命令是否显示

undefined

Step 4: Test Team Flow (if applicable)

步骤4：测试团队流程（如适用）

Clone project with settings.json to new location
Trust folder when prompted
Verify marketplaces and plugins install correctly

将包含settings.json的项目克隆到新位置
当提示时信任文件夹
验证市场和插件是否正确安装

Step 5: Verify All Components

步骤5：验证所有组件

Commands: Run
```
/command-name
```
to test
Agents: Check
```
/agents
```
or try invoking via Task
Skills: Use trigger terms to activate
Hooks: Trigger events to test
MCP servers: Check MCP tool availability

命令：运行
```
/command-name
```
进行测试
Agent：查看
```
/agents
```
或通过任务调用测试
Skill：使用触发词激活测试
钩子：触发事件进行测试
MCP服务器：检查MCP工具是否可用

Architecture Patterns

架构模式

Monorepo Pattern

单仓多插件模式

Structure:

company-plugins/
├── .claude-plugin/
│   └── marketplace.json
├── plugins/
│   ├── plugin-a/
│   ├── plugin-b/
│   └── plugin-c/
└── README.md

Pros:

Single repo to manage
Unified versioning
Easy cross-plugin changes
Simpler CI/CD

Cons:

All plugins share access control
Larger repo size
All-or-nothing updates

Best for: Team tools, related plugins, unified ownership

结构:

company-plugins/
├── .claude-plugin/
│   └── marketplace.json
├── plugins/
│   ├── plugin-a/
│   ├── plugin-b/
│   └── plugin-c/
└── README.md

优点:

仅需管理单个仓库
统一版本控制
跨插件修改更便捷
CI/CD更简单

缺点:

所有插件共享访问权限
仓库体积更大
更新需全量进行

最佳适用场景：团队工具、相关插件、统一所有权

Multi-Repo Pattern

多仓分布模式

Structure:

undefined

结构:

undefined

Marketplace repo

市场仓库

tools-marketplace/ └── .claude-plugin/marketplace.json

Separate plugin repos

独立的插件仓库

plugin-a/ # github.com/org/plugin-a plugin-b/ # github.com/org/plugin-b plugin-c/ # github.com/org/plugin-c


**Pros**:
- Independent versioning
- Separate access control
- Distributed ownership
- Smaller repos

**Cons**:
- More repos to manage
- Version coordination needed
- More complex CI/CD

**Best for**: Community collections, mixed ownership, independent plugins

---

plugin-a/ # github.com/org/plugin-a plugin-b/ # github.com/org/plugin-b plugin-c/ # github.com/org/plugin-c


**优点**:
- 独立版本控制
- 单独的访问权限控制
- 分布式所有权
- 仓库体积更小

**缺点**:
- 需要管理更多仓库
- 版本协调难度大
- CI/CD更复杂

**最佳适用场景**：社区集合、混合所有权、独立插件

---

Hybrid Pattern

混合模式

Structure:

json

{
  "plugins": [
    {"name": "core", "source": "./plugins/core"},
    {"name": "community", "source": {"source": "github", "repo": "community/tool"}},
    {"name": "internal", "source": {"source": "git", "url": "https://git.corp/..."}}
  ]
}

Pros:

Flexibility to mix sources
Can include community plugins
Supports private + public

Cons:

More complex to maintain
Mixed trust levels
Varied update cycles

Best for: Enterprise, mature ecosystems, gradual migration

结构:

json

{
  "plugins": [
    {"name": "core", "source": "./plugins/core"},
    {"name": "community", "source": {"source": "github", "repo": "community/tool"}},
    {"name": "internal", "source": {"source": "git", "url": "https://git.corp/..."}}
  ]
}

优点:

灵活混合多种源
可包含社区插件
支持私有+公有混合

缺点:

维护复杂度更高
信任级别混合
更新周期不一致

最佳适用场景：企业级、成熟生态系统、渐进式迁移

Common Pitfalls

常见误区

1. Confusing Marketplace with Plugin

1. 混淆市场与插件

Wrong: Thinking marketplace.json IS the plugin Right: marketplace.json POINTS TO plugins

marketplace.json is a catalog. The actual plugin code lives in separate directories or repos.

错误做法：认为marketplace.json就是插件 正确理解：marketplace.json指向插件

marketplace.json是一个目录清单，实际的插件代码存于独立目录或仓库中。

2. Wrong Source Type

2. 源类型使用错误

Wrong: Using GitHub shorthand for private repos

json

{"source": "github", "repo": "private-org/private-repo"}  // May fail

Right: Use git URL for private repos

json

{"source": "git", "url": "git@github.com:private-org/private-repo.git"}

错误做法：对私有仓库使用GitHub简写形式

json

{"source": "github", "repo": "private-org/private-repo"}  # 可能失败

正确做法：对私有仓库使用Git URL

json

{"source": "git", "url": "git@github.com:private-org/private-repo.git"}

3. Missing Required Fields

3. 缺少必填字段

marketplace.json required:

```
name
```
```
owner.name
```
```
plugins
```
array

plugin.json required:

```
name
```
```
description
```
```
version
```

marketplace.json必填字段:

```
name
```
```
owner.name
```
```
plugins
```
数组

plugin.json必填字段:

```
name
```
```
description
```
```
version
```

4. Path Errors

4. 路径错误

Wrong: Relative paths from wrong directory

json

{"source": "../plugins/tool"}  // Relative to what?

Right: Paths relative to marketplace.json location

json

{"source": "./plugins/tool"}  // Relative to .claude-plugin/

错误做法：从错误目录使用相对路径

json

{"source": "../plugins/tool"}  # 相对哪个目录？

正确做法：相对marketplace.json所在位置的路径

json

{"source": "./plugins/tool"}  # 相对.claude-plugin/目录

5. Version Mismatch

5. 版本不匹配

Keep versions in sync:

```
plugin.json
```
version
```
marketplace.json
```
plugin entry version

When you update a plugin, update both files.

保持版本同步:

```
plugin.json
```
中的版本
```
marketplace.json
```
中插件条目的版本

更新插件时，需同时更新这两个文件。

6. Forgetting Validation

6. 忘记验证

Always run before publishing:

bash

claude plugin validate .

发布前务必运行:

bash

claude plugin validate .

7. Trust Model Misunderstanding

7. 误解信任模型

Users MUST explicitly trust marketplaces. You cannot force-install plugins on team members. The settings.json only PRE-CONFIGURES - users still approve.

用户必须显式信任市场。你无法强制为团队成员安装插件。settings.json仅用于预配置，用户仍需手动批准。

When to Use This Skill

何时使用该技能

Use marketplace-builder when:

Creating a new marketplace
Publishing plugins for distribution
Setting up team-wide plugin configuration
Converting local plugins to distributable packages
Troubleshooting marketplace or plugin issues

Don't use when:

Creating individual commands (use slash-command-builder)
Creating individual agents (use agent-builder)
Creating individual skills (use skill-builder)
Just using existing plugins (use /plugin commands directly)

在以下场景使用marketplace-builder:

创建新市场
发布插件供分发
设置团队范围内的插件配置
将本地插件转换为可分发的包
排查市场或插件问题

请勿在以下场景使用:

创建单个命令（使用slash-command-builder）
创建单个Agent（使用agent-builder）
创建单个Skill（使用skill-builder）
仅使用现有插件（直接使用/plugin命令）

File Reference

文件参考

Templates

模板

```
templates/basic-marketplace.md
```
- Single plugin, simple setup
```
templates/plugin-structure.md
```
- Complete plugin creation guide
```
templates/multi-plugin.md
```
- Monorepo pattern
```
templates/multi-repo.md
```
- Distributed plugins pattern
```
templates/enterprise-marketplace.md
```
- Enterprise with team config

```
templates/basic-marketplace.md
```
- 单插件、简单配置
```
templates/plugin-structure.md
```
- 完整插件创建指南
```
templates/multi-plugin.md
```
- 单仓多插件模式
```
templates/multi-repo.md
```
- 分布式插件模式
```
templates/enterprise-marketplace.md
```
- 企业级团队配置

Examples

示例

```
examples/development-tools.md
```
- 6 dev tool plugins
```
examples/team-workflows.md
```
- 6 team workflow plugins
```
examples/specialized-domains.md
```
- 6 domain-specific plugins

```
examples/development-tools.md
```
- 6个开发工具插件
```
examples/team-workflows.md
```
- 6个团队工作流插件
```
examples/specialized-domains.md
```
- 6个领域专用插件

Reference

参考文档

```
reference/syntax-guide.md
```
- Complete JSON schemas
```
reference/best-practices.md
```
- Design principles
```
reference/troubleshooting.md
```
- Common issues and debugging

```
reference/syntax-guide.md
```
- 完整JSON Schema
```
reference/best-practices.md
```
- 设计原则
```
reference/troubleshooting.md
```
- 常见问题与调试