create-command

Name: create-command
Author: NeoLabHQ

827installs132forks

How to install create-command?

neolabhq/context-engineering-kit/create-command

$npx -y skills add NeoLabHQ/context-engineering-kit --skill create-command

Installs into the current project.

Summary

Interactive assistant for creating new Claude commands with proper structure, patterns, and MCP tool integration

Files · 1

View on GitHub

SKILL.md

1	# Command Creator Assistant
2
3	<task>
4	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.
5	</task>
6
7	<context>
8	CRITICAL: Read the command creation guide first: @/docs/claude-commands-guide.md
9
10	This meta-command helps create other commands by:
11
12	1. Understanding the command's purpose
13	2. Determining its category and pattern
14	3. Choosing command location (project vs user)
15	4. Generating the command file
16	5. Creating supporting resources
17	6. Updating documentation
18	</context>
19
20	<command_categories>
21
22	1. Planning Commands (Specialized)
23	- Feature ideation, proposals, PRDs
24	- Complex workflows with distinct stages
25	- Interactive, conversational style
26	- Create documentation artifacts
27	- Examples: @/.claude/commands/01_brainstorm-feature.md
28	@/.claude/commands/02_feature-proposal.md
29
30	2. Implementation Commands (Generic with Modes)
31	- Technical execution tasks
32	- Mode-based variations (ui, core, mcp, etc.)
33	- Follow established patterns
34	- Update task states
35	- Example: @/.claude/commands/implement.md
36
37	3. Analysis Commands (Specialized)
38	- Review, audit, analyze
39	- Generate reports or insights
40	- Read-heavy operations
41	- Provide recommendations
42	- Example: @/.claude/commands/review.md
43
44	4. Workflow Commands (Specialized)
45	- Orchestrate multiple steps
46	- Coordinate between areas
47	- Manage dependencies
48	- Track progress
49	- Example: @/.claude/commands/04_feature-planning.md
50
51	5. Utility Commands (Generic or Specialized)
52	- Tools, helpers, maintenance
53	- Simple operations
54	- May or may not need modes
55	</command_categories>
56
57	<command_frontmatter>
58
59	## CRITICAL: Every Command Must Start with Frontmatter
60
61	All command files MUST begin with YAML frontmatter enclosed in `---` delimiters:
62
63	```markdown
64	---
65	description: Brief description of what the command does
66	argument-hint: Description of expected arguments (optional)
67	---
68	```
69
70	### Frontmatter Fields
71
72	1. `description` (REQUIRED):
73	- One-line summary of the command's purpose
74	- Clear, concise, action-oriented
75	- Example: "Guided feature development with codebase understanding and architecture focus"
76
77	2. `argument-hint` (OPTIONAL):
78	- Describes what arguments the command accepts
79	- Examples:
80	- "Optional feature description"
81	- "File path to analyze"
82	- "Component name and location"
83	- "None required - interactive mode"
84
85	### Example Frontmatter by Command Type
86
87	```markdown
88	# Planning Command
89	---
90	description: Interactive brainstorming session for new feature ideas
91	argument-hint: Optional initial feature concept
92	---
93
94	# Implementation Command
95	---
96	description: Implements features using mode-based patterns (ui, core, mcp)
97	argument-hint: Mode and feature description (e.g., 'ui: add dark mode toggle')
98	---
99
100	# Analysis Command
101	---
102	description: Comprehensive code review with quality assessment
103	argument-hint: Optional file or directory path to review
104	---
105
106	# Utility Command
107	---
108	description: Validates API documentation against OpenAPI standards
109	argument-hint: Path to OpenAPI spec file
110	---
111	```
112
113	### Placement
114
115	- Frontmatter MUST be the very first content in the file
116	- No blank lines before the opening `---`
117	- One blank line after the closing `---` before content begins
118	</command_frontmatter>
119
120	<command_features>
121
122	## Slash Command Features
123
124	### Namespacing
125
126	Use subdirectories to group related commands. Subdirectories appear in the command description but don't affect the command name.
127
128	Example:
129	- `.claude/commands/frontend/component.md` creates `/component` with description "(project:frontend)"
130	- `~/.claude/commands/component.md` creates `/component` with description "(user)"
131
132	Priority: If a project command and user command share the same name, the project command takes precedence.
133
134	### Arguments
135
136	#### All Arguments with `$ARGUMENTS`
137
138	Captures all arguments passed to the command:
139
140	```bash
141	# Command definition
142	echo 'Fix issue #$ARGUMENTS following our coding standards' > .claude/commands/fix-issue.md
143
144	# Usage
145	> /fix-issue 123 high-priority
146	# $ARGUMENTS becomes: "123 high-priority"
147	```
148
149	#### Individual Arguments with `$1`, `$2`, etc.
150
151	Access specific arguments individually using positional parameters:
152
153	```bash
154	# Command definition
155	echo 'Review PR #$1 with priority $2 and assign to $3' > .claude/commands/review-pr.md
156
157	# Usage
158	> /review-pr 456 high alice
159	# $1 becomes "456", $2 becomes "high", $3 becomes "alice"
160	```
161
162	### Bash Command Execution
163
164	Execute bash commands before the slash command runs using the `!` prefix. The output is included in the command context.
165
166	Note: You must include `allowed-tools`

People who liked this also viewed

6 picks

Type

lark-drive飞书云空间（云盘/云存储）：管理 Drive 文件和文件夹，包含上传/下载、创建文件夹、复制/移动/删除、查看元数据、评论/权限/订阅、标题、版本、飞书文档密级标签（secure labels）和本地文件导入。用户需要整理云盘目录、处理云空间资源 URL/token、判断链接类型/真实 token/标题，或导入 Word/Markdown/Excel/CSV/PPTX/.base 为 docx/sSkillsJul 2026382k16k
lark-sharedUse for lark-cli setup/auth tasks: auth login/status/logout, user vs bot identity, business-domain permissions (--domain, including all/docs/drive), missing scopes, revoking authorization, or handlingSkillsJul 2026382k16k
lark-whiteboard飞书画板：查询和编辑飞书云文档中的画板。支持导出画板为预览图片、导出原始节点结构、使用多种格式更新画板内容。当用户需要查看画板内容、导出画板图片、编辑画板时使用此 skill。不负责：飞书云文档内容编辑（lark-doc）、文档内嵌电子表格/Base（lark-sheets / lark-base）。SkillsJul 2026380k16k
lark-task飞书任务：管理任务、清单和任务智能体。创建待办任务、查看和更新任务状态、拆分子任务、组织任务清单、分配协作成员、上传任务附件、注册或注销任务智能体、更新任务智能体的主页数据、写入智能体任务记录。当用户需要创建待办事项、查看任务列表、跟踪任务进度、管理项目清单或给他人分配任务、为任务上传附件文件、注册注销任务智能体、更新智能体主页数据、写入任务记录时使用。SkillsJul 2026380k16k
lark-attendance飞书考勤打卡：查询自己的考勤打卡记录SkillsJul 2026330k16k
lark-apps妙搭（Spark/Miaoda）应用开发与托管：应用创建、本地全栈开发、云端生成迭代、创意设计（UI mockup / 可交互原型 / 线框图 / 落地页 / 仪表盘 / 幻灯片 deck / 视觉探索）、AI相关能力和飞书平台能力或者其他外部能力集成、日志/Trace/监控指标/PV/UV 查询、环境变量管理、应用角色与成员管理、自动化触发器（定时/记录变更/Webhook/飞书审批）。当用户要SkillsJul 2026227k16k

create-command

827installs132forks

View on GitHub

How to install create-command?

neolabhq/context-engineering-kit/create-command

$npx -y skills add NeoLabHQ/context-engineering-kit --skill create-command

Installs into the current project.

Summary

Interactive assistant for creating new Claude commands with proper structure, patterns, and MCP tool integration

Files · 1

View on GitHub

SKILL.md

1	# Command Creator Assistant
2
3	<task>
4	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.
5	</task>
6
7	<context>
8	CRITICAL: Read the command creation guide first: @/docs/claude-commands-guide.md
9
10	This meta-command helps create other commands by:
11
12	1. Understanding the command's purpose
13	2. Determining its category and pattern
14	3. Choosing command location (project vs user)
15	4. Generating the command file
16	5. Creating supporting resources
17	6. Updating documentation
18	</context>
19
20	<command_categories>
21
22	1. Planning Commands (Specialized)
23	- Feature ideation, proposals, PRDs
24	- Complex workflows with distinct stages
25	- Interactive, conversational style
26	- Create documentation artifacts
27	- Examples: @/.claude/commands/01_brainstorm-feature.md
28	@/.claude/commands/02_feature-proposal.md
29
30	2. Implementation Commands (Generic with Modes)
31	- Technical execution tasks
32	- Mode-based variations (ui, core, mcp, etc.)
33	- Follow established patterns
34	- Update task states
35	- Example: @/.claude/commands/implement.md
36
37	3. Analysis Commands (Specialized)
38	- Review, audit, analyze
39	- Generate reports or insights
40	- Read-heavy operations
41	- Provide recommendations
42	- Example: @/.claude/commands/review.md
43
44	4. Workflow Commands (Specialized)
45	- Orchestrate multiple steps
46	- Coordinate between areas
47	- Manage dependencies
48	- Track progress
49	- Example: @/.claude/commands/04_feature-planning.md
50
51	5. Utility Commands (Generic or Specialized)
52	- Tools, helpers, maintenance
53	- Simple operations
54	- May or may not need modes
55	</command_categories>
56
57	<command_frontmatter>
58
59	## CRITICAL: Every Command Must Start with Frontmatter
60
61	All command files MUST begin with YAML frontmatter enclosed in `---` delimiters:
62
63	```markdown
64	---
65	description: Brief description of what the command does
66	argument-hint: Description of expected arguments (optional)
67	---
68	```
69
70	### Frontmatter Fields
71
72	1. `description` (REQUIRED):
73	- One-line summary of the command's purpose
74	- Clear, concise, action-oriented
75	- Example: "Guided feature development with codebase understanding and architecture focus"
76
77	2. `argument-hint` (OPTIONAL):
78	- Describes what arguments the command accepts
79	- Examples:
80	- "Optional feature description"
81	- "File path to analyze"
82	- "Component name and location"
83	- "None required - interactive mode"
84
85	### Example Frontmatter by Command Type
86
87	```markdown
88	# Planning Command
89	---
90	description: Interactive brainstorming session for new feature ideas
91	argument-hint: Optional initial feature concept
92	---
93
94	# Implementation Command
95	---
96	description: Implements features using mode-based patterns (ui, core, mcp)
97	argument-hint: Mode and feature description (e.g., 'ui: add dark mode toggle')
98	---
99
100	# Analysis Command
101	---
102	description: Comprehensive code review with quality assessment
103	argument-hint: Optional file or directory path to review
104	---
105
106	# Utility Command
107	---
108	description: Validates API documentation against OpenAPI standards
109	argument-hint: Path to OpenAPI spec file
110	---
111	```
112
113	### Placement
114
115	- Frontmatter MUST be the very first content in the file
116	- No blank lines before the opening `---`
117	- One blank line after the closing `---` before content begins
118	</command_frontmatter>
119
120	<command_features>
121
122	## Slash Command Features
123
124	### Namespacing
125
126	Use subdirectories to group related commands. Subdirectories appear in the command description but don't affect the command name.
127
128	Example:
129	- `.claude/commands/frontend/component.md` creates `/component` with description "(project:frontend)"
130	- `~/.claude/commands/component.md` creates `/component` with description "(user)"
131
132	Priority: If a project command and user command share the same name, the project command takes precedence.
133
134	### Arguments
135
136	#### All Arguments with `$ARGUMENTS`
137
138	Captures all arguments passed to the command:
139
140	```bash
141	# Command definition
142	echo 'Fix issue #$ARGUMENTS following our coding standards' > .claude/commands/fix-issue.md
143
144	# Usage
145	> /fix-issue 123 high-priority
146	# $ARGUMENTS becomes: "123 high-priority"
147	```
148
149	#### Individual Arguments with `$1`, `$2`, etc.
150
151	Access specific arguments individually using positional parameters:
152
153	```bash
154	# Command definition
155	echo 'Review PR #$1 with priority $2 and assign to $3' > .claude/commands/review-pr.md
156
157	# Usage
158	> /review-pr 456 high alice
159	# $1 becomes "456", $2 becomes "high", $3 becomes "alice"
160	```
161
162	### Bash Command Execution
163
164	Execute bash commands before the slash command runs using the `!` prefix. The output is included in the command context.
165
166	Note: You must include `allowed-tools`

People who liked this also viewed

6 picks

Type