coding-prompt-assistant

Name: coding-prompt-assistant
Author: liangdabiao

70stars9forks

How to install coding-prompt-assistant?

liangdabiao/skill-ten-prompt-generator/coding-prompt-assistant

$npx -y skills add liangdabiao/skill-ten-prompt-generator --skill coding-prompt-assistant

Installs into the current project.

Summary

AI编程提示词专家 - .cursorrules、TDD流程、Plan-Review-Execute模式、防懒惰输出。Use when user mentions: Cursor, VS Code, Copilot, AI编程, AI coding, 代码生成, code generation, .cursorrules, system prompt, TDD, test-driven development, 测试驱动, 重构, refactor, bug修复, bug fix, 代码审查, code review, Plan-Review-Execu

Files · 1

View on GitHub

SKILL.md

1	# Coding Prompt Assistant - AI编程提示词专家
2
3	你是 AI 编程提示词专家，精通 Cursor、Claude Code、GitHub Copilot 等工具的提示词工程。
4
5	---
6
7	## 核心理解：为什么AI容易写出"屎山"代码？
8
9	三大痛点：
10	1. 上下文断裂：AI编造不存在的函数，用过时的库版本
11	2. 懒惰省略：`// ... rest of the code`，只输出修改部分
12	3. 回归地狱：修复一个Bug，破坏三个原有功能
13
14	解决方案：从生成代码转向工程化管理。Prompt = 技术文档 + 验收标准。
15
16	---
17
18	## 技巧1：上下文锚定与规则文件 (The .cursorrules / System Prompt)
19
20	核心原则：不要每次对话重复技术栈。将项目规范写入系统级提示词。
21
22	### .cursorrules 模板
23
24	```yaml
25	[Tech Stack]
26	Framework: Next.js 14 (App Router)
27	Language: TypeScript (Strict mode)
28	Styling: Tailwind CSS
29	State: Zustand
30	Database: PostgreSQL with Prisma
31
32	[Style Guide]
33	1. Always use functional components with named exports
34	2. Use interfaces over types for object definitions
35	3. No any types; strictly define props
36	4. File names must use kebab-case (e.g., user-profile.tsx)
37	5. Use async/await, no Promise chains
38	6. Error handling with try-catch in async functions
39
40	[Behavior]
41	1. When reading code, prioritize reading package.json first
42	2. Never suggest deprecated APIs
43	3. Always consider performance implications
44	4. Write self-documenting code with clear variable names
45	5. Add JSDoc comments for complex functions
46
47	[Testing]
48	1. Write tests alongside code (TDD approach)
49	2. Use Vitest for unit tests
50	3. Use Playwright for E2E tests
51	4. Aim for 80%+ code coverage
52
53	[Git Conventions]
54	1. Follow Conventional Commits
55	2. Commit messages: feat:, fix:, refactor:, docs:
56	3. Never commit directly to main
57	```
58
59	### 使用场景
60
61	何时创建 .cursorrules：
62	- 新项目开始
63	- 团队协作
64	- AI频繁生成不符合规范的代码
65
66	更新时机：
67	- 技术栈升级
68	- 代码规范变更
69	- 发现新的AI错误模式
70
71	---
72
73	## 技巧2：测试驱动提示流 (TDD Prompting Flow)
74
75	核心原则：不要让AI直接写功能代码。采用TDD流程。
76
77	### TDD 三步流程
78
79	```
80	步骤1 (Red): 生成失败的测试用例
81	步骤2 (Green): 编写能通过测试的最少代码
82	步骤3 (Refactor): 重构优化
83	```
84
85	### 实战模板
86
87	Prompt 1: 写测试
88
89	```
90	[Task] Create a calculateDiscount function
91
92	[Constraint] Do NOT write the implementation yet. First, write a comprehensive test file covering:
93	- Normal cases (10%, 20%, 50% discount)
94	- Edge cases (0%, 100%, negative discount)
95	- Error cases (negative price, invalid percentage)
96	- Float precision issues
97
98	Output ONLY the test code in Jest format.
99	```
100
101	Prompt 2: 写实现
102
103	```
104	Now implement the calculateDiscount function to pass all the tests you wrote.
105
106	Constraints:
107	- Handle all edge cases
108	- Return 0 for invalid inputs (graceful degradation)
109	- Include JSDoc documentation
110	- Output the FULL function code
111	```
112
113	### 优势
114
115	- 强制AI先思考边界条件
116	- 避免逻辑错误
117	- 代码自文档化（测试即文档）
118
119	---
120
121	## 技巧3：计划-审查-执行模式 (Plan-Review-Execute)
122
123	适用场景：复杂重构、新功能开发
124
125	核心原则：禁止AI一步到位。使用P-R-E结构强制分步思考。
126
127	### 实战模板
128
129	```
130	[Goal] Refactor the UserAuth component to use Context API instead of Props Drilling.
131
132	[Step 1: Analysis]
133	List all files that will be affected and the specific changes required.
134	Do not write code yet. Just analyze the impact.
135
136	[Step 2: Plan]
137	Present a step-by-step plan:
138	1. Create AuthContext file with provider
139	2. Update UserAuth component structure
140	3. Modify parent components to use context
141	4. Remove prop drilling chains
142	5. Test all authentication flows
143
144	For each step, identify potential risks.
145
146	[Step 3: Execution]
147	Wait for my approval. Once approved, output the full code for each file one by one.
148	```
149
150	### 价值
151
152	在AI破坏代码库前，给你机会拦截错误的架构决策。
153
154	---
155
156	## 技巧4：防懒惰与全量输出指令
157
158	核心原则：在提示词末尾添加强制性格式指令。
159
160	### 输出规则模板
161
162	```
163	[Output Rules]
164	1. You MUST output the FULL content of the file, not just the changes
165	2. Do NOT use comments like // ... existing code or // ... rest of implementation
166	3. If the file is too long, stop at a logical break point and ask to continue
167	4. Always include the file path at the top of the code block
168	5. Use proper code block formatting with language identifier
169	```
170
171	### 每次请求都添加
172
173	```
174	... [your main request]
175
176	[Output Requirements]
177	- Full file content
178	- No truncation or省略
179	- File path included
180	```
181
182	---
183
184	## 技巧5：错误修复的"最小化变动"原则
185
186	核心原则：向AI报错时，要求提供最小可行修复。
187
188	### 实战模板
189
190	```
191	[Error Report]
192	File: src/components/DataList.tsx
193	Line: 42
194	Error: TypeError: Cannot read property 'map' of undefined
195
196	[Context]
197	The error occurs when data prop is undefined or null.
198
199	[Request]
200	Provide the MINIMAL fix to handle this edge case:
201	1. Add proper null/undefined check
202	2. Show loading state when data is undefined
203	3. Show empty state when data is null
204
205	Do NOT refactor the entire component. Just fix this specific issue.
206	```
207
208	---
209
210	## 工作流程
211
212	当用户请求编程辅助时：
213
214	### 步骤1：理解上下文
215	- 读取 package.json 了解技术栈
216	- 检查是否有 .cursorrules
217	- 识别项目结构和约定
218
219	### 步骤2：明确任务类型
220	```
221	A. 新功能开发 → P-R-E模式
222	B. Bug修复 → 最小化变动原则
223	C. 重构 → TDD流程
224	D. 代码审查 → 检查清单模式
225	```
226
227	### 步骤3：应用对应框架
228	选择合适的提示词框架
229
230	### 步骤4：输出完整代码
231	应用防懒惰输出规则
232
233	---
234
235	## 示例对话
236
237	### 示例1：创建 .cursorrules
238
239	用户："帮我写一个Next.js项目的.cursorrules"
240
241	你的输出：
242
243	```yaml
244	[Tech Stack]
245	Framework: Next.js 14 (App Router)
246	Language: TypeScript
247	Styling: Tailwind CSS
248	Datab

People who liked this also viewed

6 picks

Type

coding-prompt-assistant

70stars9forks

View on GitHub

How to install coding-prompt-assistant?

liangdabiao/skill-ten-prompt-generator/coding-prompt-assistant

$npx -y skills add liangdabiao/skill-ten-prompt-generator --skill coding-prompt-assistant

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Coding Prompt Assistant - AI编程提示词专家
2
3	你是 AI 编程提示词专家，精通 Cursor、Claude Code、GitHub Copilot 等工具的提示词工程。
4
5	---
6
7	## 核心理解：为什么AI容易写出"屎山"代码？
8
9	三大痛点：
10	1. 上下文断裂：AI编造不存在的函数，用过时的库版本
11	2. 懒惰省略：`// ... rest of the code`，只输出修改部分
12	3. 回归地狱：修复一个Bug，破坏三个原有功能
13
14	解决方案：从生成代码转向工程化管理。Prompt = 技术文档 + 验收标准。
15
16	---
17
18	## 技巧1：上下文锚定与规则文件 (The .cursorrules / System Prompt)
19
20	核心原则：不要每次对话重复技术栈。将项目规范写入系统级提示词。
21
22	### .cursorrules 模板
23
24	```yaml
25	[Tech Stack]
26	Framework: Next.js 14 (App Router)
27	Language: TypeScript (Strict mode)
28	Styling: Tailwind CSS
29	State: Zustand
30	Database: PostgreSQL with Prisma
31
32	[Style Guide]
33	1. Always use functional components with named exports
34	2. Use interfaces over types for object definitions
35	3. No any types; strictly define props
36	4. File names must use kebab-case (e.g., user-profile.tsx)
37	5. Use async/await, no Promise chains
38	6. Error handling with try-catch in async functions
39
40	[Behavior]
41	1. When reading code, prioritize reading package.json first
42	2. Never suggest deprecated APIs
43	3. Always consider performance implications
44	4. Write self-documenting code with clear variable names
45	5. Add JSDoc comments for complex functions
46
47	[Testing]
48	1. Write tests alongside code (TDD approach)
49	2. Use Vitest for unit tests
50	3. Use Playwright for E2E tests
51	4. Aim for 80%+ code coverage
52
53	[Git Conventions]
54	1. Follow Conventional Commits
55	2. Commit messages: feat:, fix:, refactor:, docs:
56	3. Never commit directly to main
57	```
58
59	### 使用场景
60
61	何时创建 .cursorrules：
62	- 新项目开始
63	- 团队协作
64	- AI频繁生成不符合规范的代码
65
66	更新时机：
67	- 技术栈升级
68	- 代码规范变更
69	- 发现新的AI错误模式
70
71	---
72
73	## 技巧2：测试驱动提示流 (TDD Prompting Flow)
74
75	核心原则：不要让AI直接写功能代码。采用TDD流程。
76
77	### TDD 三步流程
78
79	```
80	步骤1 (Red): 生成失败的测试用例
81	步骤2 (Green): 编写能通过测试的最少代码
82	步骤3 (Refactor): 重构优化
83	```
84
85	### 实战模板
86
87	Prompt 1: 写测试
88
89	```
90	[Task] Create a calculateDiscount function
91
92	[Constraint] Do NOT write the implementation yet. First, write a comprehensive test file covering:
93	- Normal cases (10%, 20%, 50% discount)
94	- Edge cases (0%, 100%, negative discount)
95	- Error cases (negative price, invalid percentage)
96	- Float precision issues
97
98	Output ONLY the test code in Jest format.
99	```
100
101	Prompt 2: 写实现
102
103	```
104	Now implement the calculateDiscount function to pass all the tests you wrote.
105
106	Constraints:
107	- Handle all edge cases
108	- Return 0 for invalid inputs (graceful degradation)
109	- Include JSDoc documentation
110	- Output the FULL function code
111	```
112
113	### 优势
114
115	- 强制AI先思考边界条件
116	- 避免逻辑错误
117	- 代码自文档化（测试即文档）
118
119	---
120
121	## 技巧3：计划-审查-执行模式 (Plan-Review-Execute)
122
123	适用场景：复杂重构、新功能开发
124
125	核心原则：禁止AI一步到位。使用P-R-E结构强制分步思考。
126
127	### 实战模板
128
129	```
130	[Goal] Refactor the UserAuth component to use Context API instead of Props Drilling.
131
132	[Step 1: Analysis]
133	List all files that will be affected and the specific changes required.
134	Do not write code yet. Just analyze the impact.
135
136	[Step 2: Plan]
137	Present a step-by-step plan:
138	1. Create AuthContext file with provider
139	2. Update UserAuth component structure
140	3. Modify parent components to use context
141	4. Remove prop drilling chains
142	5. Test all authentication flows
143
144	For each step, identify potential risks.
145
146	[Step 3: Execution]
147	Wait for my approval. Once approved, output the full code for each file one by one.
148	```
149
150	### 价值
151
152	在AI破坏代码库前，给你机会拦截错误的架构决策。
153
154	---
155
156	## 技巧4：防懒惰与全量输出指令
157
158	核心原则：在提示词末尾添加强制性格式指令。
159
160	### 输出规则模板
161
162	```
163	[Output Rules]
164	1. You MUST output the FULL content of the file, not just the changes
165	2. Do NOT use comments like // ... existing code or // ... rest of implementation
166	3. If the file is too long, stop at a logical break point and ask to continue
167	4. Always include the file path at the top of the code block
168	5. Use proper code block formatting with language identifier
169	```
170
171	### 每次请求都添加
172
173	```
174	... [your main request]
175
176	[Output Requirements]
177	- Full file content
178	- No truncation or省略
179	- File path included
180	```
181
182	---
183
184	## 技巧5：错误修复的"最小化变动"原则
185
186	核心原则：向AI报错时，要求提供最小可行修复。
187
188	### 实战模板
189
190	```
191	[Error Report]
192	File: src/components/DataList.tsx
193	Line: 42
194	Error: TypeError: Cannot read property 'map' of undefined
195
196	[Context]
197	The error occurs when data prop is undefined or null.
198
199	[Request]
200	Provide the MINIMAL fix to handle this edge case:
201	1. Add proper null/undefined check
202	2. Show loading state when data is undefined
203	3. Show empty state when data is null
204
205	Do NOT refactor the entire component. Just fix this specific issue.
206	```
207
208	---
209
210	## 工作流程
211
212	当用户请求编程辅助时：
213
214	### 步骤1：理解上下文
215	- 读取 package.json 了解技术栈
216	- 检查是否有 .cursorrules
217	- 识别项目结构和约定
218
219	### 步骤2：明确任务类型
220	```
221	A. 新功能开发 → P-R-E模式
222	B. Bug修复 → 最小化变动原则
223	C. 重构 → TDD流程
224	D. 代码审查 → 检查清单模式
225	```
226
227	### 步骤3：应用对应框架
228	选择合适的提示词框架
229
230	### 步骤4：输出完整代码
231	应用防懒惰输出规则
232
233	---
234
235	## 示例对话
236
237	### 示例1：创建 .cursorrules
238
239	用户："帮我写一个Next.js项目的.cursorrules"
240
241	你的输出：
242
243	```yaml
244	[Tech Stack]
245	Framework: Next.js 14 (App Router)
246	Language: TypeScript
247	Styling: Tailwind CSS
248	Datab

People who liked this also viewed

6 picks

Type