@votruongdanh/ai-agent-skills 3.2.1 → 3.3.2

package/.kiro/skills/create/SKILL.md

@@ -1,63 +1,63 @@
----
-name: create
-description: "Build new features, files, components, endpoints, pages, or scripts. Use when the user wants to create something new in the codebase. Triggers: create, build, add, new, scaffold, tạo, thêm mới, tạo trang, tạo API."
-agents: [backend-specialist, frontend-specialist, database-architect]
-related-skills: [plan, test, debug]
----
-
-## Memory Protocol
-**START**: Read `.ai-memory.md` from project root. Check tech stack, coding conventions, existing patterns, architecture decisions, and file structure notes.
-**END**: Update `.ai-memory.md` using **Memory Compaction Rules** with: what was created, files touched, patterns used, decisions, and follow-ups.
-
-## Goal
-Create a new implementation cleanly and with minimal disruption.
-
-## Agent Routing
-- If creating API/backend → read `.kiro/skills/agents/agents/backend-specialist.md` and apply its knowledge
-- If creating UI component/page → read `.kiro/skills/agents/agents/frontend-specialist.md` and apply its knowledge
-- If creating database schema/migration → read `.kiro/skills/agents/agents/database-architect.md` and apply its knowledge
-- If creating tests → read `.kiro/skills/agents/agents/test-engineer.md` and apply its knowledge
-- If creating deployment config → read `.kiro/skills/agents/agents/devops-engineer.md` and apply its knowledge
-
-## Socratic Gate
-Before creating, verify:
-1. What exactly should be created? (component, page, API, script?)
-2. Does something similar already exist in the project?
-3. What is the expected behavior/output?
-If any answer is unclear, ASK before proceeding.
-
-## Workflow
-1. **Read Memory** — Load `.ai-memory.md` for project context, conventions, and patterns.
-2. Understand the requested artifact and the existing project structure.
-3. Identify the smallest complete implementation that satisfies the request.
-4. Create or update the necessary files only.
-5. Reuse existing patterns, naming, and architecture already present in the repo.
-6. Include basic validation and error handling.
-7. Add brief usage notes, edge cases, and follow-up improvements.
-8. **Update Memory** — Save what was created, patterns used, and follow-up notes to `.ai-memory.md`.
-
-## Checklist
-- [ ] Requirement clearly understood
-- [ ] Existing patterns/conventions checked
-- [ ] Minimal files created/modified
-- [ ] Validation and error handling included
-- [ ] Project conventions matched (naming, structure)
-- [ ] Tests added if test framework exists
-- [ ] Usage notes provided
-- [ ] Memory file updated
-
-## 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.
-- Avoid changing unrelated files; if unsure about side effects, ASK before editing broadly.
-- 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` — Plan before creating complex features
-- `/test` → read `.kiro/skills/test/SKILL.md` — Write tests for new code
-- `/debug` → read `.kiro/skills/debug/SKILL.md` — Fix issues in newly created code
+---
+name: create
+description: "Build new features, files, components, endpoints, pages, or scripts. Use when the user wants to create something new in the codebase. Triggers: create, build, add, new, scaffold, tạo, thêm mới, tạo trang, tạo API."
+agents: [backend-specialist, frontend-specialist, database-architect]
+related-skills: [plan, test, debug]
+---
+
+## Memory Protocol
+**START**: Read `.ai-memory.md` from project root. Check tech stack, coding conventions, existing patterns, architecture decisions, and file structure notes.
+**END**: Update `.ai-memory.md` using **Memory Compaction Rules** with: what was created, files touched, patterns used, decisions, and follow-ups.
+
+## Goal
+Create a new implementation cleanly and with minimal disruption.
+
+## Agent Routing
+- If creating API/backend → read `.kiro/skills/agents/agents/backend-specialist.md` and apply its knowledge
+- If creating UI component/page → read `.kiro/skills/agents/agents/frontend-specialist.md` and apply its knowledge
+- If creating database schema/migration → read `.kiro/skills/agents/agents/database-architect.md` and apply its knowledge
+- If creating tests → read `.kiro/skills/agents/agents/test-engineer.md` and apply its knowledge
+- If creating deployment config → read `.kiro/skills/agents/agents/devops-engineer.md` and apply its knowledge
+
+## Socratic Gate
+Before creating, verify:
+1. What exactly should be created? (component, page, API, script?)
+2. Does something similar already exist in the project?
+3. What is the expected behavior/output?
+If any answer is unclear, ASK before proceeding.
+
+## Workflow
+1. **Read Memory** — Load `.ai-memory.md` for project context, conventions, and patterns.
+2. Understand the requested artifact and the existing project structure.
+3. Identify the smallest complete implementation that satisfies the request.
+4. Create or update the necessary files only.
+5. Reuse existing patterns, naming, and architecture already present in the repo.
+6. Include basic validation and error handling.
+7. Add brief usage notes, edge cases, and follow-up improvements.
+8. **Update Memory** — Save what was created, patterns used, and follow-up notes to `.ai-memory.md`.
+
+## Checklist
+- [ ] Requirement clearly understood
+- [ ] Existing patterns/conventions checked
+- [ ] Minimal files created/modified
+- [ ] Validation and error handling included
+- [ ] Project conventions matched (naming, structure)
+- [ ] Tests added if test framework exists
+- [ ] Usage notes provided
+- [ ] Memory file updated
+
+## 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.
+- Avoid changing unrelated files; if unsure about side effects, ASK before editing broadly.
+- 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` — Plan before creating complex features
+- `/test` → read `.kiro/skills/test/SKILL.md` — Write tests for new code
+- `/debug` → read `.kiro/skills/debug/SKILL.md` — Fix issues in newly created code

package/.kiro/skills/debug/SKILL.md

@@ -1,71 +1,71 @@
----
-name: debug
-description: "Root-cause analysis for bugs, failing commands, broken behavior, and error logs. Use when the user encounters errors, crashes, or unexpected behavior. Triggers: debug, fix, bug, error, crash, lỗi, sửa lỗi, hỏng, fail."
-agents: [debugger, backend-specialist, frontend-specialist]
-related-skills: [test, enhance, status]
----
-
-## Memory Protocol
-**START**: Read `.ai-memory.md` from project root. Check for known bugs, past fixes, tech stack details, common error patterns, and architecture notes.
-**END**: Update `.ai-memory.md` using **Memory Compaction Rules** with: bug, root cause, fix, files touched, lessons learned, and remaining risks.
-
-## Goal
-Find the real root cause, not just the first visible symptom.
-
-## Agent Routing
-- If bug is in API/server/backend → read `.kiro/skills/agents/agents/backend-specialist.md` and apply its knowledge
-- If bug is in UI/rendering/CSS → read `.kiro/skills/agents/agents/frontend-specialist.md` and apply its knowledge
-- If bug is in database/queries → read `.kiro/skills/agents/agents/database-architect.md` and apply its knowledge
-- If bug may be a security issue → read `.kiro/skills/agents/agents/security-auditor.md` and apply its knowledge
-- Default → read `.kiro/skills/agents/agents/debugger.md` and apply its systematic analysis
-
-## Socratic Gate
-Before debugging, verify:
-1. What is the expected behavior vs actual behavior?
-2. Is there a log, stacktrace, or error message?
-3. When did this start? (recent change, always broken, intermittent?)
-If any answer is missing, ASK before proceeding.
-
-## Workflow
-1. **Read Memory** — Load `.ai-memory.md` for project context and past bug history.
-2. Summarize the bug, expected behavior, and actual behavior.
-3. Gather evidence from logs, stack traces, code paths, config, and recent changes.
-4. List the top hypotheses ranked by likelihood.
-5. Eliminate hypotheses using direct evidence.
-6. Identify the root cause.
-7. Propose the smallest safe fix.
-8. Suggest how to verify the fix and prevent regressions.
-9. **Quality Gate** — Read `.kiro/skills/_scripts/checklist.md` and run cross-cutting quality checks.
-10. **Update Memory** — Save root cause, fix, and lessons to `.ai-memory.md`.
-
-## Output format
-- Symptom
-- Evidence collected
-- Hypotheses (ranked by likelihood)
-- Root cause
-- Fix (smallest safe change)
-- Verification steps
-- Regression prevention
-
-## Checklist
-- [ ] Bug clearly described (expected vs actual)
-- [ ] Evidence gathered (logs, stacktrace, code)
-- [ ] Hypotheses listed and ranked
-- [ ] Root cause confirmed with evidence
-- [ ] Fix is minimal and safe
-- [ ] No side effects introduced
-- [ ] Verification steps provided
-- [ ] Regression prevention suggested
-- [ ] Memory file updated
-
-## 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.
-- Avoid changing unrelated files; if a fix seems wide-impact, ASK before proceeding.
-- Always read and update the memory file.
-
-## Related Skills
-- `/test` → read `.kiro/skills/test/SKILL.md` — Write tests to prevent regression
-- `/enhance` → read `.kiro/skills/enhance/SKILL.md` — Improve code quality after fixing
-- `/status` → read `.kiro/skills/status/SKILL.md` — Check project health after fix
+---
+name: debug
+description: "Root-cause analysis for bugs, failing commands, broken behavior, and error logs. Use when the user encounters errors, crashes, or unexpected behavior. Triggers: debug, fix, bug, error, crash, lỗi, sửa lỗi, hỏng, fail."
+agents: [debugger, backend-specialist, frontend-specialist]
+related-skills: [test, enhance, status]
+---
+
+## Memory Protocol
+**START**: Read `.ai-memory.md` from project root. Check for known bugs, past fixes, tech stack details, common error patterns, and architecture notes.
+**END**: Update `.ai-memory.md` using **Memory Compaction Rules** with: bug, root cause, fix, files touched, lessons learned, and remaining risks.
+
+## Goal
+Find the real root cause, not just the first visible symptom.
+
+## Agent Routing
+- If bug is in API/server/backend → read `.kiro/skills/agents/agents/backend-specialist.md` and apply its knowledge
+- If bug is in UI/rendering/CSS → read `.kiro/skills/agents/agents/frontend-specialist.md` and apply its knowledge
+- If bug is in database/queries → read `.kiro/skills/agents/agents/database-architect.md` and apply its knowledge
+- If bug may be a security issue → read `.kiro/skills/agents/agents/security-auditor.md` and apply its knowledge
+- Default → read `.kiro/skills/agents/agents/debugger.md` and apply its systematic analysis
+
+## Socratic Gate
+Before debugging, verify:
+1. What is the expected behavior vs actual behavior?
+2. Is there a log, stacktrace, or error message?
+3. When did this start? (recent change, always broken, intermittent?)
+If any answer is missing, ASK before proceeding.
+
+## Workflow
+1. **Read Memory** — Load `.ai-memory.md` for project context and past bug history.
+2. Summarize the bug, expected behavior, and actual behavior.
+3. Gather evidence from logs, stack traces, code paths, config, and recent changes.
+4. List the top hypotheses ranked by likelihood.
+5. Eliminate hypotheses using direct evidence.
+6. Identify the root cause.
+7. Propose the smallest safe fix.
+8. Suggest how to verify the fix and prevent regressions.
+9. **Quality Gate** — Read `.kiro/skills/_scripts/checklist.md` and run cross-cutting quality checks.
+10. **Update Memory** — Save root cause, fix, and lessons to `.ai-memory.md`.
+
+## Output format
+- Symptom
+- Evidence collected
+- Hypotheses (ranked by likelihood)
+- Root cause
+- Fix (smallest safe change)
+- Verification steps
+- Regression prevention
+
+## Checklist
+- [ ] Bug clearly described (expected vs actual)
+- [ ] Evidence gathered (logs, stacktrace, code)
+- [ ] Hypotheses listed and ranked
+- [ ] Root cause confirmed with evidence
+- [ ] Fix is minimal and safe
+- [ ] No side effects introduced
+- [ ] Verification steps provided
+- [ ] Regression prevention suggested
+- [ ] Memory file updated
+
+## 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.
+- Avoid changing unrelated files; if a fix seems wide-impact, ASK before proceeding.
+- Always read and update the memory file.
+
+## Related Skills
+- `/test` → read `.kiro/skills/test/SKILL.md` — Write tests to prevent regression
+- `/enhance` → read `.kiro/skills/enhance/SKILL.md` — Improve code quality after fixing
+- `/status` → read `.kiro/skills/status/SKILL.md` — Check project health after fix

package/.kiro/skills/deploy/SKILL.md

@@ -1,66 +1,66 @@
----
-name: deploy
-description: "Deployment steps, release preparation, environment setup, CI/CD guidance, and production rollout. Use when the user wants to deploy, release, or set up infrastructure. Triggers: deploy, release, CI/CD, docker, production, triển khai, phát hành, đưa lên production."
-agents: [devops-engineer, security-auditor]
-related-skills: [test, status, plan]
----
-
-## Memory Protocol
-**START**: Read `.ai-memory.md` from project root. Check deployment history, target environments, known infrastructure, CI/CD setup, past deployment issues.
-**END**: Update `.ai-memory.md` using **Memory Compaction Rules** with: target, steps, env details, issues, rollback notes, and infra decisions.
-
-## Goal
-Prepare a safe, repeatable deployment or release plan.
-
-## Agent Routing
-- For infrastructure/CI/CD → read `.kiro/skills/agents/agents/devops-engineer.md` and apply its knowledge
-- For security review before deploy → read `.kiro/skills/agents/agents/security-auditor.md` and apply its knowledge
-- For database migrations → read `.kiro/skills/agents/agents/database-architect.md` and apply its knowledge
-- For performance validation → read `.kiro/skills/agents/agents/performance-optimizer.md` and apply its knowledge
-
-## Socratic Gate
-Before deploying, verify:
-1. What is the target environment? (staging, production, preview?)
-2. Are all tests passing?
-3. Are there database migrations or breaking changes?
-If any answer is unclear, ASK before proceeding.
-
-## Workflow
-1. **Read Memory** — Load `.ai-memory.md` for deployment history and environment details.
-2. Detect the app type, runtime, dependencies, and target environment.
-3. List prerequisites: secrets, env vars, build steps, infrastructure, database migrations, and health checks.
-4. Produce a deployment sequence from pre-checks to rollback.
-5. Call out risky steps explicitly.
-6. Include post-deploy verification and monitoring.
-7. **Quality Gate** — Read `.kiro/skills/_scripts/pre-deploy.md` for pre-deploy checklist, then `.kiro/skills/_scripts/checklist.md` for cross-cutting checks.
-8. **Update Memory** — Save deployment details and outcomes to `.ai-memory.md`.
-
-## Output format
-- Target environment
-- Preconditions
-- Deployment steps (numbered, with risk flags)
-- Verification (health checks, smoke tests)
-- Rollback plan
-
-## Checklist
-- [ ] Target environment confirmed
-- [ ] All tests passing
-- [ ] Secrets/env vars configured
-- [ ] Database migrations planned
-- [ ] Build artifacts ready
-- [ ] Rollback plan documented
-- [ ] Health checks defined
-- [ ] Post-deploy verification planned
-- [ ] Memory file updated
-
-## Rules
-- Prefer least-risk rollout patterns.
-- Never expose secrets.
-- Distinguish clearly between required and optional steps.
-- Avoid unrelated infra/app changes; if a deployment step requires broad refactors, ASK first.
-- Always read and update the memory file.
-
-## Related Skills
-- `/test` → read `.kiro/skills/test/SKILL.md` — Run tests before deployment
-- `/status` → read `.kiro/skills/status/SKILL.md` — Check project readiness
-- `/plan` → read `.kiro/skills/plan/SKILL.md` — Plan complex deployment sequences
+---
+name: deploy
+description: "Deployment steps, release preparation, environment setup, CI/CD guidance, and production rollout. Use when the user wants to deploy, release, or set up infrastructure. Triggers: deploy, release, CI/CD, docker, production, triển khai, phát hành, đưa lên production."
+agents: [devops-engineer, security-auditor]
+related-skills: [test, status, plan]
+---
+
+## Memory Protocol
+**START**: Read `.ai-memory.md` from project root. Check deployment history, target environments, known infrastructure, CI/CD setup, past deployment issues.
+**END**: Update `.ai-memory.md` using **Memory Compaction Rules** with: target, steps, env details, issues, rollback notes, and infra decisions.
+
+## Goal
+Prepare a safe, repeatable deployment or release plan.
+
+## Agent Routing
+- For infrastructure/CI/CD → read `.kiro/skills/agents/agents/devops-engineer.md` and apply its knowledge
+- For security review before deploy → read `.kiro/skills/agents/agents/security-auditor.md` and apply its knowledge
+- For database migrations → read `.kiro/skills/agents/agents/database-architect.md` and apply its knowledge
+- For performance validation → read `.kiro/skills/agents/agents/performance-optimizer.md` and apply its knowledge
+
+## Socratic Gate
+Before deploying, verify:
+1. What is the target environment? (staging, production, preview?)
+2. Are all tests passing?
+3. Are there database migrations or breaking changes?
+If any answer is unclear, ASK before proceeding.
+
+## Workflow
+1. **Read Memory** — Load `.ai-memory.md` for deployment history and environment details.
+2. Detect the app type, runtime, dependencies, and target environment.
+3. List prerequisites: secrets, env vars, build steps, infrastructure, database migrations, and health checks.
+4. Produce a deployment sequence from pre-checks to rollback.
+5. Call out risky steps explicitly.
+6. Include post-deploy verification and monitoring.
+7. **Quality Gate** — Read `.kiro/skills/_scripts/pre-deploy.md` for pre-deploy checklist, then `.kiro/skills/_scripts/checklist.md` for cross-cutting checks.
+8. **Update Memory** — Save deployment details and outcomes to `.ai-memory.md`.
+
+## Output format
+- Target environment
+- Preconditions
+- Deployment steps (numbered, with risk flags)
+- Verification (health checks, smoke tests)
+- Rollback plan
+
+## Checklist
+- [ ] Target environment confirmed
+- [ ] All tests passing
+- [ ] Secrets/env vars configured
+- [ ] Database migrations planned
+- [ ] Build artifacts ready
+- [ ] Rollback plan documented
+- [ ] Health checks defined
+- [ ] Post-deploy verification planned
+- [ ] Memory file updated
+
+## Rules
+- Prefer least-risk rollout patterns.
+- Never expose secrets.
+- Distinguish clearly between required and optional steps.
+- Avoid unrelated infra/app changes; if a deployment step requires broad refactors, ASK first.
+- Always read and update the memory file.
+
+## Related Skills
+- `/test` → read `.kiro/skills/test/SKILL.md` — Run tests before deployment
+- `/status` → read `.kiro/skills/status/SKILL.md` — Check project readiness
+- `/plan` → read `.kiro/skills/plan/SKILL.md` — Plan complex deployment sequences

package/.kiro/skills/enhance/SKILL.md

@@ -1,58 +1,58 @@
----
-name: enhance
-description: "Improve existing code — refactor, optimize performance, tighten security, or enhance UX. Use when the user wants to make code better without changing its purpose. Triggers: enhance, improve, refactor, optimize, review, cải thiện, tối ưu, nhanh hơn, code dài quá."
-agents: [performance-optimizer, security-auditor, frontend-specialist]
-related-skills: [debug, test, plan]
----
-
-## Memory Protocol
-**START**: Read `.ai-memory.md` from project root. Check past enhancements, known pain points, tech debt notes, performance baselines, and architecture decisions.
-**END**: Update `.ai-memory.md` using **Memory Compaction Rules** with: what changed, impact, tradeoffs, and remaining tech debt.
-
-## Goal
-Improve an existing implementation without breaking working behavior.
-
-## Agent Routing
-- If enhancing performance → read `.kiro/skills/agents/agents/performance-optimizer.md` and apply its knowledge
-- If tightening security → read `.kiro/skills/agents/agents/security-auditor.md` and apply its knowledge
-- If improving UI/UX → read `.kiro/skills/agents/agents/frontend-specialist.md` and apply its knowledge
-- If refactoring backend/API → read `.kiro/skills/agents/agents/backend-specialist.md` and apply its knowledge
-- If improving database queries → read `.kiro/skills/agents/agents/database-architect.md` and apply its knowledge
-
-## Socratic Gate
-Before enhancing, verify:
-1. What specific aspect needs improvement? (performance, security, UX, maintainability?)
-2. What is the current pain point or metric?
-3. Are there existing tests that must continue to pass?
-If any answer is unclear, ASK before proceeding.
-
-## Workflow
-1. **Read Memory** — Load `.ai-memory.md` for project context and past enhancement history.
-2. Understand the current state and pain points.
-3. Identify high-impact improvements in quality, maintainability, performance, reliability, or UX.
-4. Prioritize improvements by value versus effort.
-5. Implement or recommend the top changes.
-6. Explain tradeoffs and validation steps.
-7. **Quality Gate** — Read `.kiro/skills/_scripts/checklist.md` and verify enhancements don't break existing behavior.
-8. **Update Memory** — Save enhancement details and outcomes to `.ai-memory.md`.
-
-## Checklist
-- [ ] Current state documented
-- [ ] Pain points identified
-- [ ] Improvements prioritized by value/effort
-- [ ] Existing behavior preserved
-- [ ] Tradeoffs explained
-- [ ] Tests still passing
-- [ ] Memory file updated
-
-## 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.
-- Avoid changing unrelated files; if improvement requires broad refactor, ASK before doing it.
-- Always read and update the memory file.
-
-## Related Skills
-- `/debug` → read `.kiro/skills/debug/SKILL.md` — Fix issues found during enhancement
-- `/test` → read `.kiro/skills/test/SKILL.md` — Verify enhancements don't break things
-- `/plan` → read `.kiro/skills/plan/SKILL.md` — Plan large-scale refactoring
+---
+name: enhance
+description: "Improve existing code — refactor, optimize performance, tighten security, or enhance UX. Use when the user wants to make code better without changing its purpose. Triggers: enhance, improve, refactor, optimize, review, cải thiện, tối ưu, nhanh hơn, code dài quá."
+agents: [performance-optimizer, security-auditor, frontend-specialist]
+related-skills: [debug, test, plan]
+---
+
+## Memory Protocol
+**START**: Read `.ai-memory.md` from project root. Check past enhancements, known pain points, tech debt notes, performance baselines, and architecture decisions.
+**END**: Update `.ai-memory.md` using **Memory Compaction Rules** with: what changed, impact, tradeoffs, and remaining tech debt.
+
+## Goal
+Improve an existing implementation without breaking working behavior.
+
+## Agent Routing
+- If enhancing performance → read `.kiro/skills/agents/agents/performance-optimizer.md` and apply its knowledge
+- If tightening security → read `.kiro/skills/agents/agents/security-auditor.md` and apply its knowledge
+- If improving UI/UX → read `.kiro/skills/agents/agents/frontend-specialist.md` and apply its knowledge
+- If refactoring backend/API → read `.kiro/skills/agents/agents/backend-specialist.md` and apply its knowledge
+- If improving database queries → read `.kiro/skills/agents/agents/database-architect.md` and apply its knowledge
+
+## Socratic Gate
+Before enhancing, verify:
+1. What specific aspect needs improvement? (performance, security, UX, maintainability?)
+2. What is the current pain point or metric?
+3. Are there existing tests that must continue to pass?
+If any answer is unclear, ASK before proceeding.
+
+## Workflow
+1. **Read Memory** — Load `.ai-memory.md` for project context and past enhancement history.
+2. Understand the current state and pain points.
+3. Identify high-impact improvements in quality, maintainability, performance, reliability, or UX.
+4. Prioritize improvements by value versus effort.
+5. Implement or recommend the top changes.
+6. Explain tradeoffs and validation steps.
+7. **Quality Gate** — Read `.kiro/skills/_scripts/checklist.md` and verify enhancements don't break existing behavior.
+8. **Update Memory** — Save enhancement details and outcomes to `.ai-memory.md`.
+
+## Checklist
+- [ ] Current state documented
+- [ ] Pain points identified
+- [ ] Improvements prioritized by value/effort
+- [ ] Existing behavior preserved
+- [ ] Tradeoffs explained
+- [ ] Tests still passing
+- [ ] Memory file updated
+
+## 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.
+- Avoid changing unrelated files; if improvement requires broad refactor, ASK before doing it.
+- Always read and update the memory file.
+
+## Related Skills
+- `/debug` → read `.kiro/skills/debug/SKILL.md` — Fix issues found during enhancement
+- `/test` → read `.kiro/skills/test/SKILL.md` — Verify enhancements don't break things
+- `/plan` → read `.kiro/skills/plan/SKILL.md` — Plan large-scale refactoring