@votruongdanh/ai-agent-skills 1.4.0 → 1.5.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/.agent/rules/brainstorm.md +21 -0
- package/.agent/rules/clean.md +45 -0
- package/.agent/rules/debug.md +24 -0
- package/.agent/rules/enhance.md +14 -0
- package/.cursor/rules/brainstorm.mdc +27 -0
- package/.cursor/rules/clean.mdc +51 -0
- package/.cursor/rules/debug.mdc +30 -0
- package/.cursor/rules/enhance.mdc +20 -0
- package/.kiro/skills/clean/SKILL.md +50 -0
- package/README.md +3 -2
- package/package.json +4 -2
|
@@ -0,0 +1,21 @@
|
|
|
1
|
+
## Goal
|
|
2
|
+
Help the user explore many realistic options before implementation.
|
|
3
|
+
|
|
4
|
+
## Workflow
|
|
5
|
+
1. Restate the problem in one or two sentences.
|
|
6
|
+
2. Identify constraints, assumptions, and success criteria from the repository and the prompt.
|
|
7
|
+
3. Produce 3-7 strong options with pros, cons, complexity, and risks.
|
|
8
|
+
4. Call out the most practical option and the boldest option.
|
|
9
|
+
5. End with a recommended next step or implementation path.
|
|
10
|
+
|
|
11
|
+
## Output format
|
|
12
|
+
- Problem framing
|
|
13
|
+
- Constraints
|
|
14
|
+
- Options
|
|
15
|
+
- Recommendation
|
|
16
|
+
- Next step
|
|
17
|
+
|
|
18
|
+
## Rules
|
|
19
|
+
- Prefer practical ideas grounded in the current project.
|
|
20
|
+
- Avoid pretending uncertain assumptions are facts.
|
|
21
|
+
- If code context matters, inspect the repo structure first.
|
|
@@ -0,0 +1,45 @@
|
|
|
1
|
+
## Goal
|
|
2
|
+
Identify and remove unnecessary files generated by AI, build processes, or development tools without affecting the working codebase.
|
|
3
|
+
|
|
4
|
+
## Workflow
|
|
5
|
+
1. Scan the project for common junk file patterns (temp files, logs, cache, node_modules, build artifacts).
|
|
6
|
+
2. Identify AI-generated files that may be redundant or outdated.
|
|
7
|
+
3. Present a clear list of files to be removed with their sizes and reasons.
|
|
8
|
+
4. Ask for confirmation before deletion.
|
|
9
|
+
5. Remove approved files and report the space saved.
|
|
10
|
+
6. Suggest .gitignore updates if needed.
|
|
11
|
+
|
|
12
|
+
## Common Junk Patterns
|
|
13
|
+
- Temporary files: `*.tmp`, `*.temp`, `*.bak`, `*.swp`, `*~`
|
|
14
|
+
- Log files: `*.log`, `*.log.*`, `debug.log`, `error.log`
|
|
15
|
+
- Cache directories: `.cache/`, `__pycache__/`, `.pytest_cache/`, `.mypy_cache/`
|
|
16
|
+
- Build artifacts: `dist/`, `build/`, `*.pyc`, `*.pyo`, `*.class`, `*.o`
|
|
17
|
+
- Node modules: `node_modules/` (if not needed)
|
|
18
|
+
- IDE files: `.vscode/`, `.idea/` (if not in .gitignore)
|
|
19
|
+
- OS files: `.DS_Store`, `Thumbs.db`, `desktop.ini`
|
|
20
|
+
- AI artifacts: Duplicate markdown files, unused generated code, test outputs
|
|
21
|
+
|
|
22
|
+
## Safety Rules
|
|
23
|
+
- Never delete files in version control (check git status first).
|
|
24
|
+
- Never delete configuration files (.env, config.json, etc.) unless explicitly requested.
|
|
25
|
+
- Never delete source code without explicit confirmation.
|
|
26
|
+
- Always show what will be deleted before proceeding.
|
|
27
|
+
- Preserve .gitignore and other dot files unless they're clearly junk.
|
|
28
|
+
- Ask before removing entire directories.
|
|
29
|
+
|
|
30
|
+
## Output Format
|
|
31
|
+
```
|
|
32
|
+
Files to clean:
|
|
33
|
+
1. [Category] path/to/file (size) - Reason
|
|
34
|
+
2. [Category] path/to/file (size) - Reason
|
|
35
|
+
...
|
|
36
|
+
|
|
37
|
+
Total space to recover: XX MB
|
|
38
|
+
|
|
39
|
+
Proceed with deletion? (y/n)
|
|
40
|
+
```
|
|
41
|
+
|
|
42
|
+
## Follow-up Actions
|
|
43
|
+
- Update .gitignore to prevent future junk accumulation
|
|
44
|
+
- Suggest cleanup scripts for recurring patterns
|
|
45
|
+
- Recommend build tool configurations to reduce artifacts
|
|
@@ -0,0 +1,24 @@
|
|
|
1
|
+
## Goal
|
|
2
|
+
Find the real root cause, not just the first visible symptom.
|
|
3
|
+
|
|
4
|
+
## Workflow
|
|
5
|
+
1. Summarize the bug, expected behavior, and actual behavior.
|
|
6
|
+
2. Gather evidence from logs, stack traces, code paths, config, and recent changes.
|
|
7
|
+
3. List the top hypotheses ranked by likelihood.
|
|
8
|
+
4. Eliminate hypotheses using direct evidence.
|
|
9
|
+
5. Identify the root cause.
|
|
10
|
+
6. Propose the smallest safe fix.
|
|
11
|
+
7. Suggest how to verify the fix and prevent regressions.
|
|
12
|
+
|
|
13
|
+
## Output format
|
|
14
|
+
- Symptom
|
|
15
|
+
- Evidence
|
|
16
|
+
- Hypotheses
|
|
17
|
+
- Root cause
|
|
18
|
+
- Fix
|
|
19
|
+
- Verification
|
|
20
|
+
|
|
21
|
+
## Rules
|
|
22
|
+
- Do not guess when evidence is missing; say what must be checked.
|
|
23
|
+
- Prefer deterministic reproduction steps.
|
|
24
|
+
- Mention any hidden risk or side effect of the fix.
|
|
@@ -0,0 +1,14 @@
|
|
|
1
|
+
## Goal
|
|
2
|
+
Improve an existing implementation without breaking working behavior.
|
|
3
|
+
|
|
4
|
+
## Workflow
|
|
5
|
+
1. Understand the current state and pain points.
|
|
6
|
+
2. Identify high-impact improvements in quality, maintainability, performance, reliability, or UX.
|
|
7
|
+
3. Prioritize improvements by value versus effort.
|
|
8
|
+
4. Implement or recommend the top changes.
|
|
9
|
+
5. Explain tradeoffs and validation steps.
|
|
10
|
+
|
|
11
|
+
## Rules
|
|
12
|
+
- Preserve behavior unless the user asked for a behavior change.
|
|
13
|
+
- Prefer small, meaningful upgrades over broad rewrites.
|
|
14
|
+
- If performance is discussed, explain where the gain comes from.
|
|
@@ -0,0 +1,27 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: "Use when the user wants ideation, option generation, feature exploration, or types /brainstorm."
|
|
3
|
+
globs: ""
|
|
4
|
+
alwaysApply: false
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
## Goal
|
|
8
|
+
Help the user explore many realistic options before implementation.
|
|
9
|
+
|
|
10
|
+
## Workflow
|
|
11
|
+
1. Restate the problem in one or two sentences.
|
|
12
|
+
2. Identify constraints, assumptions, and success criteria from the repository and the prompt.
|
|
13
|
+
3. Produce 3-7 strong options with pros, cons, complexity, and risks.
|
|
14
|
+
4. Call out the most practical option and the boldest option.
|
|
15
|
+
5. End with a recommended next step or implementation path.
|
|
16
|
+
|
|
17
|
+
## Output format
|
|
18
|
+
- Problem framing
|
|
19
|
+
- Constraints
|
|
20
|
+
- Options
|
|
21
|
+
- Recommendation
|
|
22
|
+
- Next step
|
|
23
|
+
|
|
24
|
+
## Rules
|
|
25
|
+
- Prefer practical ideas grounded in the current project.
|
|
26
|
+
- Avoid pretending uncertain assumptions are facts.
|
|
27
|
+
- If code context matters, inspect the repo structure first.
|
|
@@ -0,0 +1,51 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: "Use when the user wants to clean up junk files, temporary files, AI-generated artifacts, cache, or types /clean."
|
|
3
|
+
globs: ""
|
|
4
|
+
alwaysApply: false
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
## Goal
|
|
8
|
+
Identify and remove unnecessary files generated by AI, build processes, or development tools without affecting the working codebase.
|
|
9
|
+
|
|
10
|
+
## Workflow
|
|
11
|
+
1. Scan the project for common junk file patterns (temp files, logs, cache, node_modules, build artifacts).
|
|
12
|
+
2. Identify AI-generated files that may be redundant or outdated.
|
|
13
|
+
3. Present a clear list of files to be removed with their sizes and reasons.
|
|
14
|
+
4. Ask for confirmation before deletion.
|
|
15
|
+
5. Remove approved files and report the space saved.
|
|
16
|
+
6. Suggest .gitignore updates if needed.
|
|
17
|
+
|
|
18
|
+
## Common Junk Patterns
|
|
19
|
+
- Temporary files: `*.tmp`, `*.temp`, `*.bak`, `*.swp`, `*~`
|
|
20
|
+
- Log files: `*.log`, `*.log.*`, `debug.log`, `error.log`
|
|
21
|
+
- Cache directories: `.cache/`, `__pycache__/`, `.pytest_cache/`, `.mypy_cache/`
|
|
22
|
+
- Build artifacts: `dist/`, `build/`, `*.pyc`, `*.pyo`, `*.class`, `*.o`
|
|
23
|
+
- Node modules: `node_modules/` (if not needed)
|
|
24
|
+
- IDE files: `.vscode/`, `.idea/` (if not in .gitignore)
|
|
25
|
+
- OS files: `.DS_Store`, `Thumbs.db`, `desktop.ini`
|
|
26
|
+
- AI artifacts: Duplicate markdown files, unused generated code, test outputs
|
|
27
|
+
|
|
28
|
+
## Safety Rules
|
|
29
|
+
- Never delete files in version control (check git status first).
|
|
30
|
+
- Never delete configuration files (.env, config.json, etc.) unless explicitly requested.
|
|
31
|
+
- Never delete source code without explicit confirmation.
|
|
32
|
+
- Always show what will be deleted before proceeding.
|
|
33
|
+
- Preserve .gitignore and other dot files unless they're clearly junk.
|
|
34
|
+
- Ask before removing entire directories.
|
|
35
|
+
|
|
36
|
+
## Output Format
|
|
37
|
+
```
|
|
38
|
+
Files to clean:
|
|
39
|
+
1. [Category] path/to/file (size) - Reason
|
|
40
|
+
2. [Category] path/to/file (size) - Reason
|
|
41
|
+
...
|
|
42
|
+
|
|
43
|
+
Total space to recover: XX MB
|
|
44
|
+
|
|
45
|
+
Proceed with deletion? (y/n)
|
|
46
|
+
```
|
|
47
|
+
|
|
48
|
+
## Follow-up Actions
|
|
49
|
+
- Update .gitignore to prevent future junk accumulation
|
|
50
|
+
- Suggest cleanup scripts for recurring patterns
|
|
51
|
+
- Recommend build tool configurations to reduce artifacts
|
|
@@ -0,0 +1,30 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: "Use when the user wants root-cause analysis for a bug, failing command, broken behavior, error log, or types /debug."
|
|
3
|
+
globs: ""
|
|
4
|
+
alwaysApply: false
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
## Goal
|
|
8
|
+
Find the real root cause, not just the first visible symptom.
|
|
9
|
+
|
|
10
|
+
## Workflow
|
|
11
|
+
1. Summarize the bug, expected behavior, and actual behavior.
|
|
12
|
+
2. Gather evidence from logs, stack traces, code paths, config, and recent changes.
|
|
13
|
+
3. List the top hypotheses ranked by likelihood.
|
|
14
|
+
4. Eliminate hypotheses using direct evidence.
|
|
15
|
+
5. Identify the root cause.
|
|
16
|
+
6. Propose the smallest safe fix.
|
|
17
|
+
7. Suggest how to verify the fix and prevent regressions.
|
|
18
|
+
|
|
19
|
+
## Output format
|
|
20
|
+
- Symptom
|
|
21
|
+
- Evidence
|
|
22
|
+
- Hypotheses
|
|
23
|
+
- Root cause
|
|
24
|
+
- Fix
|
|
25
|
+
- Verification
|
|
26
|
+
|
|
27
|
+
## Rules
|
|
28
|
+
- Do not guess when evidence is missing; say what must be checked.
|
|
29
|
+
- Prefer deterministic reproduction steps.
|
|
30
|
+
- Mention any hidden risk or side effect of the fix.
|
|
@@ -0,0 +1,20 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: "Use when the user wants to improve an existing feature, refactor code, optimize UX or performance, tighten security, or types /enhance."
|
|
3
|
+
globs: ""
|
|
4
|
+
alwaysApply: false
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
## Goal
|
|
8
|
+
Improve an existing implementation without breaking working behavior.
|
|
9
|
+
|
|
10
|
+
## Workflow
|
|
11
|
+
1. Understand the current state and pain points.
|
|
12
|
+
2. Identify high-impact improvements in quality, maintainability, performance, reliability, or UX.
|
|
13
|
+
3. Prioritize improvements by value versus effort.
|
|
14
|
+
4. Implement or recommend the top changes.
|
|
15
|
+
5. Explain tradeoffs and validation steps.
|
|
16
|
+
|
|
17
|
+
## Rules
|
|
18
|
+
- Preserve behavior unless the user asked for a behavior change.
|
|
19
|
+
- Prefer small, meaningful upgrades over broad rewrites.
|
|
20
|
+
- If performance is discussed, explain where the gain comes from.
|
|
@@ -0,0 +1,50 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: clean
|
|
3
|
+
description: Use when the user wants to clean up junk files, temporary files, AI-generated artifacts, cache, or types /clean.
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
## Goal
|
|
7
|
+
Identify and remove unnecessary files generated by AI, build processes, or development tools without affecting the working codebase.
|
|
8
|
+
|
|
9
|
+
## Workflow
|
|
10
|
+
1. Scan the project for common junk file patterns (temp files, logs, cache, node_modules, build artifacts).
|
|
11
|
+
2. Identify AI-generated files that may be redundant or outdated.
|
|
12
|
+
3. Present a clear list of files to be removed with their sizes and reasons.
|
|
13
|
+
4. Ask for confirmation before deletion.
|
|
14
|
+
5. Remove approved files and report the space saved.
|
|
15
|
+
6. Suggest .gitignore updates if needed.
|
|
16
|
+
|
|
17
|
+
## Common Junk Patterns
|
|
18
|
+
- Temporary files: `*.tmp`, `*.temp`, `*.bak`, `*.swp`, `*~`
|
|
19
|
+
- Log files: `*.log`, `*.log.*`, `debug.log`, `error.log`
|
|
20
|
+
- Cache directories: `.cache/`, `__pycache__/`, `.pytest_cache/`, `.mypy_cache/`
|
|
21
|
+
- Build artifacts: `dist/`, `build/`, `*.pyc`, `*.pyo`, `*.class`, `*.o`
|
|
22
|
+
- Node modules: `node_modules/` (if not needed)
|
|
23
|
+
- IDE files: `.vscode/`, `.idea/` (if not in .gitignore)
|
|
24
|
+
- OS files: `.DS_Store`, `Thumbs.db`, `desktop.ini`
|
|
25
|
+
- AI artifacts: Duplicate markdown files, unused generated code, test outputs
|
|
26
|
+
|
|
27
|
+
## Safety Rules
|
|
28
|
+
- Never delete files in version control (check git status first).
|
|
29
|
+
- Never delete configuration files (.env, config.json, etc.) unless explicitly requested.
|
|
30
|
+
- Never delete source code without explicit confirmation.
|
|
31
|
+
- Always show what will be deleted before proceeding.
|
|
32
|
+
- Preserve .gitignore and other dot files unless they're clearly junk.
|
|
33
|
+
- Ask before removing entire directories.
|
|
34
|
+
|
|
35
|
+
## Output Format
|
|
36
|
+
```
|
|
37
|
+
Files to clean:
|
|
38
|
+
1. [Category] path/to/file (size) - Reason
|
|
39
|
+
2. [Category] path/to/file (size) - Reason
|
|
40
|
+
...
|
|
41
|
+
|
|
42
|
+
Total space to recover: XX MB
|
|
43
|
+
|
|
44
|
+
Proceed with deletion? (y/n)
|
|
45
|
+
```
|
|
46
|
+
|
|
47
|
+
## Follow-up Actions
|
|
48
|
+
- Update .gitignore to prevent future junk accumulation
|
|
49
|
+
- Suggest cleanup scripts for recurring patterns
|
|
50
|
+
- Recommend build tool configurations to reduce artifacts
|
package/README.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# 🚀 AI Agent Skills
|
|
2
2
|
|
|
3
|
-
Professional AI agent skills for Kiro, Cursor,
|
|
3
|
+
Professional AI agent skills for Kiro, Cursor, Antigravity, and other AI-powered IDEs. 12 battle-tested workflows to supercharge your development.
|
|
4
4
|
|
|
5
5
|
[](https://www.npmjs.com/package/@votruongdanh/ai-agent-skills)
|
|
6
6
|
[](https://opensource.org/licenses/MIT)
|
|
@@ -32,11 +32,12 @@ The CLI automatically detects your IDE and installs to the correct location:
|
|
|
32
32
|
|
|
33
33
|
No configuration needed - just run the install command!
|
|
34
34
|
|
|
35
|
-
## 📦
|
|
35
|
+
## 📦 12 Professional Skills
|
|
36
36
|
|
|
37
37
|
| Skill | Command | Use Case |
|
|
38
38
|
|-------|---------|----------|
|
|
39
39
|
| **Brainstorm** | `/brainstorm` | Generate ideas and explore features |
|
|
40
|
+
| **Clean** | `/clean` | Remove junk files and AI artifacts |
|
|
40
41
|
| **Create** | `/create` | Build new features from scratch |
|
|
41
42
|
| **Debug** | `/debug` | Find and fix bugs systematically |
|
|
42
43
|
| **Deploy** | `/deploy` | Deployment and CI/CD guidance |
|
package/package.json
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@votruongdanh/ai-agent-skills",
|
|
3
|
-
"version": "1.
|
|
4
|
-
"description": "Professional AI Agent Skills -
|
|
3
|
+
"version": "1.5.0",
|
|
4
|
+
"description": "Professional AI Agent Skills - 12 powerful workflows for Antigravity, Kiro, Cursor, Windsurf, Continue, Cody, and other AI IDEs",
|
|
5
5
|
"main": "index.js",
|
|
6
6
|
"bin": {
|
|
7
7
|
"ai-skills": "bin/cli.js"
|
|
@@ -47,6 +47,8 @@
|
|
|
47
47
|
"homepage": "https://github.com/votruongdanh/ai-agent-skills#readme",
|
|
48
48
|
"files": [
|
|
49
49
|
".kiro",
|
|
50
|
+
".cursor",
|
|
51
|
+
".agent",
|
|
50
52
|
"bin",
|
|
51
53
|
"index.js",
|
|
52
54
|
"README.md"
|