ai-developer-skill-os 3.1.0 → 3.1.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: qk-system-evolution
3
- version: 3.0.0
3
+ version: 3.1.2
4
4
  updated: 2026-07-02
5
5
  description: Safely upgrade dependencies, migrate frameworks, and manage rollbacks.
6
6
  category: operations
@@ -21,6 +21,7 @@ pipeline: [analyze, plan, implement, validate, complete]
21
21
  > **Goal:** Quản lý các thay đổi lớn cấp hệ thống (Major Updates) một cách an toàn, luôn có đường lui (Rollback) nếu xảy ra sự cố.
22
22
 
23
23
  ## 🔄 1. Chain of Thought (SOP)
24
+
24
25
  1. **Analyze (Impact Analysis):**
25
26
  - Read the Changelog or Migration Guide for the new version.
26
27
  - Identify Breaking Changes and Deprecated APIs.
@@ -36,11 +37,13 @@ pipeline: [analyze, plan, implement, validate, complete]
36
37
  - Run the build process to ensure the system compiles.
37
38
 
38
39
  ## 🛡️ 3. Constraints & Rules
40
+
39
41
  - **Safety First:** Never run `npm update` blindly across all packages. Update only what was requested.
40
42
  - **Lockfiles:** Do not delete `package-lock.json` or `yarn.lock` unless resolving extreme merge conflicts.
41
43
  - **Always Rollback:** If the system produces >50 compilation errors after an upgrade and you cannot fix them in 1 turn, immediately trigger the Rollback Plan.
42
44
 
43
45
  ## 🌳 3. Decision Tree
46
+
44
47
  ```text
45
48
  Are there Breaking Changes in the target version?
46
49
  ├── YES → Create a migration checklist based on the official docs. Update code systematically.
@@ -54,11 +57,14 @@ Did the Build fail after the update?
54
57
  ```
55
58
 
56
59
  ## 🤝 4. Handoff Pipeline
60
+
57
61
  1. `validate`: Run the full test suite and `npm run build` via `qk-validation-gate`.
58
62
  2. `complete`: Generate the Evolution report.
59
63
 
60
64
  ## 📝 5. Output Format
65
+
61
66
  Vui lòng trả kết quả bằng Tiếng Việt.
67
+
62
68
  - **Tóm tắt (Summary):** Đã nâng cấp package nào, từ vX lên vY.
63
69
  - **Chi tiết (Changes):** Số lượng file phải sửa do Breaking Changes.
64
70
  - **Kế hoạch lùi (Reasoning/Risks):** Ghi rõ lệnh Rollback để User copy-paste nếu cần.
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: qk-ui-audit
3
- version: 3.0.0
3
+ version: 3.1.2
4
4
  updated: 2026-07-02
5
5
  description: Audit UI for Consistency, Accessibility, Responsive, and Performance.
6
6
  category: validation
@@ -21,6 +21,7 @@ pipeline: [analyze, review, validate, complete]
21
21
  > **Goal:** Kiểm toán chất lượng Giao diện Người dùng (UI QA). Tìm ra các lỗi hiển thị, sự thiếu đồng nhất và vi phạm Accessibility (a11y).
22
22
 
23
23
  ## 🔄 1. Chain of Thought (SOP)
24
+
24
25
  1. **Analyze (Scan UI):**
25
26
  - Read the UI component's source code.
26
27
  - Look for inline styles (`style={{...}}`) and hardcoded magic numbers (e.g., `px`, `%` instead of standard tokens).
@@ -35,10 +36,12 @@ pipeline: [analyze, review, validate, complete]
35
36
  - Calculate a rough score (0-100) based on violations.
36
37
 
37
38
  ## 🛡️ 3. Constraints & Rules
39
+
38
40
  - **Audit Only:** Do not modify the code automatically unless the user explicitly requests you to apply the fixes.
39
41
  - **Evidence Based:** Point out the exact line number where the violation occurs.
40
42
 
41
43
  ## 🌳 3. Decision Tree
44
+
42
45
  ```text
43
46
  Does the component contain hardcoded `#hex` colors or `px` values?
44
47
  ├── YES → Deduct Consistency score. Recommend using Design Tokens.
@@ -50,10 +53,13 @@ Does the component have clickable `<div>` elements?
50
53
  ```
51
54
 
52
55
  ## 🤝 4. Handoff Pipeline
56
+
53
57
  1. `complete`: Generate the UI Audit Report.
54
58
 
55
59
  ## 📝 5. Output Format
60
+
56
61
  Vui lòng trả kết quả bằng Tiếng Việt.
62
+
57
63
  - **Tóm tắt (Summary):** Chấm điểm Giao diện (Score: X/100).
58
64
  - **Chi tiết (Changes):** Liệt kê các lỗi Consistency, A11y, Responsive (ghi rõ dòng).
59
65
  - **Nguyên nhân (Reasoning):** Tại sao lại đánh lỗi điểm đó.
@@ -1,9 +1,11 @@
1
1
  ---
2
2
  name: qk-ui-system-builder
3
- version: 3.0.0
3
+ version: 3.1.2
4
4
  updated: 2026-07-02
5
5
  description: Build and maintain Design Systems, Token extraction, and shared UI libraries.
6
6
  category: frontend
7
+ behavior: development
8
+ intent: implement-feature
7
9
  priority: medium
8
10
  tags: [design-system, tokens, shared-components, storybook]
9
11
  platforms: [claude-code, cursor, windsurf, gemini-cli]
@@ -19,6 +21,7 @@ pipeline: [analyze, implement, engineering-standard, validate, complete]
19
21
  > **Goal:** Đảm bảo tính Nhất quán Giao diện (Consistency). Quản lý Design Tokens và xây dựng thư viện Shared Components.
20
22
 
21
23
  ## 🔄 1. Chain of Thought (SOP)
24
+
22
25
  1. **Analyze (Token Extraction):**
23
26
  - Extract raw colors and typography into CSS Variables or Tailwind config.
24
27
  2. **Implement (Component Factory):**
@@ -27,14 +30,18 @@ pipeline: [analyze, implement, engineering-standard, validate, complete]
27
30
  - Ensure every variation (primary, secondary, disabled) is accounted for.
28
31
 
29
32
  ## 🛡️ 2. Constraints & Rules
33
+
30
34
  - **Stateless:** System UI components should NEVER have their own backend logic or hardcoded strings.
31
35
  - **Extendable:** Always allow users to pass `className` and `...props` to the base element.
32
36
 
33
37
  ## 🤝 3. Handoff Pipeline
38
+
34
39
  1. `engineering-standard`: Verify naming conventions.
35
40
  2. `complete`: Output the Design System Report.
36
41
 
37
42
  ## 📝 4. Output Format
43
+
38
44
  Vui lòng trả kết quả bằng Tiếng Việt.
45
+
39
46
  - **Tóm tắt (Summary):** Thư viện Component vừa cập nhật.
40
47
  - **Chi tiết (Changes):** Liệt kê các variant (màu sắc, kích cỡ).
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: qk-validation-gate
3
- version: 3.0.0
3
+ version: 3.1.2
4
4
  updated: 2026-07-02
5
5
  description: Mandatory Quality Gate (Test, Lint, Security).
6
6
  category: validation
@@ -21,6 +21,7 @@ pipeline: [analyze, validate, complete]
21
21
  > **Goal:** Hoạt động như một "Người Gác Cổng" (Gatekeeper). Đảm bảo không có lỗi cú pháp, vi phạm bảo mật, hoặc code rác nào lọt qua trước khi báo cáo hoàn thành.
22
22
 
23
23
  ## 🔄 1. Chain of Thought (SOP)
24
+
24
25
  1. **Analyze (Static Sweep):**
25
26
  - Use `grep_search` to scan modified files for garbage code: `console.log(`, `debugger;`, `// TODO`, `@ts-ignore`.
26
27
  - Scan for hardcoded secrets: `API_KEY=`, `Bearer ey...`.
@@ -33,11 +34,13 @@ pipeline: [analyze, validate, complete]
33
34
  - If tests fail, report the exact failure to the user. Do NOT pretend it passed.
34
35
 
35
36
  ## 🛡️ 3. Constraints & Rules
37
+
36
38
  - **Zero Tolerance:** A failed test or a TypeScript error means the Gate is FAILED. Do not ignore errors.
37
39
  - **No Force:** Never use `--force` or `--no-verify` flags.
38
40
  - **Real Execution:** You MUST run the actual CLI commands using `run_command` and wait for the output.
39
41
 
40
42
  ## 🌳 3. Decision Tree
43
+
41
44
  ```text
42
45
  Did `npm run lint` return errors?
43
46
  ├── YES → Are they auto-fixable?
@@ -51,10 +54,13 @@ Did `tsc --noEmit` return errors?
51
54
  ```
52
55
 
53
56
  ## 🤝 4. Handoff Pipeline
57
+
54
58
  1. `complete`: Once all checks pass, output the Validation Report.
55
59
 
56
60
  ## 📝 5. Output Format
61
+
57
62
  Vui lòng trả kết quả bằng Tiếng Việt.
63
+
58
64
  - **Tóm tắt (Summary):** 🛡️ Đã chạy các cổng kiểm định (Lint, Test, Type).
59
65
  - **Chi tiết (Changes):** Liệt kê các lệnh đã chạy và kết quả.
60
66
  - **Xác thực (Verification):** Ghi rõ PASS (Xanh) hoặc FAIL (Đỏ).