@votruongdanh/ai-agent-skills 3.2.1 → 3.3.1

package/.kiro/skills/_scripts/.ai-memory-template.md

@@ -1,55 +1,55 @@
-# Project Memory
-
-> This file is automatically maintained by AI Agent Skills.
-> It persists project understanding across conversations.
-> **Do NOT delete this file** — it helps AI give better, context-aware responses.
-
-## Codex Memory Structure (when available)
-- If the workspace has `memories/`, use it alongside this file.
-- `memories/` = persistent user-level notes.
-- `memories/session/` = temporary notes for current conversation.
-- `memories/repo/` = repository-scoped technical facts and conventions.
-- Keep `.ai-memory.md` as the cross-IDE source of truth; mirror only high-signal repo facts into `memories/repo/`.
-
-## Memory Compaction Rules (IMPORTANT)
-- **Write style**: concise bullets, no paragraphs. Prefer numbers, filenames, and nouns over prose.
-- **No duplication**: if a new note repeats an existing one, update the existing bullet instead of appending.
-- **Deduping rule (anti-duplicate)**:
-  - Before writing, **scan the target section** for a similar bullet.
-  - Consider bullets “similar” if they match after: lowercasing + trimming + collapsing whitespace + removing trailing punctuation.
-  - If similar: **merge into 1 bullet** (keep the most specific wording, add missing file paths/IDs).
-  - Never keep 2 bullets that describe the same decision/issue/work item.
-- **Hard limits**:
-  - Tech Stack: max 6 bullets
-  - Architecture: max 8 bullets
-  - Conventions: max 8 bullets
-  - Decisions: keep last 12 items
-  - Known Issues: keep last 20 items (closed issues can be removed once stable)
-  - Recent Work: keep last 15 items
-- **Per bullet**: aim ≤ 140 characters. If longer, split into 2 bullets.
-- **Always include**: files touched (paths), and why (1 short phrase).
-
-## Tech Stack
-- Language: (auto-detected on first use)
-- Framework: (auto-detected on first use)
-- Database: (if any)
-- Package manager: (auto-detected)
-
-## Architecture
-- Pattern: (discovered)
-- Key directories: (discovered)
-- Entry points: (discovered)
-
-## Conventions
-- Naming: (observed from codebase)
-- File structure: (observed)
-- Testing: (framework + patterns observed)
-
-## Decisions
-<!-- Format: - [YYYY-MM-DD] Decision description and rationale -->
-
-## Known Issues
-<!-- Format: - [status] Issue description -->
-
-## Recent Work
-<!-- Format: - [YYYY-MM-DD] What was done, files changed, outcome -->
+# Project Memory
+
+> This file is automatically maintained by AI Agent Skills.
+> It persists project understanding across conversations.
+> **Do NOT delete this file** — it helps AI give better, context-aware responses.
+
+## Codex Memory Structure (when available)
+- If the workspace has `memories/`, use it alongside this file.
+- `memories/` = persistent user-level notes.
+- `memories/session/` = temporary notes for current conversation.
+- `memories/repo/` = repository-scoped technical facts and conventions.
+- Keep `.ai-memory.md` as the cross-IDE source of truth; mirror only high-signal repo facts into `memories/repo/`.
+
+## Memory Compaction Rules (IMPORTANT)
+- **Write style**: concise bullets, no paragraphs. Prefer numbers, filenames, and nouns over prose.
+- **No duplication**: if a new note repeats an existing one, update the existing bullet instead of appending.
+- **Deduping rule (anti-duplicate)**:
+  - Before writing, **scan the target section** for a similar bullet.
+  - Consider bullets “similar” if they match after: lowercasing + trimming + collapsing whitespace + removing trailing punctuation.
+  - If similar: **merge into 1 bullet** (keep the most specific wording, add missing file paths/IDs).
+  - Never keep 2 bullets that describe the same decision/issue/work item.
+- **Hard limits**:
+  - Tech Stack: max 6 bullets
+  - Architecture: max 8 bullets
+  - Conventions: max 8 bullets
+  - Decisions: keep last 12 items
+  - Known Issues: keep last 20 items (closed issues can be removed once stable)
+  - Recent Work: keep last 15 items
+- **Per bullet**: aim ≤ 140 characters. If longer, split into 2 bullets.
+- **Always include**: files touched (paths), and why (1 short phrase).
+
+## Tech Stack
+- Language: (auto-detected on first use)
+- Framework: (auto-detected on first use)
+- Database: (if any)
+- Package manager: (auto-detected)
+
+## Architecture
+- Pattern: (discovered)
+- Key directories: (discovered)
+- Entry points: (discovered)
+
+## Conventions
+- Naming: (observed from codebase)
+- File structure: (observed)
+- Testing: (framework + patterns observed)
+
+## Decisions
+<!-- Format: - [YYYY-MM-DD] Decision description and rationale -->
+
+## Known Issues
+<!-- Format: - [status] Issue description -->
+
+## Recent Work
+<!-- Format: - [YYYY-MM-DD] What was done, files changed, outcome -->

package/.kiro/skills/_scripts/checklist.md

@@ -1,34 +1,35 @@
----
-name: checklist
-description: Reusable pre/post checklists for any skill execution
----
-
-## Pre-Execution Checklist (Run before ANY skill)
-- [ ] Read `.ai-memory.md` from project root
-- [ ] Understand user intent (ask if unclear)
-- [ ] Check if similar work was done before (from memory)
-- [ ] Identify the correct agent for the domain
-- [ ] Minimize blast radius: identify the smallest set of files that must change
-- [ ] If any step is uncertain or could cause broad changes, ask before editing
-
-## Post-Execution Checklist (Run after ANY skill)
-- [ ] All checklist items from the skill are satisfied
-- [ ] No regressions introduced
-- [ ] Code follows existing project conventions
-- [ ] Update `.ai-memory.md` with findings (follow “Memory Compaction Rules”)
-- [ ] Dedupe `.ai-memory.md` updates: merge similar bullets instead of appending duplicates
-- [ ] Suggest related next steps
-
-## Code Quality Checklist
-- [ ] No hardcoded secrets or credentials
-- [ ] Error handling at system boundaries
-- [ ] Input validation for user-facing code
-- [ ] Existing tests still pass
-- [ ] New code is covered by tests (if test framework exists)
-
-## Security Checklist
-- [ ] No SQL injection vectors
-- [ ] No XSS vulnerabilities
-- [ ] No exposed secrets in code or logs
-- [ ] Dependencies are up to date
-- [ ] Access controls are appropriate
+---
+name: checklist
+description: Reusable pre/post checklists for any skill execution
+---
+
+## Pre-Execution Checklist (Run before ANY skill)
+- [ ] Read `.ai-memory.md` from project root
+- [ ] Understand user intent (ask if unclear)
+- [ ] Check if similar work was done before (from memory)
+- [ ] Identify the correct agent for the domain
+- [ ] Minimize blast radius: identify the smallest set of files that must change
+- [ ] If any step is uncertain or could cause broad changes, ask before editing
+
+## Post-Execution Checklist (Run after ANY skill)
+- [ ] All checklist items from the skill are satisfied
+- [ ] No regressions introduced
+- [ ] Code follows existing project conventions
+- [ ] Update `.ai-memory.md` with findings (follow "Memory Compaction Rules")
+- [ ] Dedupe `.ai-memory.md` updates: merge similar bullets instead of appending duplicates
+- [ ] If `.ai-memory.md` exceeds 500 lines or sections exceed limits, compact it (see `.kiro/skills/_scripts/memory-compact.md`)
+- [ ] Suggest related next steps
+
+## Code Quality Checklist
+- [ ] No hardcoded secrets or credentials
+- [ ] Error handling at system boundaries
+- [ ] Input validation for user-facing code
+- [ ] Existing tests still pass
+- [ ] New code is covered by tests (if test framework exists)
+
+## Security Checklist
+- [ ] No SQL injection vectors
+- [ ] No XSS vulnerabilities
+- [ ] No exposed secrets in code or logs
+- [ ] Dependencies are up to date
+- [ ] Access controls are appropriate

package/.kiro/skills/_scripts/memory-compact.md

@@ -0,0 +1,142 @@
+---
+name: memory-compact
+description: Procedure to compact `.ai-memory.md` when it grows too long
+---
+
+## When to compact
+Run this procedure when `.ai-memory.md` exceeds **500 lines** or when you notice:
+- Duplicate or near-duplicate bullets
+- Outdated information (old decisions, resolved issues, ancient work items)
+- Verbose bullets that could be shortened
+- Sections exceeding their hard limits (see Memory Compaction Rules)
+
+## Compaction procedure
+
+### 1. Check section limits (from `.ai-memory-template.md`)
+- **Tech Stack**: max 6 bullets
+- **Architecture**: max 8 bullets
+- **Conventions**: max 8 bullets
+- **Decisions**: keep last 12 items
+- **Known Issues**: keep last 20 items (remove resolved/closed)
+- **Recent Work**: keep last 15 items
+
+### 2. Dedupe within each section
+For each section:
+1. Read all bullets
+2. Group similar bullets (same topic, same file, same decision)
+3. Merge groups into single bullets:
+   - Keep most specific wording
+   - Preserve all file paths, dates, IDs
+   - Remove redundant phrases
+
+**Example:**
+```markdown
+Before:
+- [2024-01-15] Added auth middleware to protect routes
+- [2024-01-16] Implemented authentication middleware in src/middleware/auth.js
+- Auth middleware added for route protection
+
+After:
+- [2024-01-15] Added auth middleware (src/middleware/auth.js) to protect routes
+```
+
+### 3. Remove outdated items
+- **Decisions**: Keep only decisions still relevant to current architecture
+- **Known Issues**: Remove resolved/closed issues older than 30 days
+- **Recent Work**: Keep only last 15 items (remove older)
+
+### 4. Shorten verbose bullets
+Target: ≤ 140 characters per bullet
+
+**Techniques:**
+- Remove filler words: "basically", "essentially", "in order to"
+- Use abbreviations: "impl" for "implemented", "cfg" for "config"
+- Use file paths instead of descriptions: `src/auth.js` not "the authentication file"
+- Use symbols: `+` for "added", `~` for "updated", `-` for "removed"
+
+**Example:**
+```markdown
+Before:
+- [2024-01-15] We implemented a new authentication system that uses JWT tokens for user sessions in the backend API
+
+After:
+- [2024-01-15] + JWT auth system (src/api/auth.js) for user sessions
+```
+
+### 5. Enforce hard limits
+If a section still exceeds limits after deduping and shortening:
+- **Decisions**: Keep last 12, archive older ones in a comment
+- **Known Issues**: Keep last 20, remove oldest resolved
+- **Recent Work**: Keep last 15, remove oldest
+
+**Archive pattern:**
+```markdown
+## Decisions
+- [2024-03-01] Current decision 1
+- [2024-02-28] Current decision 2
+...
+
+<!-- Archived decisions (for reference):
+- [2024-01-15] Old decision that's no longer relevant
+-->
+```
+
+### 6. Verify compaction
+After compacting:
+- [ ] No section exceeds hard limits
+- [ ] No duplicate bullets
+- [ ] All bullets ≤ 140 characters (or split into 2)
+- [ ] File paths preserved
+- [ ] Dates preserved
+- [ ] Recent/important info retained
+
+## Quick compaction (when in a hurry)
+If you need to compact quickly:
+1. **Recent Work**: Keep last 15, delete rest
+2. **Known Issues**: Remove all resolved/closed, keep last 20
+3. **Decisions**: Keep last 12
+4. Run dedupe on remaining bullets (merge similar ones)
+
+## Automation tip
+When updating memory, always:
+1. Check if section is at limit BEFORE adding
+2. If at limit, remove oldest item OR merge with existing
+3. Never append if it creates a duplicate
+
+## Example: Full compaction
+
+**Before (verbose, duplicates, over limits):**
+```markdown
+## Recent Work
+- [2024-01-10] Added login page
+- [2024-01-11] Created login component
+- [2024-01-12] Implemented login functionality
+- [2024-01-13] Fixed login bug
+- [2024-01-14] Updated login styles
+- [2024-01-15] Added logout button
+- [2024-01-16] Implemented logout functionality
+- [2024-01-17] Fixed logout bug
+- [2024-01-18] Added user profile page
+- [2024-01-19] Created user profile component
+- [2024-01-20] Implemented profile edit
+- [2024-01-21] Fixed profile bug
+- [2024-01-22] Added settings page
+- [2024-01-23] Created settings component
+- [2024-01-24] Implemented settings save
+- [2024-01-25] Fixed settings bug
+- [2024-01-26] Added dashboard
+- [2024-01-27] Created dashboard component
+```
+
+**After (compact, deduped, within limits):**
+```markdown
+## Recent Work
+- [2024-01-27] + Dashboard (src/pages/Dashboard.jsx)
+- [2024-01-26] + Settings page (src/pages/Settings.jsx) with save functionality
+- [2024-01-22] + User profile page (src/pages/Profile.jsx) with edit feature
+- [2024-01-15] + Login/logout (src/pages/Login.jsx, src/components/LogoutBtn.jsx)
+```
+
+## Related
+- Read `.kiro/skills/_scripts/.ai-memory-template.md` for Memory Compaction Rules
+- Read `.kiro/skills/_scripts/memory-dedupe.md` for dedupe procedure

package/.kiro/skills/_scripts/memory-dedupe.md

@@ -1,26 +1,26 @@
----
-name: memory-dedupe
-description: Lightweight dedupe procedure for `.ai-memory.md` updates
----
-
-## When to use
-Run mentally for every memory update, especially when adding items to **Decisions**, **Known Issues**, or **Recent Work**.
-
-## Dedupe procedure (fast)
-1. Pick the **target section** (Decisions / Known Issues / Recent Work / etc.).
-2. Before adding a new bullet, scan existing bullets for a near-match.
-3. Normalize both bullets and compare:
-   - lowercase
-   - trim
-   - collapse whitespace
-   - remove trailing punctuation (`.`, `;`, `,`)
-4. If it’s the same idea:
-   - **merge** into the existing bullet
-   - keep the most concrete version (file paths, error codes, IDs, dates)
-   - remove the redundant one
-5. Only append a new bullet if it’s clearly a new fact/event/decision.
-
-## Examples
-- Two bullets both say “Added auth middleware” → keep one, add the specific files touched.
-- “Fix login bug” and “Fixed login issue” → merge into one with the root cause or PR/files.
-
+---
+name: memory-dedupe
+description: Lightweight dedupe procedure for `.ai-memory.md` updates
+---
+
+## When to use
+Run mentally for every memory update, especially when adding items to **Decisions**, **Known Issues**, or **Recent Work**.
+
+## Dedupe procedure (fast)
+1. Pick the **target section** (Decisions / Known Issues / Recent Work / etc.).
+2. Before adding a new bullet, scan existing bullets for a near-match.
+3. Normalize both bullets and compare:
+   - lowercase
+   - trim
+   - collapse whitespace
+   - remove trailing punctuation (`.`, `;`, `,`)
+4. If it’s the same idea:
+   - **merge** into the existing bullet
+   - keep the most concrete version (file paths, error codes, IDs, dates)
+   - remove the redundant one
+5. Only append a new bullet if it’s clearly a new fact/event/decision.
+
+## Examples
+- Two bullets both say “Added auth middleware” → keep one, add the specific files touched.
+- “Fix login bug” and “Fixed login issue” → merge into one with the root cause or PR/files.
+

package/.kiro/skills/_scripts/pre-deploy.md

@@ -1,42 +1,42 @@
----
-name: pre-deploy
-description: Pre-deployment verification checklist
----
-
-## Pre-Deploy Checklist
-
-### Code Readiness
-- [ ] All tests pass
-- [ ] No lint errors
-- [ ] Build succeeds
-- [ ] No TODO/FIXME in critical paths
-- [ ] Version number updated (package.json, CHANGELOG)
-
-### Security
-- [ ] No secrets in source code
-- [ ] Environment variables documented
-- [ ] Dependencies audited (`npm audit`)
-- [ ] No known critical vulnerabilities
-
-### Configuration
-- [ ] Environment config is correct for target
-- [ ] Database migrations are ready (if applicable)
-- [ ] API keys and secrets are in environment, not code
-- [ ] Feature flags set appropriately
-
-### Documentation
-- [ ] CHANGELOG updated
-- [ ] README reflects current state
-- [ ] API docs updated (if applicable)
-- [ ] Deployment instructions are current
-
-### Rollback Plan
-- [ ] Previous version tagged
-- [ ] Rollback procedure documented
-- [ ] Database rollback scripts ready (if applicable)
-- [ ] Monitoring alerts configured
-
-## After Deploy
-- [ ] Smoke tests pass
-- [ ] Monitoring shows healthy metrics
-- [ ] Update `.ai-memory.md` with deploy details
+---
+name: pre-deploy
+description: Pre-deployment verification checklist
+---
+
+## Pre-Deploy Checklist
+
+### Code Readiness
+- [ ] All tests pass
+- [ ] No lint errors
+- [ ] Build succeeds
+- [ ] No TODO/FIXME in critical paths
+- [ ] Version number updated (package.json, CHANGELOG)
+
+### Security
+- [ ] No secrets in source code
+- [ ] Environment variables documented
+- [ ] Dependencies audited (`npm audit`)
+- [ ] No known critical vulnerabilities
+
+### Configuration
+- [ ] Environment config is correct for target
+- [ ] Database migrations are ready (if applicable)
+- [ ] API keys and secrets are in environment, not code
+- [ ] Feature flags set appropriately
+
+### Documentation
+- [ ] CHANGELOG updated
+- [ ] README reflects current state
+- [ ] API docs updated (if applicable)
+- [ ] Deployment instructions are current
+
+### Rollback Plan
+- [ ] Previous version tagged
+- [ ] Rollback procedure documented
+- [ ] Database rollback scripts ready (if applicable)
+- [ ] Monitoring alerts configured
+
+## After Deploy
+- [ ] Smoke tests pass
+- [ ] Monitoring shows healthy metrics
+- [ ] Update `.ai-memory.md` with deploy details

package/.kiro/skills/_scripts/verify-all.md

@@ -1,28 +1,28 @@
----
-name: verify-all
-description: Full verification pass — run all checks across the project
----
-
-## Steps
-1. **Read Memory** — Load `.ai-memory.md` for known issues
-2. **Structure Check** — Verify project structure matches expectations
-3. **Dependency Check** — Are all dependencies installed and up to date?
-4. **Lint/Format Check** — Does code pass linting and formatting rules?
-5. **Test Check** — Do all existing tests pass?
-6. **Build Check** — Does the project build successfully?
-7. **Security Check** — Run security audit (npm audit, etc.)
-8. **Documentation Check** — Are README and docs up to date?
-9. **Git Check** — Any uncommitted changes? Branch is clean?
-10. **Report** — Summarize findings with pass/fail for each check
-
-## Output Format
-```
-✅ Structure    — OK
-✅ Dependencies — OK  
-⚠️  Lint        — 3 warnings
-❌ Tests       — 1 failure in test/auth.test.js
-✅ Build       — OK
-⚠️  Security   — 2 moderate vulnerabilities
-✅ Docs        — OK
-✅ Git         — Clean
-```
+---
+name: verify-all
+description: Full verification pass — run all checks across the project
+---
+
+## Steps
+1. **Read Memory** — Load `.ai-memory.md` for known issues
+2. **Structure Check** — Verify project structure matches expectations
+3. **Dependency Check** — Are all dependencies installed and up to date?
+4. **Lint/Format Check** — Does code pass linting and formatting rules?
+5. **Test Check** — Do all existing tests pass?
+6. **Build Check** — Does the project build successfully?
+7. **Security Check** — Run security audit (npm audit, etc.)
+8. **Documentation Check** — Are README and docs up to date?
+9. **Git Check** — Any uncommitted changes? Branch is clean?
+10. **Report** — Summarize findings with pass/fail for each check
+
+## Output Format
+```
+✅ Structure    — OK
+✅ Dependencies — OK  
+⚠️  Lint        — 3 warnings
+❌ Tests       — 1 failure in test/auth.test.js
+✅ Build       — OK
+⚠️  Security   — 2 moderate vulnerabilities
+✅ Docs        — OK
+✅ Git         — Clean
+```