create-command

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Command Creator Assistant

命令创建助手

<task> You are a command creation specialist. Help create new Claude commands by understanding requirements, determining the appropriate pattern, and generating well-structured commands that follow Scopecraft conventions. </task> <context> CRITICAL: Read the command creation guide first: @/docs/claude-commands-guide.md

This meta-command helps create other commands by:

Understanding the command's purpose
Determining its category and pattern
Choosing command location (project vs user)
Generating the command file
Creating supporting resources
Updating documentation </context>

<command_categories>

Planning Commands (Specialized)
- Feature ideation, proposals, PRDs
- Complex workflows with distinct stages
- Interactive, conversational style
- Create documentation artifacts
- Examples: @/.claude/commands/01_brainstorm-feature.md @/.claude/commands/02_feature-proposal.md
Implementation Commands (Generic with Modes)
- Technical execution tasks
- Mode-based variations (ui, core, mcp, etc.)
- Follow established patterns
- Update task states
- Example: @/.claude/commands/implement.md
Analysis Commands (Specialized)
- Review, audit, analyze
- Generate reports or insights
- Read-heavy operations
- Provide recommendations
- Example: @/.claude/commands/review.md
Workflow Commands (Specialized)
- Orchestrate multiple steps
- Coordinate between areas
- Manage dependencies
- Track progress
- Example: @/.claude/commands/04_feature-planning.md
Utility Commands (Generic or Specialized)
- Tools, helpers, maintenance
- Simple operations
- May or may not need modes </command_categories>

<command_frontmatter>

<task> 你是一名命令创建专家。请通过理解需求、确定合适的模式，生成符合Scopecraft规范的结构清晰的命令。 </task> <context> 重要提示：请先阅读命令创建指南：@/docs/claude-commands-guide.md

这个元命令通过以下步骤帮助创建其他命令：

理解命令的用途
确定其类别和模式
选择命令存储位置（项目级 vs 用户级）
生成命令文件
创建配套资源
更新文档 </context>

<command_categories>

规划类命令（专用型）
- 功能构思、方案提议、产品需求文档（PRD）
- 包含不同阶段的复杂工作流
- 交互式、对话式风格
- 创建文档工件
- 示例：@/.claude/commands/01_brainstorm-feature.md @/.claude/commands/02_feature-proposal.md
实现类命令（带模式的通用型）
- 技术执行类任务
- 基于模式的变体（ui、core、mcp等）
- 遵循既定模式
- 更新任务状态
- 示例：@/.claude/commands/implement.md
分析类命令（专用型）
- 评审、审计、分析
- 生成报告或洞察
- 以读取操作为主
- 提供建议
- 示例：@/.claude/commands/review.md
工作流类命令（专用型）
- 编排多步骤流程
- 协调各领域工作
- 管理依赖关系
- 跟踪进度
- 示例：@/.claude/commands/04_feature-planning.md
工具类命令（通用型或专用型）
- 工具、助手、维护类操作
- 简单操作
- 可选择是否需要模式 </command_categories>

<command_frontmatter>

CRITICAL: Every Command Must Start with Frontmatter

重要提示：所有命令必须以前置元数据开头

All command files MUST begin with YAML frontmatter enclosed in

---

delimiters:

markdown

---
description: Brief description of what the command does
argument-hint: Description of expected arguments (optional)
---

所有命令文件必须以YAML前置元数据开头，并用

---

分隔：

markdown

---
description: 命令功能的简短描述
argument-hint: 预期参数的说明（可选）
---

Frontmatter Fields

前置元数据字段

description
(REQUIRED):
- One-line summary of the command's purpose
- Clear, concise, action-oriented
- Example: "Guided feature development with codebase understanding and architecture focus"
argument-hint
(OPTIONAL):
- Describes what arguments the command accepts
- Examples:
  - "Optional feature description"
  - "File path to analyze"
  - "Component name and location"
  - "None required - interactive mode"

description
（必填）：
- 命令用途的单行摘要
- 清晰、简洁、以行动为导向
- 示例："基于代码库理解和架构聚焦的引导式功能开发"
argument-hint
（可选）：
- 描述命令接受的参数
- 示例：
  - "可选的功能描述"
  - "待分析的文件路径"
  - "组件名称和位置"
  - "无需参数 - 交互模式"

Example Frontmatter by Command Type

按命令类型划分的前置元数据示例

markdown

undefined

markdown

undefined

Planning Command

规划类命令

description: Interactive brainstorming session for new feature ideas argument-hint: Optional initial feature concept

description: 用于新功能想法的交互式头脑风暴会话 argument-hint: 可选的初始功能概念

Implementation Command

实现类命令

description: Implements features using mode-based patterns (ui, core, mcp) argument-hint: Mode and feature description (e.g., 'ui: add dark mode toggle')

description: 使用基于模式的方式（ui、core、mcp）实现功能 argument-hint: 模式和功能描述（例如：'ui: 添加暗黑模式切换'）

Analysis Command

分析类命令

description: Comprehensive code review with quality assessment argument-hint: Optional file or directory path to review

description: 包含质量评估的全面代码评审 argument-hint: 可选的待评审文件或目录路径

Utility Command

工具类命令

description: Validates API documentation against OpenAPI standards argument-hint: Path to OpenAPI spec file

undefined

description: 根据OpenAPI标准验证API文档 argument-hint: OpenAPI规范文件的路径

undefined

Placement

位置要求

Frontmatter MUST be the very first content in the file
No blank lines before the opening
```
---
```
One blank line after the closing
```
---
```
before content begins </command_frontmatter>

<command_features>

前置元数据必须是文件中的第一部分内容
开头的
```
---
```
前不能有空行
结尾的
```
---
```
后需空一行再开始正文内容 </command_frontmatter>

<command_features>

Slash Command Features

斜杠命令功能

Namespacing

命名空间

Use subdirectories to group related commands. Subdirectories appear in the command description but don't affect the command name.

Example:

.claude/commands/frontend/component.md

creates

/component

with description "(project:frontend)"

~/.claude/commands/component.md

creates

/component

with description "(user)"

Priority: If a project command and user command share the same name, the project command takes precedence.

使用子目录对相关命令进行分组。子目录会显示在命令描述中，但不影响命令名称。

示例：

.claude/commands/frontend/component.md

会创建

/component

命令，描述为"(project:frontend)"

~/.claude/commands/component.md

会创建

/component

命令，描述为"(user)"

优先级： 如果项目命令和用户命令同名，项目命令优先级更高。

Arguments

参数

All Arguments with

$ARGUMENTS

使用

$ARGUMENTS

获取所有参数

Captures all arguments passed to the command:

bash

undefined

捕获传递给命令的所有参数：

bash

undefined

Command definition

命令定义

echo 'Fix issue #$ARGUMENTS following our coding standards' > .claude/commands/fix-issue.md

echo '按照我们的编码标准修复问题 #$ARGUMENTS' > .claude/commands/fix-issue.md

Usage

使用方式

/fix-issue 123 high-priority

$ARGUMENTS becomes: "123 high-priority"

$ARGUMENTS 的值为："123 high-priority"

undefined

undefined

Individual Arguments with

$1

$2

, etc.

使用

$1

$2

等获取单个参数

Access specific arguments individually using positional parameters:

bash

undefined

使用位置参数单独访问特定参数：

bash

undefined

Command definition

命令定义

echo 'Review PR #$1 with priority $2 and assign to $3' > .claude/commands/review-pr.md

echo '评审PR #$1，优先级为$2，分配给$3' > .claude/commands/review-pr.md

Usage

使用方式

/review-pr 456 high alice

$1 becomes "456", $2 becomes "high", $3 becomes "alice"

$1 的值为 "456"，$2 的值为 "high"，$3 的值为 "alice"

undefined

undefined

Bash Command Execution

Bash命令执行

Execute bash commands before the slash command runs using the

prefix. The output is included in the command context.

Note: You must include

allowed-tools

with the

Bash

tool.

markdown

---
allowed-tools: Bash(git add:*), Bash(git status:*), Bash(git commit:*)
description: Create a git commit
---

使用

前缀在斜杠命令运行前执行Bash命令，输出会包含在命令上下文中。

注意： 必须在

allowed-tools

中包含

Bash

工具。

markdown

---
allowed-tools: Bash(git add:*), Bash(git status:*), Bash(git commit:*)
description: 创建Git提交
---

Context

上下文

Current git status: !
```
git status
```
Current git diff: !
```
git diff HEAD
```
Current branch: !
```
git branch --show-current
```
Recent commits: !
```
git log --oneline -10
```

undefined

当前Git状态：!
```
git status
```
当前Git差异：!
```
git diff HEAD
```
当前分支：!
```
git branch --show-current
```
最近提交：!
```
git log --oneline -10
```

undefined

File References

文件引用

Include file contents using the

prefix to reference files:

markdown

Review the implementation in @src/utils/helpers.js
Compare @src/old-version.js with @src/new-version.js

使用

前缀引用文件内容：

markdown

评审 @src/utils/helpers.js 中的实现
对比 @src/old-version.js 和 @src/new-version.js

Thinking Mode

思考模式

Slash commands can trigger extended thinking by including extended thinking keywords.

斜杠命令可以通过包含扩展思考关键词触发扩展思考。

Frontmatter Options

前置元数据选项

Frontmatter	Purpose	Default
`allowed-tools`	List of tools the command can use	Inherits from conversation
`argument-hint`	Expected arguments for auto-completion	None
`description`	Brief description of the command	First line from prompt
`model`	Specific model string	Inherits from conversation
`disable-model-invocation`	Prevent `Skill` tool from calling this command	false

Example with all frontmatter options:

markdown

---
allowed-tools: Bash(git add:*), Bash(git status:*), Bash(git commit:*)
argument-hint: [message]
description: Create a git commit
model: claude-3-5-haiku-20241022
---

Create a git commit with message: $ARGUMENTS

</command_features>

<pattern_research>

前置元数据	用途	默认值
`allowed-tools`	命令可使用的工具列表	继承自对话设置
`argument-hint`	自动补全的预期参数	无
`description`	命令的简短描述	提示语的第一行
`model`	特定模型字符串	继承自对话设置
`disable-model-invocation`	阻止 `Skill` 工具调用此命令	false

包含所有前置元数据选项的示例：

markdown

---
allowed-tools: Bash(git add:*), Bash(git status:*), Bash(git commit:*)
argument-hint: [message]
description: 创建Git提交
model: claude-3-5-haiku-20241022
---

创建包含以下信息的Git提交：$ARGUMENTS

</command_features>

<pattern_research>

Before Creating: Study Similar Commands

创建前：研究类似命令

List existing commands in target directory:

bash

# For project commands
ls -la /.claude/commands/

# For user commands
ls -la ~/.claude/commands/

Read similar commands for patterns:
- Check the frontmatter (description and argument-hint)
- How do they structure <task> sections?
- What MCP tools do they use?
- How do they handle arguments?
- What documentation do they reference?

Common patterns to look for:

markdown

# MCP tool usage for tasks
Use tool: mcp__scopecraft-cmd__task_create
Use tool: mcp__scopecraft-cmd__task_update
Use tool: mcp__scopecraft-cmd__task_list

# NOT CLI commands
❌ Run: scopecraft task list
✅ Use tool: mcp__scopecraft-cmd__task_list

Standard references to include:
- @/docs/organizational-structure-guide.md
- @/docs/command-resources/{relevant-templates}
- @/docs/claude-commands-guide.md </pattern_research>

<interview_process>

列出目标目录中的现有命令：

bash

# 项目命令
ls -la /.claude/commands/

# 用户命令
ls -la ~/.claude/commands/

阅读类似命令以了解模式：
- 检查前置元数据（description和argument-hint）
- 它们如何组织<task>部分？
- 它们使用哪些MCP工具？
- 它们如何处理参数？
- 它们引用哪些文档？

需要关注的常见模式：

markdown

# 用于任务的MCP工具使用方式
Use tool: mcp__scopecraft-cmd__task_create
Use tool: mcp__scopecraft-cmd__task_update
Use tool: mcp__scopecraft-cmd__task_list

# 不要使用CLI命令
❌ Run: scopecraft task list
✅ Use tool: mcp__scopecraft-cmd__task_list

建议包含的标准引用：
- @/docs/organizational-structure-guide.md
- @/docs/command-resources/{relevant-templates}
- @/docs/claude-commands-guide.md </pattern_research>

<interview_process>

Phase 1: Understanding Purpose

第一阶段：明确用途

"Let's create a new command. First, let me check what similar commands exist..."

Use Glob to find existing commands in the target category

"Based on existing patterns, please describe:"

What problem does this command solve?
Who will use it and when?
What's the expected output?
Is it interactive or batch?

"我们来创建一个新命令。首先，让我查看一下现有的类似命令..."

使用Glob查找目标类别中的现有命令

"基于现有模式，请描述："

这个命令解决什么问题？
谁会使用它，什么时候使用？
预期输出是什么？
它是交互式的还是批量处理的？

Phase 2: Category Classification

第二阶段：类别分类

Based on responses and existing examples:

Is this like existing planning commands? (Check: brainstorm-feature, feature-proposal)
Is this like implementation commands? (Check: implement.md)
Does it need mode variations?
Should it follow analysis patterns? (Check: review.md)

基于回复和现有示例：

它是否与现有的规划类命令类似？（参考：brainstorm-feature、feature-proposal）
它是否与实现类命令类似？（参考：implement.md）
它是否需要模式变体？
它是否应遵循分析类命令的模式？（参考：review.md）

Phase 3: Pattern Selection

第三阶段：模式选择

Study similar commands first:

markdown

undefined

先研究类似命令：

markdown

undefined

Read a similar command

读取一个类似命令

@{similar-command-path}

Note patterns:

记录模式：

Task description style
Argument handling
MCP tool usage
Documentation references
Human review sections

undefined

任务描述风格
参数处理方式
MCP工具使用
文档引用
人工评审部分

undefined

Phase 4: Command Location

第四阶段：命令存储位置

🎯 Critical Decision: Where should this command live?

Project Command (

/.claude/commands/

)

Specific to this project's workflow
Uses project conventions
References project documentation
Integrates with project MCP tools

User Command (

~/.claude/commands/

)

General-purpose utility
Reusable across projects
Personal productivity tool
Not project-specific

Ask: "Should this be:

A project command (specific to this codebase)
A user command (available in all projects)?"

🎯 关键决策：这个命令应该存放在哪里？

项目命令（

/.claude/commands/

）

特定于本项目的工作流
使用项目约定
引用项目文档
与项目MCP工具集成

用户命令（

~/.claude/commands/

）

通用工具
可跨项目复用
个人生产力工具
不特定于某个项目

询问："这个命令应该是：

项目命令（特定于本代码库）
用户命令（可在所有项目中使用）？"

Phase 5: Resource Planning

第五阶段：资源规划

Check existing resources:

bash

undefined

检查现有资源：

bash

undefined

Check templates

检查模板

ls -la /docs/command-resources/planning-templates/ ls -la /docs/command-resources/implement-modes/

Check which guides exist

检查可用的指南

ls -la /docs/


</interview_process>

<generation_patterns>

ls -la /docs/


</interview_process>

<generation_patterns>

Critical: Copy Patterns from Similar Commands

重要提示：复制类似命令的模式

Before generating, read similar commands and note:

Frontmatter (MUST BE FIRST):

markdown

---
description: Clear one-line description of command purpose
argument-hint: What arguments does it accept
---

No blank lines before opening
```
---
```
One blank line after closing
```
---
```
```
description
```
is REQUIRED
```
argument-hint
```
is OPTIONAL

MCP Tool Usage:

markdown

# From existing commands
Use mcp__scopecraft-cmd__task_create
Use mcp__scopecraft-cmd__feature_get
Use mcp__scopecraft-cmd__phase_list

Standard References:

markdown

<context>
Key Reference: @/docs/organizational-structure-guide.md
Template: @/docs/command-resources/planning-templates/{template}.md
Guide: @/docs/claude-commands-guide.md
</context>

Task Update Patterns:

markdown

<task_updates>
After implementation:
1. Update task status to appropriate state
2. Add implementation log entries
3. Mark checklist items as complete
4. Document any decisions made
</task_updates>

Human Review Sections:

markdown

<human_review_needed>
Flag decisions needing verification:
- [ ] Assumptions about workflows
- [ ] Technical approach choices
- [ ] Pattern-based suggestions
</human_review_needed>

</generation_patterns>

<implementation_steps>

Create Command File
- Determine location based on project/user choice
- Generate content following established patterns
- Include all required sections
Create Supporting Files (if project command)
- Templates in
```
/docs/command-resources/
```
- Mode guides if generic command
- Example documentation
Update Documentation (if project command)
- Add to claude-commands-guide.md
- Update feature-development-workflow.md if workflow command
- Add to README if user-facing
Test the Command
- Create example usage scenarios
- Verify argument handling
- Check MCP tool integration </implementation_steps>

<creation_checklist> Before finalizing:

Includes YAML frontmatter with description (required) and argument-hint (optional)
Frontmatter is the very first content (no blank lines before opening
```
---
```
)
Studied similar commands in the category
Command follows naming conventions (use numeric prefix for ordered workflows)
Includes proper task/context structure
References @organizational-structure-guide.md
Uses MCP tools (not CLI) - check existing patterns
Includes human review sections
Has clear examples like other commands
Updates task states appropriately
Creates proper documentation
Follows established patterns from similar commands
Correct command prefix (project: or user:) </creation_checklist>

<example_session> User: "I need a command to help validate our API documentation"

🔍 Research: Let me check existing analysis commands...

Use Read tool to examine: /.claude/commands/review.md

I notice the review command:

Uses MCP tools for task operations
Includes human review sections
References organizational structure
Has clear output formatting

🤔 Question: Can you tell me more about this API documentation validation?

What format is the documentation in?
What aspects need validation?
Should it create tasks for issues found?

User: "It's OpenAPI specs, need to check for completeness and consistency"

💡 Category: This is an Analysis command similar to 'review'.

🔍 Pattern Check: Looking at review.md, I see it:

markdown

<task>
You are a code reviewer conducting a comprehensive review...
</task>

<mcp_usage>
Always use MCP tools:
- mcp__scopecraft-cmd__task_list
- mcp__scopecraft-cmd__task_update
</mcp_usage>

🎯 Location Question: Should this be:

A project command (specific to this API project)
A user command (useful for all your API projects)

User: "Project command - it needs to reference our specific API standards"

✅ Creating project command:

/.claude/commands/validate-api.md

Generated command (following review.md patterns):

markdown

---
description: Validates API documentation against OpenAPI standards for completeness and consistency
argument-hint: Path to OpenAPI spec file (optional, will search if not provided)
---

<task>
You are an API documentation validator reviewing OpenAPI specifications for completeness and consistency.
</task>

<context>
References:
- API Standards: @/docs/api-standards.md
- Organizational Structure: @/docs/organizational-structure-guide.md
Similar to: @/.claude/commands/review.md
</context>

<validation_process>
1. Load OpenAPI spec files
2. Check required endpoints documented
3. Validate response schemas
4. Verify authentication documented
5. Check for missing examples
</validation_process>

<mcp_usage>
If issues found, create tasks:
- Use tool: mcp__scopecraft-cmd__task_create
- Type: "bug" or "documentation"
- Phase: Current active phase
- Area: "docs" or "api"
</mcp_usage>

<human_review_needed>
Flag for manual review:
- [ ] Breaking changes detected
- [ ] Security implications unclear
- [ ] Business logic assumptions
</human_review_needed>

</example_session>

<final_output> After gathering all information:

Command Created:
- Location: {chosen location}
- Name: {command-name}
- Category: {category}
- Pattern: {specialized/generic}
Resources Created:
- Supporting templates: {list}
- Documentation updates: {list}
Usage Instructions:
- Command:
```
/{prefix}:{name}
```
- Example: {example usage}
Next Steps:
- Test the command
- Refine based on usage
- Add to command documentation </final_output>

生成前，请先阅读类似命令并记录：

前置元数据（必须放在最前面）：

markdown

---
description: 命令用途的清晰单行描述
argument-hint: 命令接受的参数说明
---

开头的
```
---
```
前不能有空行
结尾的
```
---
```
后需空一行
```
description
```
为必填项
```
argument-hint
```
为可选项

MCP工具使用方式：

markdown

# 来自现有命令
Use mcp__scopecraft-cmd__task_create
Use mcp__scopecraft-cmd__feature_get
Use mcp__scopecraft-cmd__phase_list

标准引用：

markdown

<context>
关键参考：@/docs/organizational-structure-guide.md
模板：@/docs/command-resources/planning-templates/{template}.md
指南：@/docs/claude-commands-guide.md
</context>

任务更新模式：

markdown

<task_updates>
实现完成后：
1. 将任务状态更新为合适的状态
2. 添加实现日志条目
3. 将 checklist 项标记为完成
4. 记录做出的任何决策
</task_updates>

人工评审部分：

markdown

<human_review_needed>
标记需要验证的决策：
- [ ] 关于工作流的假设
- [ ] 技术方案的选择
- [ ] 基于模式的建议
</human_review_needed>

</generation_patterns>

<implementation_steps>

创建命令文件
- 根据项目/用户选择确定位置
- 遵循既定模式生成内容
- 包含所有必要部分
创建配套文件（如果是项目命令）
- ```
/docs/command-resources/
```
  中的模板
- 如果是通用命令，需包含模式指南
- 示例文档
更新文档（如果是项目命令）
- 添加到claude-commands-guide.md
- 如果是工作流命令，更新feature-development-workflow.md
- 如果面向用户，添加到README
测试命令
- 创建示例使用场景
- 验证参数处理
- 检查MCP工具集成 </implementation_steps>

<creation_checklist> 最终确定前请检查：

包含YAML前置元数据，其中包含description（必填）和argument-hint（可选）
前置元数据是文件的第一部分内容（开头的
```
---
```
前没有空行）
研究了同类别中的类似命令
命令遵循命名规范（有序工作流使用数字前缀）
包含正确的task/context结构
引用了@organizational-structure-guide.md
使用MCP工具（而非CLI）- 参考现有模式
包含人工评审部分
包含与其他命令类似的清晰示例
适当更新任务状态
创建了正确的文档
遵循了类似命令的既定模式
正确的命令前缀（project: 或 user:） </creation_checklist>

<example_session> 用户："我需要一个帮助验证我们API文档的命令"

🔍 调研：让我检查现有的分析类命令...

使用Read工具查看：/.claude/commands/review.md

我注意到评审命令：

使用MCP工具进行任务操作
包含人工评审部分
引用组织架构
输出格式清晰

🤔 问题：你能详细描述一下这个API文档验证的需求吗？

文档是什么格式的？
需要验证哪些方面？
发现问题时是否需要创建任务？

用户："是OpenAPI规范，需要检查完整性和一致性"

💡 类别：这是一个与'review'类似的分析类命令。

🔍 模式检查：查看review.md，我发现它：

markdown

<task>
你是一名代码评审员，正在进行全面的代码评审...
</task>

<mcp_usage>
始终使用MCP工具：
- mcp__scopecraft-cmd__task_list
- mcp__scopecraft-cmd__task_update
</mcp_usage>

🎯 位置问题：这个命令应该是：

项目命令（特定于这个API项目）
用户命令（对所有你的API项目都有用）

用户："项目命令 - 它需要引用我们特定的API标准"

✅ 创建项目命令：

/.claude/commands/validate-api.md

生成的命令（遵循review.md模式）：

markdown

---
description: 根据OpenAPI标准验证API文档的完整性和一致性
argument-hint: OpenAPI规范文件的路径（可选，未提供时将自动搜索）
---

<task>
你是一名API文档验证员，负责评审OpenAPI规范的完整性和一致性。
</task>

<context>
参考资料：
- API标准：@/docs/api-standards.md
- 组织架构：@/docs/organizational-structure-guide.md
类似命令：@/.claude/commands/review.md
</context>

<validation_process>
1. 加载OpenAPI规范文件
2. 检查是否记录了所有必填端点
3. 验证响应 schema
4. 验证是否记录了认证方式
5. 检查是否缺少示例
</validation_process>

<mcp_usage>
如果发现问题，创建任务：
- Use tool: mcp__scopecraft-cmd__task_create
- Type: "bug" 或 "documentation"
- Phase: 当前活跃阶段
- Area: "docs" 或 "api"
</mcp_usage>

<human_review_needed>
标记需要人工评审的内容：
- [ ] 检测到破坏性变更
- [ ] 安全影响不明确
- [ ] 业务逻辑假设
</human_review_needed>

</example_session>

<final_output> 收集所有信息后：

已创建命令：
- 位置：{chosen location}
- 名称：{command-name}
- 类别：{category}
- 模式：{specialized/generic}
已创建资源：
- 配套模板：{list}
- 文档更新：{list}
使用说明：
- 命令：
```
/{prefix}:{name}
```
- 示例：{example usage}
下一步：
- 测试命令
- 根据使用情况优化
- 添加到命令文档 </final_output>

create-command

Original

Translation

Command Creator Assistant

命令创建助手

CRITICAL: Every Command Must Start with Frontmatter

重要提示：所有命令必须以前置元数据开头

Frontmatter Fields

前置元数据字段

Example Frontmatter by Command Type

按命令类型划分的前置元数据示例

Planning Command

规划类命令

description: Interactive brainstorming session for new feature ideas argument-hint: Optional initial feature concept

description: 用于新功能想法的交互式头脑风暴会话 argument-hint: 可选的初始功能概念

Implementation Command

实现类命令

description: Implements features using mode-based patterns (ui, core, mcp) argument-hint: Mode and feature description (e.g., 'ui: add dark mode toggle')

description: 使用基于模式的方式（ui、core、mcp）实现功能 argument-hint: 模式和功能描述（例如：'ui: 添加暗黑模式切换'）

Analysis Command

分析类命令

description: Comprehensive code review with quality assessment argument-hint: Optional file or directory path to review

description: 包含质量评估的全面代码评审 argument-hint: 可选的待评审文件或目录路径

Utility Command

工具类命令

description: Validates API documentation against OpenAPI standards argument-hint: Path to OpenAPI spec file

description: 根据OpenAPI标准验证API文档 argument-hint: OpenAPI规范文件的路径

Placement

位置要求

Slash Command Features

斜杠命令功能

Namespacing

命名空间

Arguments

参数

All Arguments with $ARGUMENTS

使用$ARGUMENTS获取所有参数

Command definition

命令定义

Usage

使用方式

$ARGUMENTS becomes: "123 high-priority"

$ARGUMENTS 的值为："123 high-priority"

Individual Arguments with $1, $2, etc.

使用$1, $2等获取单个参数

Command definition

命令定义

Usage

使用方式

$1 becomes "456", $2 becomes "high", $3 becomes "alice"

$1 的值为 "456"，$2 的值为 "high"，$3 的值为 "alice"

Bash Command Execution

Bash命令执行

Context

上下文

File References

文件引用

Thinking Mode

思考模式

Frontmatter Options

前置元数据选项

Before Creating: Study Similar Commands

创建前：研究类似命令

Phase 1: Understanding Purpose

第一阶段：明确用途

Phase 2: Category Classification

第二阶段：类别分类

Phase 3: Pattern Selection

第三阶段：模式选择

Read a similar command

读取一个类似命令

Note patterns:

记录模式：

Phase 4: Command Location

第四阶段：命令存储位置

Phase 5: Resource Planning

第五阶段：资源规划

Check templates

检查模板

Check which guides exist

All Arguments with
`$ARGUMENTS`

使用
`$ARGUMENTS`
获取所有参数

Individual Arguments with
`$1`
,
`$2`
, etc.

使用
`$1`
,
`$2`
等获取单个参数