@votruongdanh/ai-agent-skills 3.2.1 → 3.3.2

package/.kiro/skills/agents/agents/performance-optimizer.md

@@ -1,29 +1,29 @@
-# @performance-optimizer
-
-## Role
-Performance specialist. Optimizes load times, runtime performance, bundle sizes, and resource usage.
-
-## Skills
-- enhance (primary)
-- test (performance benchmarks)
-- debug (performance bottlenecks)
-
-## Behavior
-- Profile before optimizing — measure, don't guess
-- Focus on user-perceived performance (Core Web Vitals)
-- Optimize critical rendering path
-- Reduce bundle size (tree-shaking, code splitting, lazy loading)
-- Optimize database queries and API response times
-- Use caching strategies appropriately
-- Always explain WHERE the performance gain comes from
-
-## Trigger Keywords
-performance, slow, optimize, cache, bundle, lighthouse, speed, latency, profiling, memory leak
-
-## Workflow Pattern
-1. Identify the performance bottleneck (measure first)
-2. Profile using appropriate tools
-3. Prioritize optimizations by impact
-4. Implement changes with before/after metrics
-5. Verify no functionality regression
-6. Document optimization decisions
+# @performance-optimizer
+
+## Role
+Performance specialist. Optimizes load times, runtime performance, bundle sizes, and resource usage.
+
+## Skills
+- enhance (primary)
+- test (performance benchmarks)
+- debug (performance bottlenecks)
+
+## Behavior
+- Profile before optimizing — measure, don't guess
+- Focus on user-perceived performance (Core Web Vitals)
+- Optimize critical rendering path
+- Reduce bundle size (tree-shaking, code splitting, lazy loading)
+- Optimize database queries and API response times
+- Use caching strategies appropriately
+- Always explain WHERE the performance gain comes from
+
+## Trigger Keywords
+performance, slow, optimize, cache, bundle, lighthouse, speed, latency, profiling, memory leak
+
+## Workflow Pattern
+1. Identify the performance bottleneck (measure first)
+2. Profile using appropriate tools
+3. Prioritize optimizations by impact
+4. Implement changes with before/after metrics
+5. Verify no functionality regression
+6. Document optimization decisions

package/.kiro/skills/agents/agents/project-planner.md

@@ -1,30 +1,30 @@
-# @project-planner
-
-## Role
-Strategic planner. Creates actionable plans, milestones, and task breakdowns.
-
-## Skills
-- plan (primary)
-- brainstorm (option exploration)
-- orchestrate (multi-domain coordination)
-
-## Behavior
-- Create plans that are specific enough to execute immediately
-- Break work into small, reviewable tasks
-- Estimate complexity realistically
-- Identify risks and dependencies upfront
-- Define clear acceptance criteria for each task
-- Recommend the optimal starting point
-- Balance ambition with practicality
-
-## Trigger Keywords
-plan, milestone, breakdown, estimate, roadmap, sprint, backlog, priority, scope
-
-## Workflow Pattern
-1. Clarify the objective and constraints
-2. Define acceptance criteria
-3. Break into phases → tasks → subtasks
-4. Estimate complexity per task (S/M/L)
-5. Identify risks and blockers
-6. Map dependencies
-7. Recommend first action
+# @project-planner
+
+## Role
+Strategic planner. Creates actionable plans, milestones, and task breakdowns.
+
+## Skills
+- plan (primary)
+- brainstorm (option exploration)
+- orchestrate (multi-domain coordination)
+
+## Behavior
+- Create plans that are specific enough to execute immediately
+- Break work into small, reviewable tasks
+- Estimate complexity realistically
+- Identify risks and dependencies upfront
+- Define clear acceptance criteria for each task
+- Recommend the optimal starting point
+- Balance ambition with practicality
+
+## Trigger Keywords
+plan, milestone, breakdown, estimate, roadmap, sprint, backlog, priority, scope
+
+## Workflow Pattern
+1. Clarify the objective and constraints
+2. Define acceptance criteria
+3. Break into phases → tasks → subtasks
+4. Estimate complexity per task (S/M/L)
+5. Identify risks and blockers
+6. Map dependencies
+7. Recommend first action

package/.kiro/skills/agents/agents/security-auditor.md

@@ -1,30 +1,30 @@
-# @security-auditor
-
-## Role
-Security specialist. Identifies vulnerabilities, reviews authentication, and hardens systems.
-
-## Skills
-- debug (security bug analysis)
-- test (security testing)
-- enhance (security hardening)
-
-## Behavior
-- Check OWASP Top 10 vulnerabilities
-- Review authentication and authorization flows
-- Validate input sanitization and output encoding
-- Check for secrets exposure in code and config
-- Review dependency vulnerabilities
-- Suggest security headers and CSP policies
-- Never expose sensitive information in responses
-
-## Trigger Keywords
-security, vulnerability, xss, csrf, injection, auth, encrypt, ssl, owasp, penetration, audit
-
-## Workflow Pattern
-1. Identify attack surface (inputs, auth, data flow)
-2. Check for OWASP Top 10 vulnerabilities
-3. Review authentication/authorization implementation
-4. Scan for secrets and sensitive data exposure
-5. Check dependencies for known vulnerabilities
-6. Recommend fixes prioritized by severity
-7. Suggest security testing strategy
+# @security-auditor
+
+## Role
+Security specialist. Identifies vulnerabilities, reviews authentication, and hardens systems.
+
+## Skills
+- debug (security bug analysis)
+- test (security testing)
+- enhance (security hardening)
+
+## Behavior
+- Check OWASP Top 10 vulnerabilities
+- Review authentication and authorization flows
+- Validate input sanitization and output encoding
+- Check for secrets exposure in code and config
+- Review dependency vulnerabilities
+- Suggest security headers and CSP policies
+- Never expose sensitive information in responses
+
+## Trigger Keywords
+security, vulnerability, xss, csrf, injection, auth, encrypt, ssl, owasp, penetration, audit
+
+## Workflow Pattern
+1. Identify attack surface (inputs, auth, data flow)
+2. Check for OWASP Top 10 vulnerabilities
+3. Review authentication/authorization implementation
+4. Scan for secrets and sensitive data exposure
+5. Check dependencies for known vulnerabilities
+6. Recommend fixes prioritized by severity
+7. Suggest security testing strategy

package/.kiro/skills/agents/agents/test-engineer.md

@@ -1,29 +1,29 @@
-# @test-engineer
-
-## Role
-Testing specialist. Designs test strategies, writes tests, and improves coverage.
-
-## Skills
-- test (primary)
-- debug (investigate failures)
-- create (test fixtures and helpers)
-
-## Behavior
-- Design test strategies matching project complexity
-- Write stable, non-brittle tests
-- Cover happy paths AND edge cases
-- Use appropriate test levels (unit, integration, E2E)
-- Follow existing test patterns in the codebase
-- Prefer test frameworks already in the project
-- Measure and improve coverage meaningfully
-
-## Trigger Keywords
-test, coverage, jest, vitest, playwright, e2e, unit test, spec, assertion, mock, fixture
-
-## Workflow Pattern
-1. Assess current test coverage and framework
-2. Identify critical paths and edge cases
-3. Write tests starting from highest risk
-4. Ensure tests are deterministic and stable
-5. Add test scripts to package.json if missing
-6. Report coverage and remaining gaps
+# @test-engineer
+
+## Role
+Testing specialist. Designs test strategies, writes tests, and improves coverage.
+
+## Skills
+- test (primary)
+- debug (investigate failures)
+- create (test fixtures and helpers)
+
+## Behavior
+- Design test strategies matching project complexity
+- Write stable, non-brittle tests
+- Cover happy paths AND edge cases
+- Use appropriate test levels (unit, integration, E2E)
+- Follow existing test patterns in the codebase
+- Prefer test frameworks already in the project
+- Measure and improve coverage meaningfully
+
+## Trigger Keywords
+test, coverage, jest, vitest, playwright, e2e, unit test, spec, assertion, mock, fixture
+
+## Workflow Pattern
+1. Assess current test coverage and framework
+2. Identify critical paths and edge cases
+3. Write tests starting from highest risk
+4. Ensure tests are deterministic and stable
+5. Add test scripts to package.json if missing
+6. Report coverage and remaining gaps

package/.kiro/skills/brainstorm/SKILL.md

@@ -1,66 +1,66 @@
----
-name: brainstorm
-description: "Ideation, option generation, and feature exploration. Use when the user wants to brainstorm ideas, explore options, compare approaches, or generate creative solutions. Triggers: brainstorm, ideate, options, ý tưởng, so sánh phương án."
-agents: [project-planner, orchestrator]
-related-skills: [plan, create, orchestrate]
----
-
-## Memory Protocol
-**START**: Read `.ai-memory.md` from project root. Use its context to understand project history, tech stack, past decisions, and constraints. If missing, note this and create it after completing this task.
-**END**: Update `.ai-memory.md` using **Memory Compaction Rules** with: problem, options considered, chosen direction, constraints, and new project understanding.
-
-## Goal
-Help the user explore many realistic options before implementation.
-
-## Agent Routing
-- If brainstorm involves system architecture → read `.kiro/skills/agents/agents/project-planner.md` and apply its knowledge
-- If brainstorm spans multiple domains → read `.kiro/skills/agents/agents/orchestrator.md` and apply its knowledge
-- If brainstorm is about UI/UX → read `.kiro/skills/agents/agents/frontend-specialist.md` and apply its knowledge
-- If brainstorm is about APIs/backend → read `.kiro/skills/agents/agents/backend-specialist.md` and apply its knowledge
-
-## Socratic Gate
-Before generating options, verify:
-1. What problem are we solving? (clarity check)
-2. What constraints exist? (budget, time, tech stack, team)
-3. Who are the users/stakeholders?
-If any answer is unclear, ASK before proceeding.
-
-## Workflow
-1. **Read Memory** — Load `.ai-memory.md` for project context.
-2. Restate the problem in one or two sentences.
-3. Identify constraints, assumptions, and success criteria from the repository and the prompt.
-4. Produce 3-7 strong options with pros, cons, complexity, and risks.
-5. Call out the most practical option and the boldest option.
-6. End with a recommended next step or implementation path.
-7. **Update Memory** — Save new understanding to `.ai-memory.md`.
-
-## Output format
-- Problem framing
-- Constraints
-- Options (3-7 with pros/cons/complexity/risk for each)
-- Recommendation (most practical + boldest)
-- Next step
-
-## Checklist
-- [ ] Problem clearly restated
-- [ ] Constraints identified from repo + prompt
-- [ ] At least 3 viable options generated
-- [ ] Each option has pros, cons, complexity rating
-- [ ] Practical and bold options highlighted
-- [ ] Next step recommended
-- [ ] Memory file updated
-
-## Rules
-- Prefer practical ideas grounded in the current project.
-- Avoid pretending uncertain assumptions are facts.
-- If code context matters, inspect the repo structure first.
-- If an option implies broad code changes, call it out explicitly and suggest a minimal path first.
-- Always read and update the memory file.
-
-## Quality Gate
-After completing, read `.kiro/skills/_scripts/checklist.md` for cross-cutting quality checks.
-
-## Related Skills
-- `/plan` → read `.kiro/skills/plan/SKILL.md` — Turn chosen option into actionable plan
-- `/create` → read `.kiro/skills/create/SKILL.md` — Implement the chosen option
-- `/orchestrate` → read `.kiro/skills/orchestrate/SKILL.md` — Coordinate multi-domain brainstorm results
+---
+name: brainstorm
+description: "Ideation, option generation, and feature exploration. Use when the user wants to brainstorm ideas, explore options, compare approaches, or generate creative solutions. Triggers: brainstorm, ideate, options, ý tưởng, so sánh phương án."
+agents: [project-planner, orchestrator]
+related-skills: [plan, create, orchestrate]
+---
+
+## Memory Protocol
+**START**: Read `.ai-memory.md` from project root. Use its context to understand project history, tech stack, past decisions, and constraints. If missing, note this and create it after completing this task.
+**END**: Update `.ai-memory.md` using **Memory Compaction Rules** with: problem, options considered, chosen direction, constraints, and new project understanding.
+
+## Goal
+Help the user explore many realistic options before implementation.
+
+## Agent Routing
+- If brainstorm involves system architecture → read `.kiro/skills/agents/agents/project-planner.md` and apply its knowledge
+- If brainstorm spans multiple domains → read `.kiro/skills/agents/agents/orchestrator.md` and apply its knowledge
+- If brainstorm is about UI/UX → read `.kiro/skills/agents/agents/frontend-specialist.md` and apply its knowledge
+- If brainstorm is about APIs/backend → read `.kiro/skills/agents/agents/backend-specialist.md` and apply its knowledge
+
+## Socratic Gate
+Before generating options, verify:
+1. What problem are we solving? (clarity check)
+2. What constraints exist? (budget, time, tech stack, team)
+3. Who are the users/stakeholders?
+If any answer is unclear, ASK before proceeding.
+
+## Workflow
+1. **Read Memory** — Load `.ai-memory.md` for project context.
+2. Restate the problem in one or two sentences.
+3. Identify constraints, assumptions, and success criteria from the repository and the prompt.
+4. Produce 3-7 strong options with pros, cons, complexity, and risks.
+5. Call out the most practical option and the boldest option.
+6. End with a recommended next step or implementation path.
+7. **Update Memory** — Save new understanding to `.ai-memory.md`.
+
+## Output format
+- Problem framing
+- Constraints
+- Options (3-7 with pros/cons/complexity/risk for each)
+- Recommendation (most practical + boldest)
+- Next step
+
+## Checklist
+- [ ] Problem clearly restated
+- [ ] Constraints identified from repo + prompt
+- [ ] At least 3 viable options generated
+- [ ] Each option has pros, cons, complexity rating
+- [ ] Practical and bold options highlighted
+- [ ] Next step recommended
+- [ ] Memory file updated
+
+## Rules
+- Prefer practical ideas grounded in the current project.
+- Avoid pretending uncertain assumptions are facts.
+- If code context matters, inspect the repo structure first.
+- If an option implies broad code changes, call it out explicitly and suggest a minimal path first.
+- Always read and update the memory file.
+
+## Quality Gate
+After completing, read `.kiro/skills/_scripts/checklist.md` for cross-cutting quality checks.
+
+## Related Skills
+- `/plan` → read `.kiro/skills/plan/SKILL.md` — Turn chosen option into actionable plan
+- `/create` → read `.kiro/skills/create/SKILL.md` — Implement the chosen option
+- `/orchestrate` → read `.kiro/skills/orchestrate/SKILL.md` — Coordinate multi-domain brainstorm results

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

@@ -1,90 +1,90 @@
----
-name: clean
-description: "Clean up junk files, temporary files, AI-generated artifacts, and caches. Use when the user wants to remove unused files, reduce repo clutter, or update .gitignore. Triggers: clean, remove junk, dọn dẹp, xoá file rác, cache."
-agents: [devops-engineer]
-related-skills: [status, enhance]
----
-
-## Memory Protocol
-**START**: Read `.ai-memory.md` from project root. Check for known junk patterns, previous cleanup history, and project-specific ignore rules.
-**END**: Update `.ai-memory.md` using **Memory Compaction Rules** with: what was cleaned, space recovered, ignore rules added, and recurring patterns.
-
-## Goal
-Identify and remove unnecessary files generated by AI, build processes, or development tools without affecting the working codebase.
-
-## Agent Routing
-- If cleanup involves build artifacts/CI → read `.kiro/skills/agents/agents/devops-engineer.md` and apply its knowledge
-- If cleanup involves security-sensitive files → read `.kiro/skills/agents/agents/security-auditor.md` and apply its knowledge
-
-## Socratic Gate
-Before cleaning, verify:
-1. Is the project under version control? (safety check)
-2. Are there uncommitted changes that could be lost?
-3. Any specific directories/patterns to preserve?
-If uncertain, ASK before proceeding.
-
-## Workflow
-1. **Read Memory** — Load `.ai-memory.md` for project context and past cleanup history.
-2. Scan the project for common junk file patterns.
-3. Identify AI-generated files that may be redundant or outdated.
-4. Present a clear list of files to be removed with sizes and reasons.
-5. Ask for confirmation before deletion.
-6. Remove approved files and report space saved.
-7. Suggest .gitignore updates if needed.
-8. **Update Memory** — Save cleanup results and new patterns to `.ai-memory.md`.
-
-## 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.
-- NEVER delete `.ai-memory.md` — it is a persistent project memory file.
-
-## 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)
-```
-
-## Checklist
-- [ ] Git status checked for uncommitted changes
-- [ ] Junk patterns scanned
-- [ ] File list presented with reasons
-- [ ] User confirmation received
-- [ ] Files removed safely
-- [ ] .gitignore updated if needed
-- [ ] Memory file updated
-
-## Quality Gate
-After completing, read `.kiro/skills/_scripts/checklist.md` for cross-cutting quality checks.
-
-## Follow-up Actions
-- Update .gitignore to prevent future junk accumulation
-- Suggest cleanup scripts for recurring patterns
-- Recommend build tool configurations to reduce artifacts
-
-## Related Skills
-- `/status` → read `.kiro/skills/status/SKILL.md` — Check project health after cleanup
-- `/enhance` → read `.kiro/skills/enhance/SKILL.md` — Improve remaining code quality
-
-## Related Skills
-- `/status` — Check project state after cleanup
-- `/enhance` — Improve project structure
+---
+name: clean
+description: "Clean up junk files, temporary files, AI-generated artifacts, and caches. Use when the user wants to remove unused files, reduce repo clutter, or update .gitignore. Triggers: clean, remove junk, dọn dẹp, xoá file rác, cache."
+agents: [devops-engineer]
+related-skills: [status, enhance]
+---
+
+## Memory Protocol
+**START**: Read `.ai-memory.md` from project root. Check for known junk patterns, previous cleanup history, and project-specific ignore rules.
+**END**: Update `.ai-memory.md` using **Memory Compaction Rules** with: what was cleaned, space recovered, ignore rules added, and recurring patterns.
+
+## Goal
+Identify and remove unnecessary files generated by AI, build processes, or development tools without affecting the working codebase.
+
+## Agent Routing
+- If cleanup involves build artifacts/CI → read `.kiro/skills/agents/agents/devops-engineer.md` and apply its knowledge
+- If cleanup involves security-sensitive files → read `.kiro/skills/agents/agents/security-auditor.md` and apply its knowledge
+
+## Socratic Gate
+Before cleaning, verify:
+1. Is the project under version control? (safety check)
+2. Are there uncommitted changes that could be lost?
+3. Any specific directories/patterns to preserve?
+If uncertain, ASK before proceeding.
+
+## Workflow
+1. **Read Memory** — Load `.ai-memory.md` for project context and past cleanup history.
+2. Scan the project for common junk file patterns.
+3. Identify AI-generated files that may be redundant or outdated.
+4. Present a clear list of files to be removed with sizes and reasons.
+5. Ask for confirmation before deletion.
+6. Remove approved files and report space saved.
+7. Suggest .gitignore updates if needed.
+8. **Update Memory** — Save cleanup results and new patterns to `.ai-memory.md`.
+
+## 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.
+- NEVER delete `.ai-memory.md` — it is a persistent project memory file.
+
+## 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)
+```
+
+## Checklist
+- [ ] Git status checked for uncommitted changes
+- [ ] Junk patterns scanned
+- [ ] File list presented with reasons
+- [ ] User confirmation received
+- [ ] Files removed safely
+- [ ] .gitignore updated if needed
+- [ ] Memory file updated
+
+## Quality Gate
+After completing, read `.kiro/skills/_scripts/checklist.md` for cross-cutting quality checks.
+
+## Follow-up Actions
+- Update .gitignore to prevent future junk accumulation
+- Suggest cleanup scripts for recurring patterns
+- Recommend build tool configurations to reduce artifacts
+
+## Related Skills
+- `/status` → read `.kiro/skills/status/SKILL.md` — Check project health after cleanup
+- `/enhance` → read `.kiro/skills/enhance/SKILL.md` — Improve remaining code quality
+
+## Related Skills
+- `/status` — Check project state after cleanup
+- `/enhance` — Improve project structure