@votruongdanh/ai-agent-skills 1.4.0 → 1.5.1

package/.agent/rules/brainstorm.md

@@ -0,0 +1,21 @@
+## Goal
+Help the user explore many realistic options before implementation.
+
+## Workflow
+1. Restate the problem in one or two sentences.
+2. Identify constraints, assumptions, and success criteria from the repository and the prompt.
+3. Produce 3-7 strong options with pros, cons, complexity, and risks.
+4. Call out the most practical option and the boldest option.
+5. End with a recommended next step or implementation path.
+
+## Output format
+- Problem framing
+- Constraints
+- Options
+- Recommendation
+- Next step
+
+## Rules
+- Prefer practical ideas grounded in the current project.
+- Avoid pretending uncertain assumptions are facts.
+- If code context matters, inspect the repo structure first.

package/.agent/rules/clean.md

@@ -0,0 +1,45 @@
+## Goal
+Identify and remove unnecessary files generated by AI, build processes, or development tools without affecting the working codebase.
+
+## Workflow
+1. Scan the project for common junk file patterns (temp files, logs, cache, node_modules, build artifacts).
+2. Identify AI-generated files that may be redundant or outdated.
+3. Present a clear list of files to be removed with their sizes and reasons.
+4. Ask for confirmation before deletion.
+5. Remove approved files and report the space saved.
+6. Suggest .gitignore updates if needed.
+
+## Common Junk Patterns
+- Temporary files: `*.tmp`, `*.temp`, `*.bak`, `*.swp`, `*~`
+- Log files: `*.log`, `*.log.*`, `debug.log`, `error.log`
+- Cache directories: `.cache/`, `__pycache__/`, `.pytest_cache/`, `.mypy_cache/`
+- Build artifacts: `dist/`, `build/`, `*.pyc`, `*.pyo`, `*.class`, `*.o`
+- Node modules: `node_modules/` (if not needed)
+- IDE files: `.vscode/`, `.idea/` (if not in .gitignore)
+- OS files: `.DS_Store`, `Thumbs.db`, `desktop.ini`
+- AI artifacts: Duplicate markdown files, unused generated code, test outputs
+
+## Safety Rules
+- Never delete files in version control (check git status first).
+- Never delete configuration files (.env, config.json, etc.) unless explicitly requested.
+- Never delete source code without explicit confirmation.
+- Always show what will be deleted before proceeding.
+- Preserve .gitignore and other dot files unless they're clearly junk.
+- Ask before removing entire directories.
+
+## Output Format
+```
+Files to clean:
+1. [Category] path/to/file (size) - Reason
+2. [Category] path/to/file (size) - Reason
+...
+
+Total space to recover: XX MB
+
+Proceed with deletion? (y/n)
+```
+
+## Follow-up Actions
+- Update .gitignore to prevent future junk accumulation
+- Suggest cleanup scripts for recurring patterns
+- Recommend build tool configurations to reduce artifacts

package/.agent/rules/debug.md

@@ -0,0 +1,24 @@
+## Goal
+Find the real root cause, not just the first visible symptom.
+
+## Workflow
+1. Summarize the bug, expected behavior, and actual behavior.
+2. Gather evidence from logs, stack traces, code paths, config, and recent changes.
+3. List the top hypotheses ranked by likelihood.
+4. Eliminate hypotheses using direct evidence.
+5. Identify the root cause.
+6. Propose the smallest safe fix.
+7. Suggest how to verify the fix and prevent regressions.
+
+## Output format
+- Symptom
+- Evidence
+- Hypotheses
+- Root cause
+- Fix
+- Verification
+
+## Rules
+- Do not guess when evidence is missing; say what must be checked.
+- Prefer deterministic reproduction steps.
+- Mention any hidden risk or side effect of the fix.

package/.agent/rules/enhance.md

@@ -0,0 +1,14 @@
+## Goal
+Improve an existing implementation without breaking working behavior.
+
+## Workflow
+1. Understand the current state and pain points.
+2. Identify high-impact improvements in quality, maintainability, performance, reliability, or UX.
+3. Prioritize improvements by value versus effort.
+4. Implement or recommend the top changes.
+5. Explain tradeoffs and validation steps.
+
+## Rules
+- Preserve behavior unless the user asked for a behavior change.
+- Prefer small, meaningful upgrades over broad rewrites.
+- If performance is discussed, explain where the gain comes from.

package/.agent/workflows/brainstorm.md

@@ -0,0 +1,25 @@
+---
+description: Help explore many realistic options before implementation
+---
+
+## Goal
+Help the user explore many realistic options before implementation.
+
+## Workflow
+1. Restate the problem in one or two sentences.
+2. Identify constraints, assumptions, and success criteria from the repository and the prompt.
+3. Produce 3-7 strong options with pros, cons, complexity, and risks.
+4. Call out the most practical option and the boldest option.
+5. End with a recommended next step or implementation path.
+
+## Output format
+- Problem framing
+- Constraints
+- Options
+- Recommendation
+- Next step
+
+## Rules
+- Prefer practical ideas grounded in the current project.
+- Avoid pretending uncertain assumptions are facts.
+- If code context matters, inspect the repo structure first.

package/.agent/workflows/clean.md

@@ -0,0 +1,49 @@
+---
+description: Clean up junk files, temporary files, AI-generated artifacts, and cache
+---
+
+## Goal
+Identify and remove unnecessary files generated by AI, build processes, or development tools without affecting the working codebase.
+
+## Workflow
+1. Scan the project for common junk file patterns (temp files, logs, cache, node_modules, build artifacts).
+2. Identify AI-generated files that may be redundant or outdated.
+3. Present a clear list of files to be removed with their sizes and reasons.
+4. Ask for confirmation before deletion.
+5. Remove approved files and report the space saved.
+6. Suggest .gitignore updates if needed.
+
+## Common Junk Patterns
+- Temporary files: `*.tmp`, `*.temp`, `*.bak`, `*.swp`, `*~`
+- Log files: `*.log`, `*.log.*`, `debug.log`, `error.log`
+- Cache directories: `.cache/`, `__pycache__/`, `.pytest_cache/`, `.mypy_cache/`
+- Build artifacts: `dist/`, `build/`, `*.pyc`, `*.pyo`, `*.class`, `*.o`
+- Node modules: `node_modules/` (if not needed)
+- IDE files: `.vscode/`, `.idea/` (if not in .gitignore)
+- OS files: `.DS_Store`, `Thumbs.db`, `desktop.ini`
+- AI artifacts: Duplicate markdown files, unused generated code, test outputs
+
+## Safety Rules
+- Never delete files in version control (check git status first).
+- Never delete configuration files (.env, config.json, etc.) unless explicitly requested.
+- Never delete source code without explicit confirmation.
+- Always show what will be deleted before proceeding.
+- Preserve .gitignore and other dot files unless they're clearly junk.
+- Ask before removing entire directories.
+
+## Output Format
+```
+Files to clean:
+1. [Category] path/to/file (size) - Reason
+2. [Category] path/to/file (size) - Reason
+...
+
+Total space to recover: XX MB
+
+Proceed with deletion? (y/n)
+```
+
+## Follow-up Actions
+- Update .gitignore to prevent future junk accumulation
+- Suggest cleanup scripts for recurring patterns
+- Recommend build tool configurations to reduce artifacts

package/.agent/workflows/create.md

@@ -0,0 +1,19 @@
+---
+description: Create a new implementation cleanly and with minimal disruption
+---
+
+## Goal
+Create a new implementation cleanly and with minimal disruption.
+
+## Workflow
+1. Understand the requested artifact and the existing project structure.
+2. Identify the smallest complete implementation that satisfies the request.
+3. Create or update the necessary files only.
+4. Reuse existing patterns, naming, and architecture already present in the repo.
+5. Add brief usage notes, edge cases, and follow-up improvements.
+
+## Rules
+- Prefer incremental changes over large rewrites.
+- Match the project's conventions.
+- Include basic validation and error handling.
+- If tests exist nearby, add or update them when appropriate.

package/.agent/workflows/debug.md

@@ -0,0 +1,28 @@
+---
+description: Find the real root cause, not just the first visible symptom
+---
+
+## Goal
+Find the real root cause, not just the first visible symptom.
+
+## Workflow
+1. Summarize the bug, expected behavior, and actual behavior.
+2. Gather evidence from logs, stack traces, code paths, config, and recent changes.
+3. List the top hypotheses ranked by likelihood.
+4. Eliminate hypotheses using direct evidence.
+5. Identify the root cause.
+6. Propose the smallest safe fix.
+7. Suggest how to verify the fix and prevent regressions.
+
+## Output format
+- Symptom
+- Evidence
+- Hypotheses
+- Root cause
+- Fix
+- Verification
+
+## Rules
+- Do not guess when evidence is missing; say what must be checked.
+- Prefer deterministic reproduction steps.
+- Mention any hidden risk or side effect of the fix.

package/.agent/workflows/deploy.md

@@ -0,0 +1,19 @@
+---
+description: Deployment steps, release preparation, environment setup, and CI/CD guidance
+---
+
+## Goal
+Guide deployment and release preparation with minimal risk.
+
+## Workflow
+1. Review the current deployment setup and target environment.
+2. Identify deployment prerequisites (env vars, secrets, dependencies).
+3. Outline deployment steps in order.
+4. Suggest rollback procedures.
+5. Recommend monitoring and verification steps post-deployment.
+
+## Rules
+- Always include rollback instructions.
+- Verify environment variables and secrets are documented.
+- Suggest smoke tests after deployment.
+- Consider zero-downtime strategies when applicable.

package/.agent/workflows/enhance.md

@@ -0,0 +1,18 @@
+---
+description: Improve an existing implementation without breaking working behavior
+---
+
+## Goal
+Improve an existing implementation without breaking working behavior.
+
+## Workflow
+1. Understand the current state and pain points.
+2. Identify high-impact improvements in quality, maintainability, performance, reliability, or UX.
+3. Prioritize improvements by value versus effort.
+4. Implement or recommend the top changes.
+5. Explain tradeoffs and validation steps.
+
+## Rules
+- Preserve behavior unless the user asked for a behavior change.
+- Prefer small, meaningful upgrades over broad rewrites.
+- If performance is discussed, explain where the gain comes from.

package/.agent/workflows/orchestrate.md

@@ -0,0 +1,19 @@
+---
+description: Coordinate multi-step workflows across multiple roles, files, systems, or parallel workstreams
+---
+
+## Goal
+Coordinate a multi-step plan across multiple roles, files, systems, or parallel workstreams.
+
+## Workflow
+1. Break down the high-level objective into distinct phases.
+2. Identify dependencies between phases.
+3. Assign clear responsibilities for each phase.
+4. Outline parallel workstreams where possible.
+5. Provide checkpoints and validation steps between phases.
+
+## Rules
+- Make dependencies explicit.
+- Identify bottlenecks early.
+- Suggest parallel execution where safe.
+- Include rollback or recovery steps for each phase.

package/.agent/workflows/plan.md

@@ -0,0 +1,19 @@
+---
+description: Create a concrete implementation plan with milestones and task breakdown
+---
+
+## Goal
+Create a concrete implementation plan with milestones and task breakdown.
+
+## Workflow
+1. Understand the feature or change request.
+2. Break it down into logical milestones.
+3. For each milestone, list specific tasks.
+4. Identify risks and dependencies.
+5. Suggest an order of implementation.
+
+## Rules
+- Keep tasks small and testable.
+- Identify blockers early.
+- Suggest incremental delivery where possible.
+- Include testing and documentation tasks.

package/.agent/workflows/preview.md

@@ -0,0 +1,19 @@
+---
+description: Preview expected output, UX, copy, interaction flow, or generated content
+---
+
+## Goal
+Preview expected output, UX, copy, interaction flow, or generated content before implementation.
+
+## Workflow
+1. Understand what needs to be previewed (UI, API response, user flow, etc.).
+2. Generate a mockup, wireframe, or sample output.
+3. Highlight key interactions or decision points.
+4. Suggest alternatives or improvements.
+5. Provide implementation notes if needed.
+
+## Rules
+- Focus on user experience and clarity.
+- Show realistic data, not placeholder text.
+- Highlight edge cases in the preview.
+- Suggest accessibility considerations.

package/.agent/workflows/status.md

@@ -0,0 +1,19 @@
+---
+description: Get current project status summary, progress snapshot, repo overview, and outstanding work
+---
+
+## Goal
+Provide a current project status summary, progress snapshot, repo overview, and outstanding work.
+
+## Workflow
+1. Scan the repository structure and key files.
+2. Identify completed features and in-progress work.
+3. List outstanding tasks or known issues.
+4. Summarize recent changes (from git history if available).
+5. Suggest next steps or priorities.
+
+## Rules
+- Be concise and factual.
+- Highlight blockers or risks.
+- Use git history when available.
+- Suggest actionable next steps.

package/.agent/workflows/test.md

@@ -0,0 +1,19 @@
+---
+description: Write tests, test strategy, coverage improvements, and validation steps
+---
+
+## Goal
+Write tests, test strategy, coverage improvements, and validation steps.
+
+## Workflow
+1. Understand what needs to be tested (feature, bug fix, edge case).
+2. Identify the appropriate test type (unit, integration, e2e).
+3. Write test cases covering happy path and edge cases.
+4. Suggest coverage improvements if applicable.
+5. Provide instructions to run the tests.
+
+## Rules
+- Test behavior, not implementation details.
+- Cover edge cases and error conditions.
+- Keep tests fast and isolated.
+- Use descriptive test names.

package/.agent/workflows/ui-ux-pro-max.md

@@ -0,0 +1,20 @@
+---
+description: Advanced UI/UX improvements, layout optimization, design critique, copy refinement, and interaction design
+---
+
+## Goal
+Provide advanced UI/UX improvements, layout optimization, design critique, copy refinement, and interaction design.
+
+## Workflow
+1. Review the current UI/UX implementation.
+2. Identify usability issues, visual inconsistencies, or accessibility gaps.
+3. Suggest specific improvements with rationale.
+4. Provide mockups, wireframes, or code examples.
+5. Highlight accessibility and responsive design considerations.
+
+## Rules
+- Focus on user needs and usability.
+- Suggest incremental improvements, not full redesigns.
+- Consider accessibility (WCAG guidelines).
+- Provide mobile and desktop considerations.
+- Use clear, concise copy.

package/.cursor/rules/brainstorm.mdc

@@ -0,0 +1,27 @@
+---
+description: "Use when the user wants ideation, option generation, feature exploration, or types /brainstorm."
+globs: ""
+alwaysApply: false
+---
+
+## Goal
+Help the user explore many realistic options before implementation.
+
+## Workflow
+1. Restate the problem in one or two sentences.
+2. Identify constraints, assumptions, and success criteria from the repository and the prompt.
+3. Produce 3-7 strong options with pros, cons, complexity, and risks.
+4. Call out the most practical option and the boldest option.
+5. End with a recommended next step or implementation path.
+
+## Output format
+- Problem framing
+- Constraints
+- Options
+- Recommendation
+- Next step
+
+## Rules
+- Prefer practical ideas grounded in the current project.
+- Avoid pretending uncertain assumptions are facts.
+- If code context matters, inspect the repo structure first.

package/.cursor/rules/clean.mdc

@@ -0,0 +1,51 @@
+---
+description: "Use when the user wants to clean up junk files, temporary files, AI-generated artifacts, cache, or types /clean."
+globs: ""
+alwaysApply: false
+---
+
+## Goal
+Identify and remove unnecessary files generated by AI, build processes, or development tools without affecting the working codebase.
+
+## Workflow
+1. Scan the project for common junk file patterns (temp files, logs, cache, node_modules, build artifacts).
+2. Identify AI-generated files that may be redundant or outdated.
+3. Present a clear list of files to be removed with their sizes and reasons.
+4. Ask for confirmation before deletion.
+5. Remove approved files and report the space saved.
+6. Suggest .gitignore updates if needed.
+
+## Common Junk Patterns
+- Temporary files: `*.tmp`, `*.temp`, `*.bak`, `*.swp`, `*~`
+- Log files: `*.log`, `*.log.*`, `debug.log`, `error.log`
+- Cache directories: `.cache/`, `__pycache__/`, `.pytest_cache/`, `.mypy_cache/`
+- Build artifacts: `dist/`, `build/`, `*.pyc`, `*.pyo`, `*.class`, `*.o`
+- Node modules: `node_modules/` (if not needed)
+- IDE files: `.vscode/`, `.idea/` (if not in .gitignore)
+- OS files: `.DS_Store`, `Thumbs.db`, `desktop.ini`
+- AI artifacts: Duplicate markdown files, unused generated code, test outputs
+
+## Safety Rules
+- Never delete files in version control (check git status first).
+- Never delete configuration files (.env, config.json, etc.) unless explicitly requested.
+- Never delete source code without explicit confirmation.
+- Always show what will be deleted before proceeding.
+- Preserve .gitignore and other dot files unless they're clearly junk.
+- Ask before removing entire directories.
+
+## Output Format
+```
+Files to clean:
+1. [Category] path/to/file (size) - Reason
+2. [Category] path/to/file (size) - Reason
+...
+
+Total space to recover: XX MB
+
+Proceed with deletion? (y/n)
+```
+
+## Follow-up Actions
+- Update .gitignore to prevent future junk accumulation
+- Suggest cleanup scripts for recurring patterns
+- Recommend build tool configurations to reduce artifacts

package/.cursor/rules/debug.mdc

@@ -0,0 +1,30 @@
+---
+description: "Use when the user wants root-cause analysis for a bug, failing command, broken behavior, error log, or types /debug."
+globs: ""
+alwaysApply: false
+---
+
+## Goal
+Find the real root cause, not just the first visible symptom.
+
+## Workflow
+1. Summarize the bug, expected behavior, and actual behavior.
+2. Gather evidence from logs, stack traces, code paths, config, and recent changes.
+3. List the top hypotheses ranked by likelihood.
+4. Eliminate hypotheses using direct evidence.
+5. Identify the root cause.
+6. Propose the smallest safe fix.
+7. Suggest how to verify the fix and prevent regressions.
+
+## Output format
+- Symptom
+- Evidence
+- Hypotheses
+- Root cause
+- Fix
+- Verification
+
+## Rules
+- Do not guess when evidence is missing; say what must be checked.
+- Prefer deterministic reproduction steps.
+- Mention any hidden risk or side effect of the fix.

package/.cursor/rules/enhance.mdc

@@ -0,0 +1,20 @@
+---
+description: "Use when the user wants to improve an existing feature, refactor code, optimize UX or performance, tighten security, or types /enhance."
+globs: ""
+alwaysApply: false
+---
+
+## Goal
+Improve an existing implementation without breaking working behavior.
+
+## Workflow
+1. Understand the current state and pain points.
+2. Identify high-impact improvements in quality, maintainability, performance, reliability, or UX.
+3. Prioritize improvements by value versus effort.
+4. Implement or recommend the top changes.
+5. Explain tradeoffs and validation steps.
+
+## Rules
+- Preserve behavior unless the user asked for a behavior change.
+- Prefer small, meaningful upgrades over broad rewrites.
+- If performance is discussed, explain where the gain comes from.

package/.kiro/skills/clean/SKILL.md

@@ -0,0 +1,50 @@
+---
+name: clean
+description: Use when the user wants to clean up junk files, temporary files, AI-generated artifacts, cache, or types /clean.
+---
+
+## Goal
+Identify and remove unnecessary files generated by AI, build processes, or development tools without affecting the working codebase.
+
+## Workflow
+1. Scan the project for common junk file patterns (temp files, logs, cache, node_modules, build artifacts).
+2. Identify AI-generated files that may be redundant or outdated.
+3. Present a clear list of files to be removed with their sizes and reasons.
+4. Ask for confirmation before deletion.
+5. Remove approved files and report the space saved.
+6. Suggest .gitignore updates if needed.
+
+## Common Junk Patterns
+- Temporary files: `*.tmp`, `*.temp`, `*.bak`, `*.swp`, `*~`
+- Log files: `*.log`, `*.log.*`, `debug.log`, `error.log`
+- Cache directories: `.cache/`, `__pycache__/`, `.pytest_cache/`, `.mypy_cache/`
+- Build artifacts: `dist/`, `build/`, `*.pyc`, `*.pyo`, `*.class`, `*.o`
+- Node modules: `node_modules/` (if not needed)
+- IDE files: `.vscode/`, `.idea/` (if not in .gitignore)
+- OS files: `.DS_Store`, `Thumbs.db`, `desktop.ini`
+- AI artifacts: Duplicate markdown files, unused generated code, test outputs
+
+## Safety Rules
+- Never delete files in version control (check git status first).
+- Never delete configuration files (.env, config.json, etc.) unless explicitly requested.
+- Never delete source code without explicit confirmation.
+- Always show what will be deleted before proceeding.
+- Preserve .gitignore and other dot files unless they're clearly junk.
+- Ask before removing entire directories.
+
+## Output Format
+```
+Files to clean:
+1. [Category] path/to/file (size) - Reason
+2. [Category] path/to/file (size) - Reason
+...
+
+Total space to recover: XX MB
+
+Proceed with deletion? (y/n)
+```
+
+## Follow-up Actions
+- Update .gitignore to prevent future junk accumulation
+- Suggest cleanup scripts for recurring patterns
+- Recommend build tool configurations to reduce artifacts

package/README.md

@@ -1,6 +1,6 @@
 # 🚀 AI Agent Skills
 
-Professional AI agent skills for Kiro, Cursor, Windsurf, and other AI-powered IDEs. 11 battle-tested workflows to supercharge your development.
+Professional AI agent skills for Kiro, Cursor, Antigravity, and other AI-powered IDEs. 12 battle-tested workflows to supercharge your development.
 
 [![npm version](https://img.shields.io/npm/v/@votruongdanh/ai-agent-skills.svg)](https://www.npmjs.com/package/@votruongdanh/ai-agent-skills)
 [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
@@ -32,11 +32,12 @@ The CLI automatically detects your IDE and installs to the correct location:
 
 No configuration needed - just run the install command!
 
-## 📦 11 Professional Skills
+## 📦 12 Professional Skills
 
 | Skill | Command | Use Case |
 |-------|---------|----------|
 | **Brainstorm** | `/brainstorm` | Generate ideas and explore features |
+| **Clean** | `/clean` | Remove junk files and AI artifacts |
 | **Create** | `/create` | Build new features from scratch |
 | **Debug** | `/debug` | Find and fix bugs systematically |
 | **Deploy** | `/deploy` | Deployment and CI/CD guidance |

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@votruongdanh/ai-agent-skills",
-  "version": "1.4.0",
-  "description": "Professional AI Agent Skills - 11 powerful workflows for Antigravity, Kiro, Cursor, Windsurf, Continue, Cody, and other AI IDEs",
+  "version": "1.5.1",
+  "description": "Professional AI Agent Skills - 12 powerful workflows for Antigravity, Kiro, Cursor, Windsurf, Continue, Cody, and other AI IDEs",
   "main": "index.js",
   "bin": {
     "ai-skills": "bin/cli.js"
@@ -47,6 +47,8 @@
   "homepage": "https://github.com/votruongdanh/ai-agent-skills#readme",
   "files": [
     ".kiro",
+    ".cursor",
+    ".agent",
     "bin",
     "index.js",
     "README.md"