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-bug-resolution
3
- version: 3.0.0
3
+ version: 3.1.2
4
4
  updated: 2026-07-02
5
5
  description: Fix bugs and prevent regressions.
6
6
  category: engineering
@@ -21,6 +21,7 @@ pipeline: [analyze, implement, engineering-standard, validate, complete]
21
21
  > **Goal:** Định vị nguyên nhân, sửa lỗi triệt để, và đảm bảo lỗi không bị lặp lại (Regression Prevention).
22
22
 
23
23
  ## 🔄 1. Chain of Thought (SOP)
24
+
24
25
  1. **Analyze (Root Cause Analysis):**
25
26
  - Read the provided error log or bug description.
26
27
  - Trace the error to the exact file and line of code.
@@ -36,11 +37,13 @@ pipeline: [analyze, implement, engineering-standard, validate, complete]
36
37
  - Ensure backward compatibility.
37
38
 
38
39
  ## 🛡️ 3. Constraints & Rules
40
+
39
41
  - **No Guesses:** Do not assume the shape of an API response. Print it or read the type definitions first.
40
42
  - **Minimal Fix:** Always prefer a 1-line fix over a 100-line refactor, unless the architecture is fundamentally broken.
41
43
  - **Clean Up:** Remove any `console.log()` or debugger statements introduced during the debugging process.
42
44
 
43
45
  ## 🌳 3. Decision Tree
46
+
44
47
  ```text
45
48
  Is there a Stack Trace?
46
49
  ├── YES → Use grep_search to find the exact file and line number.
@@ -52,13 +55,17 @@ Is the bug related to State/Re-rendering?
52
55
  ```
53
56
 
54
57
  ## 🤝 4. Handoff Pipeline
58
+
55
59
  After implementing the fix, map to the pipeline:
60
+
56
61
  1. `engineering-standard`: Ensure the fix follows naming and architecture rules.
57
62
  2. `validate`: Run linters and tests (via `qk-validation-gate` equivalent).
58
63
  3. `complete`: Output the final report.
59
64
 
60
65
  ## 📝 5. Output Format
66
+
61
67
  Vui lòng sử dụng template `templates/bug-report.md` (Báo Cáo Xử Lý Lỗi) để phản hồi lại cho người dùng bằng Tiếng Việt. Nội dung bao gồm:
68
+
62
69
  - Summary
63
70
  - Changes
64
71
  - Root Cause
@@ -1,9 +1,11 @@
1
1
  ---
2
2
  name: qk-context-loader
3
- version: 3.0.0
3
+ version: 3.1.2
4
4
  updated: 2026-07-02
5
5
  description: Load relevant files and map the dependency graph for a task.
6
6
  category: utilities
7
+ behavior: static-analysis
8
+ intent: review-code
7
9
  priority: medium
8
10
  tags: [context, filesystem, dependencies, graph]
9
11
  platforms: [claude-code, cursor, windsurf, gemini-cli]
@@ -19,6 +21,7 @@ pipeline: [analyze, implement, complete]
19
21
  > **Goal:** "Người thu thập tình báo". Đảm bảo AI hiểu rõ môi trường xung quanh một file code trước khi tiến hành sửa nó, tránh lỗi thiếu context.
20
22
 
21
23
  ## 🔄 1. Chain of Thought (SOP)
24
+
22
25
  1. **Analyze (Target Identification):**
23
26
  - Identify the main file that needs modification.
24
27
  2. **Implement (Graph Traversal):**
@@ -29,9 +32,11 @@ pipeline: [analyze, implement, complete]
29
32
  - Build a mental map of how the data flows.
30
33
 
31
34
  ## 🛡️ 2. Constraints & Rules
35
+
32
36
  - **Token Optimization:** Do not load `node_modules` or massive minified build files. Extract only the exact logic needed.
33
37
 
34
38
  ## 🌳 3. Decision Tree
39
+
35
40
  ```text
36
41
  Is the target file a UI Component?
37
42
  ├── YES → Load its CSS/Theme tokens and any nested Child components.
@@ -39,9 +44,12 @@ Is the target file a UI Component?
39
44
  ```
40
45
 
41
46
  ## 🤝 4. Handoff Pipeline
47
+
42
48
  1. `complete`: Provide the context map to the Orchestrator or Target Skill.
43
49
 
44
50
  ## 📝 5. Output Format
51
+
45
52
  Vui lòng trả kết quả bằng Tiếng Việt.
53
+
46
54
  - **Tóm tắt (Summary):** Đã nạp thành công ngữ cảnh.
47
55
  - **Chi tiết (Changes):** Các file có liên quan trực tiếp.
@@ -1,9 +1,11 @@
1
1
  ---
2
2
  name: qk-data-lifecycle
3
- version: 3.0.0
3
+ version: 3.1.2
4
4
  updated: 2026-07-02
5
5
  description: Manage Database Schema, Migrations, and Repositories.
6
6
  category: database
7
+ behavior: development
8
+ intent: implement-feature
7
9
  priority: medium
8
10
  tags: [database, sql, migration, schema, orm]
9
11
  platforms: [claude-code, cursor, windsurf, gemini-cli]
@@ -19,6 +21,7 @@ pipeline: [analyze, design, implement, engineering-standard, validate, complete]
19
21
  > **Goal:** Quản lý an toàn vòng đời dữ liệu, đảm bảo Schema chuẩn xác, Migration có thể Rollback và Query tối ưu.
20
22
 
21
23
  ## 🔄 1. Chain of Thought (SOP)
24
+
22
25
  1. **Analyze (Requirements):**
23
26
  - Understand the entities and their relationships (1:1, 1:N, N:N).
24
27
  - Identify the ORM/Query Builder used in the project (e.g., Prisma, TypeORM, Drizzle).
@@ -33,11 +36,13 @@ pipeline: [analyze, design, implement, engineering-standard, validate, complete]
33
36
  - Review the migration script for destructive operations (e.g., `DROP TABLE`, `DROP COLUMN`).
34
37
 
35
38
  ## 🛡️ 2. Constraints & Rules
39
+
36
40
  - **No Data Loss:** NEVER execute a migration that drops data on Production without explicit User approval and a backup plan.
37
41
  - **Decoupling:** Do not write SQL queries directly in Controllers. Always use the Repository or DAO pattern.
38
42
  - **Index Rule:** Any column used in a `WHERE`, `JOIN`, or `ORDER BY` clause should be evaluated for an index.
39
43
 
40
44
  ## 🌳 3. Decision Tree
45
+
41
46
  ```text
42
47
  Is this modifying an existing table in Production?
43
48
  ├── YES → Does it drop a column or change a data type destructively?
@@ -47,12 +52,15 @@ Is this modifying an existing table in Production?
47
52
  ```
48
53
 
49
54
  ## 🤝 4. Handoff Pipeline
55
+
50
56
  1. `engineering-standard`: Verify naming conventions (e.g., snake_case for DB columns if required).
51
57
  2. `validate`: Run dry-run migrations or unit tests.
52
58
  3. `complete`: Generate the Database report.
53
59
 
54
60
  ## 📝 5. Output Format
61
+
55
62
  Vui lòng trả kết quả bằng Tiếng Việt.
63
+
56
64
  - **Tóm tắt (Summary):** Bảng nào được tạo/sửa.
57
65
  - **Chi tiết (Changes):** File migration và Model đã sinh ra.
58
66
  - **Kiến trúc (Reasoning):** Lý do thiết kế quan hệ bảng và các Index.
@@ -1,9 +1,11 @@
1
1
  ---
2
2
  name: qk-design-to-code
3
- version: 3.0.0
3
+ version: 3.1.2
4
4
  updated: 2026-07-02
5
5
  description: Convert Figma/Images to semantic, pixel-perfect code components.
6
6
  category: frontend
7
+ behavior: development
8
+ intent: implement-feature
7
9
  priority: high
8
10
  tags: [ui, figma, frontend, styling, css]
9
11
  platforms: [claude-code, cursor, windsurf, gemini-cli]
@@ -19,6 +21,7 @@ pipeline: [analyze, implement, engineering-standard, validate, complete]
19
21
  > **Goal:** Dịch thiết kế (Mockups/Images) thành mã nguồn (React, Vue, HTML/CSS) với độ chính xác Pixel-Perfect.
20
22
 
21
23
  ## 🔄 1. Chain of Thought (SOP)
24
+
22
25
  1. **Analyze (Deconstruct Design):**
23
26
  - Look at the provided mockup.
24
27
  - Break it down from Outside-In (Container -> Rows -> Columns -> Elements).
@@ -31,16 +34,20 @@ pipeline: [analyze, implement, engineering-standard, validate, complete]
31
34
  - Ensure the component uses relative units where necessary and scales on mobile.
32
35
 
33
36
  ## 🛡️ 2. Constraints & Rules
37
+
34
38
  - **No Magic Values:** Do not use random hex codes or pixel values if a Design System is available.
35
39
  - **Accessibility:** Always include `alt` for images and `aria-label` for icon-only buttons.
36
40
 
37
41
  ## 🤝 3. Handoff Pipeline
42
+
38
43
  1. `engineering-standard`: Ensure the UI component has no business logic.
39
44
  2. `validate`: Trigger `qk-ui-audit` checks.
40
45
  3. `complete`: Generate the UI Component Report.
41
46
 
42
47
  ## 📝 4. Output Format
48
+
43
49
  Vui lòng trả kết quả bằng Tiếng Việt.
50
+
44
51
  - **Tóm tắt (Summary):** Tên Component vừa tạo.
45
52
  - **Chi tiết (Changes):** File chứa component.
46
53
  - **Rủi ro (Risks):** Vấn đề responsive nếu có.
@@ -1,9 +1,11 @@
1
1
  ---
2
2
  name: qk-docs
3
- version: 3.0.0
3
+ version: 3.1.2
4
4
  updated: 2026-07-02
5
5
  description: Write and maintain human-readable project documentation.
6
6
  category: documentation
7
+ behavior: static-analysis
8
+ intent: maintain
7
9
  priority: low
8
10
  tags: [docs, markdown, jsdoc, readme]
9
11
  platforms: [claude-code, cursor, windsurf, gemini-cli]
@@ -19,6 +21,7 @@ pipeline: [analyze, implement, validate, complete]
19
21
  > **Goal:** Đóng vai trò là "Technical Writer". Viết tài liệu (README, API Docs, Code Comments) rõ ràng, dễ hiểu cho con người.
20
22
 
21
23
  ## 🔄 1. Chain of Thought (SOP)
24
+
22
25
  1. **Analyze (Context Extraction):**
23
26
  - Read the target source code to understand its Inputs, Outputs, and side effects.
24
27
  2. **Implement (Drafting):**
@@ -30,10 +33,12 @@ pipeline: [analyze, implement, validate, complete]
30
33
  - Ensure proper Markdown syntax (bolding, code blocks with languages).
31
34
 
32
35
  ## 🛡️ 2. Constraints & Rules
36
+
33
37
  - **Human Friendly:** Avoid overly academic language. Explain it as if explaining to a junior developer.
34
38
  - **Language Hybrid:** If writing Vietnamese documentation, keep technical keywords (props, state, endpoint, fetch) in English.
35
39
 
36
40
  ## 🌳 3. Decision Tree
41
+
37
42
  ```text
38
43
  Is this an API Documentation?
39
44
  ├── YES → Use standard REST/GraphQL documentation layout (Endpoint, Method, Body, Response).
@@ -43,10 +48,13 @@ Is this an API Documentation?
43
48
  ```
44
49
 
45
50
  ## 🤝 4. Handoff Pipeline
51
+
46
52
  1. `complete`: Generate the Docs and save them to the project files.
47
53
 
48
54
  ## 📝 5. Output Format
55
+
49
56
  Vui lòng trả kết quả bằng Tiếng Việt.
57
+
50
58
  - **Tóm tắt (Summary):** Tài liệu nào đã được tạo/cập nhật.
51
59
  - **Chi tiết (Changes):** Cấu trúc tài liệu.
52
60
  - **Xác thực (Verification):** Yêu cầu User đọc lướt qua tài liệu.
@@ -1,9 +1,11 @@
1
1
  ---
2
2
  name: qk-documentation-system
3
- version: 3.0.0
3
+ version: 3.1.2
4
4
  updated: 2026-07-02
5
5
  description: Maintain system-level architecture docs and DevOps runbooks.
6
6
  category: documentation
7
+ behavior: static-analysis
8
+ intent: maintain
7
9
  priority: low
8
10
  tags: [architecture, diagrams, mermaid, runbooks]
9
11
  platforms: [claude-code, cursor, windsurf, gemini-cli]
@@ -19,6 +21,7 @@ pipeline: [analyze, design, implement, complete]
19
21
  > **Goal:** Quản lý tài liệu cấp hệ thống (System Architecture, Sequence Diagrams, Runbooks).
20
22
 
21
23
  ## 🔄 1. Chain of Thought (SOP)
24
+
22
25
  1. **Analyze (System Flow):**
23
26
  - Understand the flow of data across microservices or complex components.
24
27
  2. **Design (Diagramming):**
@@ -27,12 +30,16 @@ pipeline: [analyze, design, implement, complete]
27
30
  - Save the documentation into the `/docs/` folder.
28
31
 
29
32
  ## 🛡️ 2. Constraints & Rules
33
+
30
34
  - **Syntax Check:** Ensure Mermaid diagrams are syntactically valid before saving.
31
35
 
32
36
  ## 🤝 3. Handoff Pipeline
37
+
33
38
  1. `complete`: Output the System Documentation Report.
34
39
 
35
40
  ## 📝 4. Output Format
41
+
36
42
  Vui lòng trả kết quả bằng Tiếng Việt.
43
+
37
44
  - **Tóm tắt (Summary):** Tài liệu kiến trúc nào đã được tạo.
38
45
  - **Chi tiết (Changes):** Đường dẫn file.
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: qk-engineering-standard
3
- version: 3.0.0
3
+ version: 3.1.2
4
4
  updated: 2026-07-02
5
5
  description: Enforce SOLID, DRY, Clean Code, and Naming conventions.
6
6
  category: standard
@@ -21,6 +21,7 @@ pipeline: [analyze, review, implement, validate, complete]
21
21
  > **Goal:** Đóng vai trò là "Kiến trúc sư trưởng", rà soát và ép buộc mã nguồn phải tuân thủ chuẩn mực Clean Code, dễ đọc và dễ bảo trì.
22
22
 
23
23
  ## 🔄 1. Chain of Thought (SOP)
24
+
24
25
  1. **Analyze (Context Review):**
25
26
  - Scan the target file(s) and determine their role (UI, Logic, API, Config).
26
27
  2. **Review (Smell Detection):**
@@ -35,11 +36,13 @@ pipeline: [analyze, review, implement, validate, complete]
35
36
  - Ensure the refactoring did NOT change the business logic or behavior of the app (Regression check).
36
37
 
37
38
  ## 🛡️ 3. Constraints & Rules
39
+
38
40
  - **Code is for Humans:** Write code that junior developers can easily understand. Avoid overly clever or obscure syntax.
39
41
  - **Scope Limit:** Do NOT refactor the entire project if the user only asked to review one file. Limit the scope to the current task context.
40
42
  - **Preserve Behavior:** Refactoring must strictly preserve backward compatibility.
41
43
 
42
44
  ## 🌳 3. Decision Tree
45
+
43
46
  ```text
44
47
  Is the file larger than 300 lines?
45
48
  ├── YES → Propose splitting the file into sub-components or moving logic to hooks.
@@ -51,11 +54,14 @@ Does the React Component contain `fetch()` or heavy data mapping?
51
54
  ```
52
55
 
53
56
  ## 🤝 4. Handoff Pipeline
57
+
54
58
  1. `validate`: Run static analysis (Linters, TypeScript compiler) to ensure the refactored code has no syntax errors.
55
59
  2. `complete`: Generate the review report.
56
60
 
57
61
  ## 📝 5. Output Format
62
+
58
63
  Vui lòng trả kết quả bằng Tiếng Việt. Cấu trúc báo cáo bao gồm:
64
+
59
65
  - **Tóm tắt (Summary):** File nào vừa được Refactor / Review.
60
66
  - **Chi tiết (Changes):** Các thay đổi cụ thể về Tên biến, Cấu trúc.
61
67
  - **Nguyên nhân (Reasoning):** Giải thích tại sao code cũ là "Bad Practice" và code mới tốt hơn thế nào.
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: qk-feature-delivery
3
- version: 3.0.0
3
+ version: 3.1.2
4
4
  updated: 2026-07-02
5
5
  description: Develop new features end-to-end (Frontend & Backend).
6
6
  category: engineering
@@ -21,6 +21,7 @@ pipeline: [analyze, implement, engineering-standard, validate, complete]
21
21
  > **Goal:** Phát triển một tính năng mới hoàn chỉnh, từ giao diện (Frontend) đến API (Backend) và Cơ sở dữ liệu (nếu có).
22
22
 
23
23
  ## 🔄 1. Chain of Thought (SOP)
24
+
24
25
  1. **Analyze (Requirements Gathering):**
25
26
  - Read the user's requirements.
26
27
  - Break down the feature into sub-tasks (e.g., Schema -> API -> UI Component -> Integration).
@@ -35,11 +36,13 @@ pipeline: [analyze, implement, engineering-standard, validate, complete]
35
36
  - Ensure the API handles edge cases (empty states, loading, error).
36
37
 
37
38
  ## 🛡️ 3. Constraints & Rules
39
+
38
40
  - **Contract First:** Always define the Type/Interface contract before writing the implementation logic.
39
41
  - **Component Reusability:** Do not create a new Button or Input if a Shared Component already exists in `src/components/shared/`.
40
42
  - **DRY (Don't Repeat Yourself):** Extract inline styles or duplicate logic into hooks/utilities.
41
43
 
42
44
  ## 🌳 3. Decision Tree
45
+
43
46
  ```text
44
47
  Does the feature require Backend API changes?
45
48
  ├── YES → Start with Database Schema/Types -> API Route -> UI Integration.
@@ -49,14 +52,19 @@ Does the feature require Backend API changes?
49
52
  ```
50
53
 
51
54
  ## 🤝 4. Handoff Pipeline
55
+
52
56
  After implementing the feature, map to the pipeline:
57
+
53
58
  1. `engineering-standard`: Ensure naming conventions and file size limits are respected.
54
59
  2. `validate`: Run tests and format the code.
55
60
  3. `complete`: Output the final report.
56
61
 
57
62
  ## 📝 5. Output Format
63
+
58
64
  Vui lòng báo cáo lại bằng Tiếng Việt với cấu trúc tương tự `templates/bug-report.md` nhưng thay đổi tiêu đề thành:
65
+
59
66
  ### 🚀 Báo Cáo Triển Khai Tính Năng (Feature Report)
67
+
60
68
  - **Tóm tắt (Summary):** Tính năng gì đã được làm.
61
69
  - **Chi tiết (Changes):** Liệt kê các file tạo mới / chỉnh sửa.
62
70
  - **Kiến trúc (Reasoning):** Giải thích quyết định thiết kế State/API.
@@ -1,9 +1,11 @@
1
1
  ---
2
2
  name: qk-help
3
- version: 3.0.0
3
+ version: 3.1.2
4
4
  updated: 2026-07-02
5
5
  description: Display the list of available skills and pro-tips.
6
6
  category: utilities
7
+ behavior: static-analysis
8
+ intent: review-code
7
9
  priority: low
8
10
  tags: [help, manual, list, tutorial]
9
11
  platforms: [claude-code, cursor, windsurf, gemini-cli]
@@ -19,19 +21,24 @@ pipeline: [analyze, complete]
19
21
  > **Goal:** Bản đồ hướng dẫn sử dụng Agent Skills. Giúp User tra cứu nhanh lệnh.
20
22
 
21
23
  ## 🔄 1. Chain of Thought (SOP)
24
+
22
25
  1. **Analyze (Scan):**
23
26
  - Read the skills directory to list all available tools.
24
27
  2. **Complete (Format):**
25
28
  - Format the skills into a neat Markdown table.
26
29
 
27
30
  ## 🛡️ 2. Constraints & Rules
31
+
28
32
  - **Keep it short:** Do not print the entire content of `SKILL.md`. Only print the Name and Description from the metadata.
29
33
 
30
34
  ## 🤝 3. Handoff Pipeline
35
+
31
36
  1. `complete`: Output the Help table.
32
37
 
33
38
  ## 📝 4. Output Format
39
+
34
40
  Vui lòng trả kết quả bằng Tiếng Việt dạng Bảng (Table).
41
+
35
42
  - **Cột 1:** Tên Skill
36
43
  - **Cột 2:** Mô tả ngắn (Tiếng Việt)
37
44
  - **Cột 3:** Lệnh kích hoạt (Ví dụ: `@qk-bug-resolution`)
@@ -1,9 +1,11 @@
1
1
  ---
2
2
  name: qk-orchestrator
3
- version: 3.0.0
3
+ version: 3.1.2
4
4
  updated: 2026-07-02
5
5
  description: Route user requests, parse intents, and delegate to the correct sub-skills.
6
6
  category: orchestration
7
+ behavior: static-analysis
8
+ intent: review-code
7
9
  priority: critical
8
10
  tags: [router, orchestrator, delegation, ai-manager]
9
11
  platforms: [claude-code, cursor, windsurf, gemini-cli]
@@ -19,6 +21,7 @@ pipeline: [analyze, plan, delegate]
19
21
  > **Goal:** "Tổng tư lệnh" (Master Orchestrator). Phân tích ý đồ của người dùng và điều phối các kỹ năng (Skills) khác để giải quyết vấn đề thay vì làm mọi thứ một cách thủ công.
20
22
 
21
23
  ## 🔄 1. Chain of Thought (SOP)
24
+
22
25
  1. **Analyze (Intent Parsing):**
23
26
  - Read the user's request. Determine the goal: Is it a Bug Fix, a New Feature, a Refactor, or just a Question?
24
27
  2. **Plan (Context Gathering & Skill Selection):**
@@ -28,10 +31,12 @@ pipeline: [analyze, plan, delegate]
28
31
  - Handoff the gathered context to the selected Skill.
29
32
 
30
33
  ## 🛡️ 2. Constraints & Rules
34
+
31
35
  - **Delegation First:** Do not write source code directly while acting as the Orchestrator. Delegate to the correct specialized Skill.
32
36
  - **Ambiguity Check:** If the user's intent is unclear, give them 2-3 Skill suggestions to choose from.
33
37
 
34
38
  ## 🌳 3. Decision Tree
39
+
35
40
  ```text
36
41
  Is the task a massive project (e.g., "Build an Admin Dashboard")?
37
42
  ├── YES → Break it down:
@@ -43,10 +48,13 @@ Is the task a massive project (e.g., "Build an Admin Dashboard")?
43
48
  ```
44
49
 
45
50
  ## 🤝 4. Handoff Pipeline
51
+
46
52
  1. `delegate`: Call the target Skill.
47
53
 
48
54
  ## 📝 5. Output Format
55
+
49
56
  Vui lòng trả kết quả bằng Tiếng Việt.
57
+
50
58
  - **Tóm tắt (Summary):** Đã phân tích xong yêu cầu của User.
51
59
  - **Quyết định điều phối (Reasoning):** Giao việc cho Skill nào.
52
60
  - **Hành động tiếp (Next Action):** Tự động chuyển vai trò sang Skill được chọn.
@@ -1,9 +1,11 @@
1
1
  ---
2
2
  name: qk-policy-engine
3
- version: 3.0.0
3
+ version: 3.1.2
4
4
  updated: 2026-07-02
5
5
  description: Policy evaluation engine to ensure actions are authorized and safe.
6
6
  category: security
7
+ behavior: static-analysis
8
+ intent: review-code
7
9
  priority: high
8
10
  tags: [security, policy, guardrails, authorization]
9
11
  platforms: [claude-code, cursor, windsurf, gemini-cli]
@@ -19,6 +21,7 @@ pipeline: [analyze, evaluate, complete]
19
21
  > **Goal:** Đóng vai trò là "Bộ quy tắc thép" (Policy Enforcer). Ngăn chặn các lệnh sai lầm có thể phá hoại hệ thống.
20
22
 
21
23
  ## 🔄 1. Chain of Thought (SOP)
24
+
22
25
  1. **Analyze (Risk Assessment):**
23
26
  - Classify the user's request (Low, Medium, High risk).
24
27
  - High Risk: Dropping databases, deleting multiple files, force-pushing to `main`.
@@ -29,10 +32,12 @@ pipeline: [analyze, evaluate, complete]
29
32
  - Approve (Allow execution) or Deny (Block execution) with explicit reasons.
30
33
 
31
34
  ## 🛡️ 2. Constraints & Rules
35
+
32
36
  - **Deny by Default:** If an action is highly destructive and no backup plan exists, DENY it.
33
37
  - **Override:** Only allow skipping the policy if the user explicitly passes an `--override` flag in their prompt.
34
38
 
35
39
  ## 🌳 3. Decision Tree
40
+
36
41
  ```text
37
42
  Does the action involve deleting data or resources in Production?
38
43
  ├── YES → Has the user provided a backup confirmation?
@@ -42,10 +47,13 @@ Does the action involve deleting data or resources in Production?
42
47
  ```
43
48
 
44
49
  ## 🤝 4. Handoff Pipeline
50
+
45
51
  1. `complete`: Generate the Policy Decision Report.
46
52
 
47
53
  ## 📝 5. Output Format
54
+
48
55
  Vui lòng trả kết quả bằng Tiếng Việt.
56
+
49
57
  - **Tóm tắt (Summary):** Mức độ rủi ro (Risk Level).
50
58
  - **Phán quyết (Decision):** ✅ APPROVED hoặc ❌ DENIED.
51
59
  - **Nguyên nhân (Reasoning):** Vi phạm chính sách nào (nếu bị Deny).
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: qk-production-release
3
- version: 3.0.0
3
+ version: 3.1.2
4
4
  updated: 2026-07-02
5
5
  description: Prepare the codebase for a production release (Build, CI/CD, Security).
6
6
  category: operations
@@ -21,6 +21,7 @@ pipeline: [analyze, review, implement, validate, complete]
21
21
  > **Goal:** Chuẩn bị gói phần mềm để đẩy lên môi trường Production an toàn và tối ưu nhất (Minified, Tree-shaked).
22
22
 
23
23
  ## 🔄 1. Chain of Thought (SOP)
24
+
24
25
  1. **Analyze (Pre-flight Checks):**
25
26
  - Check if the git branch is clean.
26
27
  - Verify environment variables are documented.
@@ -32,15 +33,19 @@ pipeline: [analyze, review, implement, validate, complete]
32
33
  - Provide a manual checklist for the user to execute the final deployment.
33
34
 
34
35
  ## 🛡️ 3. Constraints & Rules
36
+
35
37
  - **No Rogue Deploys:** Never run commands like `firebase deploy` or `vercel --prod` without explicit, undeniable user approval.
36
38
  - **Secret Safety:** Never hardcode URLs. Ensure they are injected via ENV.
37
39
 
38
40
  ## 🤝 3. Handoff Pipeline
41
+
39
42
  1. `validate`: Run security sweep on the build output.
40
43
  2. `complete`: Output the Release Report.
41
44
 
42
45
  ## 📝 4. Output Format
46
+
43
47
  Vui lòng trả kết quả bằng Tiếng Việt.
48
+
44
49
  - **Tóm tắt (Summary):** Trạng thái Build.
45
50
  - **Chi tiết (Changes):** Dung lượng Bundle (Bundle size optimization).
46
51
  - **Rủi ro (Risks):** Có lộ secret không.
@@ -1,9 +1,11 @@
1
1
  ---
2
2
  name: qk-project-bootstrap
3
- version: 3.0.0
3
+ version: 3.1.2
4
4
  updated: 2026-07-02
5
5
  description: Initialize a new project with best practices, linters, and folder structures.
6
6
  category: setup
7
+ behavior: development
8
+ intent: implement-feature
7
9
  priority: high
8
10
  tags: [bootstrap, scaffolding, setup, init]
9
11
  platforms: [claude-code, cursor, windsurf, gemini-cli]
@@ -19,6 +21,7 @@ pipeline: [analyze, implement, engineering-standard, validate, complete]
19
21
  > **Goal:** "Thợ xây móng". Khởi tạo một dự án mới hoàn toàn với các cấu hình chuẩn mực nhất từ Day 1.
20
22
 
21
23
  ## 🔄 1. Chain of Thought (SOP)
24
+
22
25
  1. **Analyze (Requirements):**
23
26
  - Ask the user for their preferred stack (e.g., Next.js, Vite, NestJS).
24
27
  2. **Implement (Scaffolding):**
@@ -29,15 +32,19 @@ pipeline: [analyze, implement, engineering-standard, validate, complete]
29
32
  - Run `npm run dev` in a short background task to ensure it doesn't crash.
30
33
 
31
34
  ## 🛡️ 2. Constraints & Rules
35
+
32
36
  - **Strict Mode:** Always enable `strict: true` in TypeScript configurations.
33
37
  - **Package Manager Check:** If the user uses `pnpm`, do NOT run `npm install`. Stick to one package manager.
34
38
 
35
39
  ## 🤝 3. Handoff Pipeline
40
+
36
41
  1. `engineering-standard`: Verify the generated folder structure.
37
42
  2. `complete`: Output the Bootstrap Report.
38
43
 
39
44
  ## 📝 4. Output Format
45
+
40
46
  Vui lòng trả kết quả bằng Tiếng Việt.
47
+
41
48
  - **Tóm tắt (Summary):** Dự án đã được khởi tạo với Stack nào.
42
49
  - **Chi tiết (Changes):** Cấu trúc thư mục mới và các file cấu hình.
43
50
  - **Xác thực (Verification):** Cách chạy dự án.
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: qk-project-health
3
- version: 3.0.0
3
+ version: 3.1.2
4
4
  updated: 2026-07-02
5
5
  description: Comprehensive audit of Code Smells, Tech Debt, and Architecture.
6
6
  category: architecture
@@ -21,6 +21,7 @@ pipeline: [analyze, review, validate, complete]
21
21
  > **Goal:** "Khám sức khỏe" toàn diện cho Codebase. Tìm ra các Nợ Kỹ Thuật (Tech Debt), Mã Lỗi Thời (Code Smells), và các rủi ro cấu trúc dài hạn.
22
22
 
23
23
  ## 🔄 1. Chain of Thought (SOP)
24
+
24
25
  1. **Analyze (Dependency Scan):**
25
26
  - Read `package.json` to identify outdated libraries, bloated dependencies, or unused packages.
26
27
  2. **Review (Architecture Scan):**
@@ -33,10 +34,12 @@ pipeline: [analyze, review, validate, complete]
33
34
  - Generate a prioritized Refactor Roadmap (High, Medium, Low).
34
35
 
35
36
  ## 🛡️ 3. Constraints & Rules
37
+
36
38
  - **Audit Only - No Touch:** Do not modify any code. You are diagnosing, not performing surgery.
37
39
  - **Evidence Based:** Provide concrete metrics (e.g., "Folder `components` has 45 files, making it hard to navigate").
38
40
 
39
41
  ## 🌳 3. Decision Tree
42
+
40
43
  ```text
41
44
  Is the `src/components` folder bloated (>30 files)?
42
45
  ├── YES → Recommend migrating to a Feature-driven structure (e.g., `src/features/auth`).
@@ -48,10 +51,13 @@ Are there components exceeding 500 lines?
48
51
  ```
49
52
 
50
53
  ## 🤝 4. Handoff Pipeline
54
+
51
55
  1. `complete`: Output the Health Audit Report.
52
56
 
53
57
  ## 📝 5. Output Format
58
+
54
59
  Vui lòng trả kết quả bằng Tiếng Việt.
60
+
55
61
  - **Tóm tắt (Summary):** Đánh giá tổng quan Sức Khỏe Dự Án (Điểm: X/100).
56
62
  - **Chi tiết (Changes):** Phân tích Dependencies, Architecture, Code Smells.
57
63
  - **Xác thực (Verification):** Các bằng chứng thu thập được từ code (dòng nào, file nào phình to).
@@ -1,9 +1,11 @@
1
1
  ---
2
2
  name: qk-project-memory
3
- version: 3.0.0
3
+ version: 3.1.2
4
4
  updated: 2026-07-02
5
5
  description: Store and retrieve long-term project context across sessions.
6
6
  category: utilities
7
+ behavior: static-analysis
8
+ intent: maintain
7
9
  priority: low
8
10
  tags: [memory, context, storage]
9
11
  platforms: [claude-code, cursor, windsurf, gemini-cli]
@@ -19,17 +21,22 @@ pipeline: [analyze, implement, complete]
19
21
  > **Goal:** "Bộ nhớ dài hạn". Giúp Agent nhớ lại các cấu hình, đường dẫn API hoặc luật lệ riêng của dự án mà không cần User nhắc lại.
20
22
 
21
23
  ## 🔄 1. Chain of Thought (SOP)
24
+
22
25
  1. **Analyze (Fact Extraction):**
23
26
  - Extract the core facts from the conversation (e.g., "The project uses pnpm, not npm").
24
27
  2. **Implement (Storage):**
25
28
  - Append the fact to `.ai-memory.md` or a similar configuration file.
26
29
 
27
30
  ## 🛡️ 2. Constraints & Rules
31
+
28
32
  - **Keep it small:** Do not write entire source files into memory. Only save abstract facts and rules.
29
33
 
30
34
  ## 🤝 3. Handoff Pipeline
35
+
31
36
  1. `complete`: Output confirmation.
32
37
 
33
38
  ## 📝 4. Output Format
39
+
34
40
  Vui lòng trả kết quả bằng Tiếng Việt.
41
+
35
42
  - **Tóm tắt (Summary):** Đã ghi nhớ thông tin gì.