ai-developer-skill-os 7.5.1 → 8.1.5

package/skills/qk-project-memory/SKILL.md

@@ -1,219 +0,0 @@
----
-name: qk-project-memory
-category: core
-version: 7.5.1
-description: "Lưu trữ và truy xuất ngữ cảnh dự án dài hạn — chỉ lưu fact đã xác minh, không lưu giả thuyết."
-platforms: [antigravity, claude-code, cursor, windsurf, kilo-code]
-execution_mode: deterministic
-cost: low
-latency: fast
-risk: low
-side_effects: edit_files
-produces: [plan]
-consumes: [source-code, context-graph]
-token_budget:
-  max_files_read: 2
-  max_lines_per_read: 100
-  max_shell_commands: 0
-  stop_early: true
-exit_codes: [SUCCESS, BLOCKED, FAILED, PARTIAL]
-skill_version: 7.5.1
-runtime_version: 1
-schema_version: 2
----
-
-# qk-project-memory — Long-Term Context Store
-
-> **Language rule:** Code, identifiers, file names ? English. Explanations, summaries ? Vietnamese.
-
----
-
-## Preconditions
-- [ ] Project has a `.agents/memory/` directory OR user confirms creation
-
----
-
-## Scope
-- ✅ Store verified facts about project (architecture, decisions, patterns)
-- ✅ Retrieve facts for current session context
-- ✅ Invalidate stale entries when code changes
-
-## Non-Goals
-- ❌ Store assumptions or unverified hypotheses
-- ❌ Overwrite architectural rules without explicit user consent
-- ❌ Store sensitive data (env vars, secrets)
-
----
-
-## Memory Schema (Required Format)
-
-```json
-{
-  "id": "mem_[timestamp]",
-  "category": "architecture|pattern|decision|warning|preference",
-  "fact": "[Verified, specific statement]",
-  "evidence": "path/to/file.ts:LINE",
-  "confidence": "HIGH|MEDIUM",
-  "created_at": "ISO8601",
-  "expires_at": "ISO8601 OR null (permanent)",
-  "tags": ["auth", "database", "api"]
-}
-```
-
----
-
-## Storage Path
-```
-.agents/memory/
-├── architecture.json    # System architecture facts
-├── patterns.json        # Established code patterns
-├── decisions.json       # Technical decisions made
-└── warnings.json        # Known risks or debt items
-```
-
----
-
-## [MEMORIZE] Workflow
-1. Verify fact against actual codebase (grep_search or view_file)
-2. Confirm confidence is HIGH or MEDIUM
-3. Write to appropriate `.agents/memory/[category].json` file
-
-**Decision:** `IF confidence is LOW → do NOT store — collect more evidence`
-
-## [RECALL] Workflow
-1. Read relevant memory file
-2. Check `expires_at` — skip stale entries
-3. Return matching facts with their evidence references
-
----
-
-## Exit Codes
-| Code | Meaning | When |
-|------|---------|------|
-| SUCCESS | Fact stored/retrieved with verified evidence | HIGH/MEDIUM confidence |
-| PARTIAL | Fact stored but evidence is indirect (MEDIUM confidence) | Indirect source |
-| BLOCKED | Cannot verify fact against codebase | No evidence available |
-| FAILED | Memory file corrupted or schema mismatch | Structural error |
-
----
-
-## Confidence Model
-| Level | Condition | Action |
-|-------|-----------|--------|
-| HIGH | Fact directly read from code (grep_search returned file:line) | Store immediately |
-| MEDIUM | Fact inferred from patterns (not direct file reference) | Store with note: "inferred" |
-| LOW | Assumption without code evidence | Do NOT store — collect more evidence first |
-
----
-
-## Severity
-| Level | Definition | Example |
-|-------|-----------|----------|
-| CRITICAL | Storing incorrect architectural fact misleads all future work | Wrong auth pattern stored |
-| HIGH | Storing stale fact that conflicts with current code | Outdated API path remembered |
-| MEDIUM | Missing important fact causing repeated re-discovery | Auth pattern unknown |
-| LOW | Memory file not organized by category | All facts in one file |
-
----
-
-## Evidence Format
-```
-[CONFIDENCE] path/to/file.ts:LINE
-Fact:       [what was stored]
-Category:   [architecture|pattern|decision|warning|preference]
-Expires:    [ISO8601 date | null]
-```
-
----
-
-## Retry Policy
-```
-Fact unverifiable
-  └─ Read 1 more file for evidence
-       ├─ Evidence found → upgrade to MEDIUM/HIGH → store
-       └─ Still unverifiable → do NOT store
-            └─ Do NOT retry more than 1 additional evidence read
-```
-
----
-
-## Escalation Rules
-```
-BLOCKED: Cannot verify fact against codebase
-Missing:
-  - Access to relevant source file
-  - Or explicit user confirmation
-Questions:
-  1. Bạn có thể xác nhận: [fact statement] là đúng không?
-Recommended Assumptions:
-  - Do NOT store until confirmed
-```
-
----
-
-## Handoff Contract
-### Consumes
-```json
-{
-  "from": "user or any skill",
-  "required_fields": ["fact_statement"],
-  "optional_fields": ["evidence_location", "expiry_date", "category"]
-}
-```
-### Produces
-```json
-{
-  "to": "any downstream skill",
-  "output_fields": ["recalled_facts", "confidence_levels", "evidence_refs", "exit_code"]
-}
-```
-
----
-
-## UI Diversification Memory
-
-### Purpose
-Prevent UI template repetition across project builds. Inspired by Hallmark's `.hallmark/log.json`.
-
-### Storage Path
-```
-.agents/memory/
-├── architecture.json
-├── patterns.json
-├── decisions.json
-├── warnings.json
-└── ui-diversification.json    # NEW: UI build history
-```
-
-### Schema
-```json
-{
-  "id": "ui_[timestamp]",
-  "category": "ui-diversification",
-  "fact": "Built [component] with [theme] theme and [macrostructure] macrostructure",
-  "evidence": "path/to/component.tsx",
-  "confidence": "HIGH",
-  "created_at": "ISO8601",
-  "expires_at": null,
-  "tags": ["theme", "macrostructure", "component"]
-}
-```
-
-### Rule
-**No two consecutive UI builds in the same project may share the same theme + macrostructure combination.**
-
-When `qk-ui-builder` runs:
-1. Read `.agents/memory/ui-diversification.json` (if exists)
-2. Get last entry's theme + macrostructure
-3. Pick different combination for current build
-4. After build, append new entry to `ui-diversification.json`
-
-### Enforcement
-If user requests same theme/macrostructure as last build:
-- Note the conflict in output
-- Recommend alternative
-- Proceed only if user explicitly overrides
-
----
-
-

package/skills/qk-system-evolution/SKILL.md

@@ -1,282 +0,0 @@
----
-name: qk-system-evolution
-category: maintenance
-version: 7.5.1
-description: "Nâng cấp thư viện/framework an toàn với rollback plan bắt buộc — incremental, không big-bang."
-platforms: [antigravity, claude-code, cursor, windsurf, kilo-code]
-execution_mode: deterministic
-
-cost: high
-latency: slow
-risk: high
-side_effects: edit_files
-produces: [code, report, plan]
-consumes: [context-graph, source-code]
-
-token_budget:
-  max_files_read: 4
-  max_lines_per_read: 100
-  max_shell_commands: 2
-  stop_early: false
-
-exit_codes: [SUCCESS, BLOCKED, FAILED, PARTIAL]
-skill_version: 7.5.1
-runtime_version: 1
-schema_version: 2
----
-
-# qk-system-evolution — Safe Upgrade Manager
-
-> **Language rule:** Code, identifiers, file names ? English. Explanations, summaries ? Vietnamese.
-
-skill_version: 7.5.1
-runtime_version: 1
-schema_version: 2
----
-
-## Preconditions
-- [ ] Current version and target version are specified
-- [ ] Rollback strategy is defined (git tag OR package-lock.json snapshot)
-- [ ] Existing test suite is available to verify after upgrade
-
-```
-On missing precondition:
-  EXIT: BLOCKED
-  Message: "Rollback plan required before any major upgrade. Specify: target version + rollback method."
-```
-
-skill_version: 7.5.1
-runtime_version: 1
-schema_version: 2
----
-
-## Scope
-- ✅ Read official Changelog/Migration Guide for breaking changes
-- ✅ Apply incremental upgrades (not big-bang)
-- ✅ Verify each step with existing tests
-- ✅ Document rollback procedure
-
-## Non-Goals
-- ❌ Blindly run `npm update` — only targeted upgrades
-- ❌ Skip reading Changelog for major version bumps
-- ❌ Upgrade multiple major versions at once (one at a time)
-
-skill_version: 7.5.1
-runtime_version: 1
-schema_version: 2
----
-
-## Priority Order
-
-| Priority | Check | Skip Threshold |
-|----------|-------|----------------|
-| P1 | Read Changelog for breaking changes | Never |
-| P2 | Snapshot rollback point (git tag) | Never |
-| P3 | Apply upgrade to package.json only | Never |
-| P4 | Run tests to detect breakage | Never |
-| P5 | Fix breaking changes if minor (< 3 files affected) | Budget < 40% |
-| P6 | Update documentation/README | Budget < 70% |
-
-skill_version: 7.5.1
-runtime_version: 1
-schema_version: 2
----
-
-## Workflow
-
-### Phase 1 — Breaking Change Analysis
-
-**Steps:**
-1. `view_file` or `read_url` — read official Changelog for target version
-2. List all `BREAKING CHANGE` entries
-3. Map each breaking change to affected files in current codebase (`grep_search`)
-
-**Decision:**
-```
-IF 0 breaking changes
-  → Confidence: HIGH → go to Phase 2 (minor/patch upgrade)
-
-IF 1–3 breaking changes, all in < 5 files
-  → Confidence: MEDIUM → go to Phase 2
-
-IF > 3 breaking changes OR affects core files
-  → EXIT: BLOCKED — this is architectural migration, not an upgrade
-  → Recommend: plan as a dedicated migration project
-```
-
-skill_version: 7.5.1
-runtime_version: 1
-schema_version: 2
----
-
-### Phase 2 — Rollback Snapshot
-
-**Steps:**
-1. Verify `git tag` or instruct user to create one: `git tag pre-upgrade-[package]-[version]`
-2. Copy `package-lock.json` snapshot reference
-3. Document exact rollback command:
-   ```
-   Rollback: git checkout pre-upgrade-[package]-[version]
-   OR: npm install [package]@[previous-version]
-   ```
-
-**Exit When:** Rollback procedure documented → go to Phase 3
-
-skill_version: 7.5.1
-runtime_version: 1
-schema_version: 2
----
-
-### Phase 3 — Incremental Upgrade
-
-**Steps:**
-1. Edit `package.json` — change version (one package at a time)
-2. Apply code changes for breaking changes (using `replace_file_content`)
-3. Run: `npm install` (1 command)
-
-**Decision:**
-```
-IF install succeeds
-  → go to Phase 4
-
-IF install fails (peer dep conflict)
-  → EXIT: PARTIAL — report conflict, suggest resolution
-```
-
-skill_version: 7.5.1
-runtime_version: 1
-schema_version: 2
----
-
-### Phase 4 — Verification
-
-**Steps:**
-1. Run tests: `npm test` (2nd command)
-2. Parse test results for failures
-
-**Decision:**
-```
-IF all tests pass
-  → EXIT: SUCCESS
-
-IF 1–3 tests fail (related to upgrade)
-  → Fix if minor (< 10 lines change per fix)
-  → EXIT: PARTIAL
-
-IF > 3 tests fail OR core tests fail
-  → EXIT: FAILED — rollback recommended
-  → Provide exact rollback command
-```
-
-skill_version: 7.5.1
-runtime_version: 1
-schema_version: 2
----
-
-## Confidence Model
-
-| Level | Condition | Action |
-|-------|-----------|--------|
-| HIGH | Changelog read, breaking changes mapped, tests pass | Proceed |
-| MEDIUM | Changelog read, some uncertainties remain | Proceed with caution, note risks |
-| LOW | Cannot access Changelog or no tests available | EXIT: BLOCKED |
-
-skill_version: 7.5.1
-runtime_version: 1
-schema_version: 2
----
-
-## Severity
-
-| Level | Definition |
-|-------|-----------|
-| CRITICAL | Core authentication/security package upgrade |
-| HIGH | ORM, framework, or router upgrade |
-| MEDIUM | Utility library, build tool upgrade |
-| LOW | Dev dependency, formatter upgrade |
-
-skill_version: 7.5.1
-runtime_version: 1
-schema_version: 2
----
-
-## Evidence Format
-
-```
-[SEVERITY] package: [name] v[old] → v[new]
-Breaking changes: [list from Changelog]
-Affected files:   [N files — list]
-Confidence:       [HIGH|MEDIUM|LOW]
-Rollback:         git checkout [tag] OR npm install [name]@[old-version]
-```
-
-skill_version: 7.5.1
-runtime_version: 1
-schema_version: 2
----
-
-## Rollback Procedure (Required Output)
-
-Every upgrade must document:
-```
-🔄 Rollback Procedure
-─────────────────────────────────────────────────
-Method 1 (Git):  git checkout [tag-name]
-Method 2 (npm):  npm install [package]@[previous-version]
-Snapshot tag:    [pre-upgrade-[package]-[date]]
-```
-
-skill_version: 7.5.1
-runtime_version: 1
-schema_version: 2
----
-
-## Handoff Contract
-
-### Consumes
-```json
-{
-  "from": "user",
-  "required_fields": ["package_name", "target_version", "rollback_method"],
-  "optional_fields": ["changelog_url", "affected_scope"]
-}
-```
-
-### Produces
-```json
-{
-  "to": "qk-validation-gate",
-  "output_fields": ["upgraded_packages", "breaking_changes_fixed", "rollback_procedure", "exit_code"]
-}
-```
-
-skill_version: 7.5.1
-runtime_version: 1
-schema_version: 2
----
-
-
----
-
-## Escalation Rules
-
-
----
-
-## Retry Policy
-
-
----
-## Exit Codes
-
-| Code | Meaning | When |
-|------|---------|------|
-| SUCCESS | Upgrade complete, all tests pass | Clean upgrade |
-| PARTIAL | Upgrade done, some tests fail or peer conflict | Needs follow-up |
-| BLOCKED | No rollback plan or too many breaking changes | Plan migration instead |
-| FAILED | Tests fail after upgrade, rollback recommended | Provide rollback command |
-
----
-
-
-