ai-developer-skill-os 3.1.5 → 6.0.0-rc1

package/skills/qk-engineering-standard/SKILL.md

@@ -1,69 +1,38 @@
 ---
 name: qk-engineering-standard
-version: 3.1.5
-updated: 2026-07-02
-description: Ép buộc áp dụng SOLID, DRY, Clean Code, và các quy tắc đặt tên.
-category: standard
-behavior: static-analysis
-intent: review-code
-priority: critical
-tags: [clean-code, architecture, refactoring, solid]
-platforms: [claude-code, cursor, windsurf, gemini-cli]
-trigger: User asks to review code, refactor code, or as part of the pipeline before validation.
-inputs: [Source Code, Target Directory]
-outputs: [Refactored Code, Code Review Report]
-allowed_tools: [grep_search, read_file, write_to_file]
-pipeline: [analyze, review, implement, validate, complete]
+category: conventions
+version: 6.0.0
 ---
 
-# 🛠️ qk-engineering-standard - Standard Operating Procedure
+# qk-engineering-standard
 
-> **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ì.
+## Scope
+- Readability and structural improvements (Evaluate)
 
-## 🔄 1. Chain of Thought (SOP)
-
-1. **Analyze (Context Review):**
-   - Scan the target file(s) and determine their role (UI, Logic, API, Config).
-2. **Review (Smell Detection):**
-   - Check for Naming violations (e.g., `temp`, `data`, `res` instead of `userData`).
-   - Check for Magic Numbers/Strings.
-   - Check for God Components (Files > 300 lines or > 3 responsibilities).
-3. **Implement (Refactoring):**
-   - Extract inline styles or raw strings into constants.
-   - Split large components into smaller, pure components.
-   - Separate UI rendering from Business Logic (Custom Hooks).
-4. **Verify (Validation):**
-   - Ensure the refactoring did NOT change the business logic or behavior of the app (Regression check).
-
-## 🛡️ 3. Constraints & Rules
-
-- **Code is for Humans:** Write code that junior developers can easily understand. Avoid overly clever or obscure syntax.
-- **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.
-- **Preserve Behavior:** Refactoring must strictly preserve backward compatibility.
-
-## 🌳 3. Decision Tree
-
-```text
-Is the file larger than 300 lines?
-  ├── YES → Propose splitting the file into sub-components or moving logic to hooks.
-  └── NO → Continue normal inspection.
-
-Does the React Component contain `fetch()` or heavy data mapping?
-  ├── YES → Extract the logic into a separate `use[Feature]Data.ts` hook.
-  └── NO → Pass.
+## Constraints
+```yaml
+must:
+  - Preserve business logic exactly
+  - Ensure tests pass after refactor
+must_not:
+  - Invent new requirements
+  - Change public API signature
 ```
 
-## 🤝 4. Handoff Pipeline
-
-1. `validate`: Run static analysis (Linters, TypeScript compiler) to ensure the refactored code has no syntax errors.
-2. `complete`: Generate the review report.
-
-## 📝 5. Output Format
+## Policies
+```yaml
+prefer:
+  - Readability over cleverness
+  - Explain trade-offs
+```
 
-Vui lòng trả kết quả bằng Tiếng Việt. Cấu trúc báo cáo bao gồm:
+## Escalation
+```yaml
+stop:
+  - Tests fail
+```
 
-- **Tóm tắt (Summary):** File nào vừa được Refactor / Review.
-- **Chi tiết (Changes):** Các thay đổi cụ thể về Tên biến, Cấu trúc.
-- **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.
-- **Xác thực (Verification):** Đảm bảo code chạy không lỗi.
-- **Hành động tiếp (Next Action):** Bàn giao lại cho Pipeline.
+## Output
+- Evaluation summary
+- Refactored code
+```

package/skills/qk-feature-delivery/SKILL.md

@@ -1,74 +1,39 @@
 ---
 name: qk-feature-delivery
-version: 3.1.5
-updated: 2026-07-02
-description: Phát triển tính năng mới hoàn chỉnh từ Frontend đến Backend.
-category: engineering
-behavior: development
-intent: implement-feature
-priority: high
-tags: [feature, development, e2e, ui, api]
-platforms: [claude-code, cursor, windsurf, gemini-cli]
-trigger: User asks to create a new page, component, or endpoint.
-inputs: [Feature requirements, Design/Mockup (optional)]
-outputs: [Implemented code, Test cases]
-allowed_tools: [run_command, read_file, write_to_file, grep_search]
-pipeline: [analyze, implement, engineering-standard, validate, complete]
+category: fullstack
+version: 6.0.0
 ---
 
-# 🛠️ qk-feature-delivery - Standard Operating Procedure
+# qk-feature-delivery
 
-> **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ó).
+## Scope
+- New capabilities (Execute)
 
-## 🔄 1. Chain of Thought (SOP)
-
-1. **Analyze (Requirements Gathering):**
-   - Read the user's requirements.
-   - Break down the feature into sub-tasks (e.g., Schema -> API -> UI Component -> Integration).
-2. **Plan (Architecture & Design):**
-   - Identify if you need to load specific knowledge files (e.g., `knowledge/frontend/react.md`).
-   - Define data interfaces (TypeScript Types/Interfaces) first.
-3. **Execute (Implementation):**
-   - Build the backend/API mock first (if applicable).
-   - Build the UI component and bind the data.
-4. **Verify (Validation):**
-   - **4 UI States:** Implement all 4 UI states: `Loading` (Skeleton/Spinner), `Success` (Data), `Error` (Fallback UI/Retry), and `Empty` (No data).
-   - Check if the UI is responsive (works well on Mobile & Desktop).
-
-## 🛡️ 3. Constraints & Rules
-
-- **Contract First:** Always define the Type/Interface contract before writing the implementation logic.
-- **State Management:** Lift state to Global (Redux/Zustand/Context) only if 2 or more components outside the same parent/child tree need to share it. Do not abuse Global State.
-- **Component Reusability:** Do not create a new Button or Input if a Shared Component already exists in `src/components/shared/`.
-- **DRY (Don't Repeat Yourself):** Extract inline styles or duplicate logic into hooks/utilities.
-
-## 🌳 3. Decision Tree
-
-```text
-Does the feature require Backend API changes?
-  ├── YES → Start with Database Schema/Types -> API Route -> UI Integration.
-  └── NO → Is it a purely visual UI component?
-             ├── YES → Load UI/Design tokens and implement.
-             └── NO (Stateful) → Load `knowledge/frontend/react.md` to design the State Management strategy.
+## Constraints
+```yaml
+must:
+  - Clarify requirements if unclear
+  - Implement complete end-to-end flow
+must_not:
+  - Mix refactoring into feature work
+  - Ignore backward compatibility
 ```
 
-## 🤝 4. Handoff Pipeline
-
-After implementing the feature, map to the pipeline:
-
-1. `engineering-standard`: Ensure naming conventions and file size limits are respected.
-2. `validate`: Run tests and format the code.
-3. `complete`: Output the final report.
-
-## 📝 5. Output Format
-
-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:
+## Policies
+```yaml
+prefer:
+  - Plan before implementing
+  - Cover UI loading/error states
+```
 
-### 🚀 Báo Cáo Triển Khai Tính Năng (Feature Report)
+## Escalation
+```yaml
+stop:
+  - Requirements are ambiguous
+ask:
+  - Before adding heavy dependencies
+```
 
-- **Tóm tắt (Summary):** Tính năng gì đã được làm.
-- **Chi tiết (Changes):** Liệt kê các file tạo mới / chỉnh sửa.
-- **Kiến trúc (Reasoning):** Giải thích quyết định thiết kế State/API.
-- **Xác thực (Verification):** Các bước để user test thử.
-- **Rủi ro (Risks):** Có làm chậm hệ thống hay bundle size không.
-- **Hành động tiếp (Next Action):** ...
+## Output
+- Feature implementation
+```

package/skills/qk-help/SKILL.md

@@ -1,44 +1,34 @@
 ---
 name: qk-help
-version: 3.1.5
-updated: 2026-07-02
-description: Hiển thị danh sách các kỹ năng hiện có và các mẹo sử dụng.
-category: utilities
-behavior: static-analysis
-intent: review-code
-priority: low
-tags: [help, manual, list, tutorial]
-platforms: [claude-code, cursor, windsurf, gemini-cli]
-trigger: User types 'help', asks for a list of skills, or doesn't know how to use the agent.
-inputs: [Help query]
-outputs: [List of skills, Tips]
-allowed_tools: [read_file, list_dir]
-pipeline: [analyze, complete]
+category: core
+version: 6.0.0
 ---
 
-# 🛠️ qk-help - Standard Operating Procedure
-
-> **Goal:** Bản đồ hướng dẫn sử dụng Agent Skills. Giúp User tra cứu nhanh lệnh.
-
-## 🔄 1. Chain of Thought (SOP)
-
-1. **Analyze (Scan):**
-   - Read the skills directory to list all available tools.
-2. **Complete (Format):**
-   - Format the skills into a neat Markdown table.
-
-## 🛡️ 2. Constraints & Rules
-
-- **Keep it short:** Do not print the entire content of `SKILL.md`. Only print the Name and Description from the metadata.
-
-## 🤝 3. Handoff Pipeline
-
-1. `complete`: Output the Help table.
-
-## 📝 4. Output Format
-
-Vui lòng trả kết quả bằng Tiếng Việt dạng Bảng (Table).
-
-- **Cột 1:** Tên Skill
-- **Cột 2:** Mô tả ngắn (Tiếng Việt)
-- **Cột 3:** Lệnh kích hoạt (Ví dụ: `@qk-bug-resolution`)
+# qk-help
+
+## Scope
+- Displaying available skills and usage tips (Collect & Delegate)
+
+## Constraints
+```yaml
+must:
+  - Present information clearly and concisely
+must_not:
+  - Hallucinate skills that do not exist in the repository
+```
+
+## Policies
+```yaml
+prefer:
+  - Short, actionable examples over long descriptions
+```
+
+## Escalation
+```yaml
+ask:
+  - If the user's intent is unclear when asking for help
+```
+
+## Output
+- List of available skills and usage instructions
+```

package/skills/qk-orchestrator/SKILL.md

@@ -1,61 +1,35 @@
 ---
 name: qk-orchestrator
-version: 3.1.5
-updated: 2026-07-02
-description: Điều hướng yêu cầu của người dùng, phân tích ý định và ủy quyền cho các sub-skills phù hợp.
-category: orchestration
-behavior: static-analysis
-intent: review-code
-priority: critical
-tags: [router, orchestrator, delegation, ai-manager]
-platforms: [claude-code, cursor, windsurf, gemini-cli]
-trigger: Triggered initially when the user provides a vague or complex multi-step request.
-inputs: [User intent, Raw Context]
-outputs: [Workflow routing, Sub-skill delegation]
-allowed_tools: [grep_search, read_file]
-pipeline: [analyze, plan, delegate]
+category: core
+version: 6.0.0
 ---
 
-# 🛠️ qk-orchestrator - Standard Operating Procedure
+# qk-orchestrator
 
-> **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.
+## Scope
+- Request analysis and task delegation (Coordinate)
 
-## 🔄 1. Chain of Thought (SOP)
-
-1. **Analyze (Intent Parsing):**
-   - Read the user's request. Determine the goal: Is it a Bug Fix, a New Feature, a Refactor, or just a Question?
-2. **Plan (Context Gathering & Skill Selection):**
-   - Determine which specific files are needed.
-   - Select the most appropriate Skill (e.g., `qk-feature-delivery` for new UI, `qk-bug-resolution` for fixing errors).
-3. **Delegate (Handoff):**
-   - Handoff the gathered context to the selected Skill.
-
-## 🛡️ 2. Constraints & Rules
-
-- **Cost-Awareness:** Evaluate task complexity. If the task is trivial (e.g., fix a typo, change display text), solve it directly to save tokens.
-- **Delegation First:** For complex tasks, do not write source code directly. Delegate to the correct specialized Skill.
-- **Ambiguity Check:** If the user's intent is unclear, give them 2-3 Skill suggestions to choose from.
-
-## 🌳 3. Decision Tree
-
-```text
-Is the task a massive project (e.g., "Build an Admin Dashboard")?
-  ├── YES → Break it down:
-  │       1. `qk-project-bootstrap` (Setup)
-  │       2. `qk-data-lifecycle` (DB Schema)
-  │       3. `qk-api-lifecycle` (Endpoints)
-  │       4. `qk-feature-delivery` (UI).
-  └── NO → Delegate to the single most appropriate skill.
+## Constraints
+```yaml
+must:
+  - Route user request to the correct sub-skill
+must_not:
+  - Write code directly
+  - Hallucinate non-existent skills
 ```
 
-## 🤝 4. Handoff Pipeline
-
-1. `delegate`: Call the target Skill.
-
-## 📝 5. Output Format
+## Policies
+```yaml
+prefer:
+  - Delegate to specialist skills
+```
 
-Vui lòng trả kết quả bằng Tiếng Việt.
+## Escalation
+```yaml
+stop:
+  - No matching skill is found
+```
 
-- **Tóm tắt (Summary):** Đã phân tích xong yêu cầu của User.
-- **Quyết định điều phối (Reasoning):** Giao việc cho Skill nào.
-- **Hành động tiếp (Next Action):** Tự động chuyển vai trò sang Skill được chọn.
+## Output
+- Delegation plan
+```

package/skills/qk-policy-engine/SKILL.md

@@ -1,60 +1,35 @@
 ---
 name: qk-policy-engine
-version: 3.1.5
-updated: 2026-07-02
-description: Hệ thống đánh giá chính sách để đảm bảo các hành động an toàn và được ủy quyền.
 category: security
-behavior: static-analysis
-intent: review-code
-priority: high
-tags: [security, policy, guardrails, authorization]
-platforms: [claude-code, cursor, windsurf, gemini-cli]
-trigger: User asks to perform a high-risk destructive action (e.g., DROP table, mass delete).
-inputs: [Requested Action, Context]
-outputs: [Approval/Denial, Policy violations]
-allowed_tools: [read_file]
-pipeline: [analyze, evaluate, complete]
+version: 6.0.0
 ---
 
-# 🛠️ qk-policy-engine - Standard Operating Procedure
+# qk-policy-engine
 
-> **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.
+## Scope
+- System policy evaluation for safe and authorized actions (Govern)
 
-## 🔄 1. Chain of Thought (SOP)
-
-1. **Analyze (Risk Assessment):**
-   - Classify the user's request (Low, Medium, High risk).
-   - High Risk: Dropping databases, deleting multiple files, force-pushing to `main`.
-2. **Evaluate (Policy Check):**
-   - Load security policies (from `.agents/AGENTS.md` or `.cursorrules`).
-   - Check if the action violates any safety constraints.
-3. **Complete (Decision):**
-   - Approve (Allow execution) or Deny (Block execution) with explicit reasons.
-
-## 🛡️ 2. Constraints & Rules
-
-- **Deny by Default:** If an action is highly destructive and no backup plan exists, DENY it.
-- **Override:** Only allow skipping the policy if the user explicitly passes an `--override` flag in their prompt.
-
-## 🌳 3. Decision Tree
-
-```text
-Does the action involve deleting data or resources in Production?
-  ├── YES → Has the user provided a backup confirmation?
-  │       ├── YES → Approve.
-  │       └── NO → DENY and request backup confirmation.
-  └── NO → Approve.
+## Constraints
+```yaml
+must:
+  - Evaluate requested actions against defined system constraints
+  - Enforce OS-level invariants
+must_not:
+  - Allow destructive commands (e.g. rm -rf /) to bypass checks
 ```
 
-## 🤝 4. Handoff Pipeline
-
-1. `complete`: Generate the Policy Decision Report.
-
-## 📝 5. Output Format
+## Policies
+```yaml
+prefer:
+  - Strict adherence to policy over convenience
+```
 
-Vui lòng trả kết quả bằng Tiếng Việt.
+## Escalation
+```yaml
+stop:
+  - Action explicitly violates core safety policies
+```
 
-- **Tóm tắt (Summary):** Mức độ rủi ro (Risk Level).
-- **Phán quyết (Decision):** ✅ APPROVED hoặc ❌ DENIED.
-- **Nguyên nhân (Reasoning):** Vi phạm chính sách nào (nếu bị Deny).
-- **Hành động tiếp (Next Action):** ...
+## Output
+- Policy evaluation result (Allow/Deny)
+```

package/skills/qk-production-release/SKILL.md

@@ -1,52 +1,35 @@
 ---
 name: qk-production-release
-version: 3.1.5
-updated: 2026-07-02
-description: Chuẩn bị codebase để phát hành lên production (Build, CI/CD, Security).
-category: operations
-behavior: validation
-intent: validate
-priority: high
-tags: [deploy, release, build, production]
-platforms: [claude-code, cursor, windsurf, gemini-cli]
-trigger: User asks to deploy the app, build for production, or release a new version.
-inputs: [Release request, Environment configs]
-outputs: [Deployment artifacts, Release checklist]
-allowed_tools: [run_command, grep_search]
-pipeline: [analyze, review, implement, validate, complete]
+category: devops
+version: 6.0.0
 ---
 
-# 🛠️ qk-production-release - Standard Operating Procedure
-
-> **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).
-
-## 🔄 1. Chain of Thought (SOP)
-
-1. **Analyze (Pre-flight Checks):**
-   - Check if the git branch is clean.
-   - Verify environment variables are documented.
-2. **Implement (Build & Optimize):**
-   - Run `npm run build`.
-3. **Validate (Security Gate):**
-   - Scan the build output (e.g., `dist/` or `.next/`) for leaked API Keys (`grep_search`).
-4. **Complete (Deployment Plan):**
-   - Provide a manual checklist for the user to execute the final deployment.
-
-## 🛡️ 3. Constraints & Rules
-
-- **No Rogue Deploys:** Never run commands like `firebase deploy` or `vercel --prod` without explicit, undeniable user approval.
-- **Secret Safety:** Never hardcode URLs. Ensure they are injected via ENV.
-
-## 🤝 3. Handoff Pipeline
-
-1. `validate`: Run security sweep on the build output.
-2. `complete`: Output the Release Report.
-
-## 📝 4. Output Format
-
-Vui lòng trả kết quả bằng Tiếng Việt.
-
-- **Tóm tắt (Summary):** Trạng thái Build.
-- **Chi tiết (Changes):** Dung lượng Bundle (Bundle size optimization).
-- **Rủi ro (Risks):** Có lộ secret không.
-- **Hành động tiếp (Next Action):** Checklist để user tự Deploy.
+# qk-production-release
+
+## Scope
+- Preparing codebase for production release including Build, CI/CD, and Security checks (Plan & Govern)
+
+## Constraints
+```yaml
+must:
+  - Verify that all tests pass and linters are clean
+  - Check for exposed secrets or misconfigurations
+must_not:
+  - Deploy code that fails security audits
+```
+
+## Policies
+```yaml
+prefer:
+  - Immutable artifacts and deterministic builds
+```
+
+## Escalation
+```yaml
+stop:
+  - Security vulnerabilities or critical test failures are detected
+```
+
+## Output
+- Release checklist and deployment readiness status
+```

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

@@ -1,50 +1,36 @@
 ---
 name: qk-project-bootstrap
-version: 3.1.5
-updated: 2026-07-02
-description: Khởi tạo dự án mới với các best practices, linters, và cấu trúc thư mục chuẩn.
-category: setup
-behavior: development
-intent: implement-feature
-priority: high
-tags: [bootstrap, scaffolding, setup, init]
-platforms: [claude-code, cursor, windsurf, gemini-cli]
-trigger: User asks to start a new project, create a new repo, or setup standard configurations.
-inputs: [Stack selection, Project Name]
-outputs: [Scaffolded Codebase, Configs]
-allowed_tools: [run_command, write_to_file]
-pipeline: [analyze, implement, engineering-standard, validate, complete]
+category: fullstack
+version: 6.0.0
 ---
 
-# 🛠️ qk-project-bootstrap - Standard Operating Procedure
-
-> **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.
-
-## 🔄 1. Chain of Thought (SOP)
-
-1. **Analyze (Requirements):**
-   - Ask the user for their preferred stack (e.g., Next.js, Vite, NestJS).
-2. **Implement (Scaffolding):**
-   - Run the initialization command (e.g., `npx create-next-app@latest`).
-   - Overwrite `.eslintrc`, `prettierrc`, `tsconfig.json` with strict rules.
-   - Scaffold the architecture (e.g., create `src/features/`, `src/components/shared/`).
-3. **Verify (Validation):**
-   - Run `npm run dev` in a short background task to ensure it doesn't crash.
-
-## 🛡️ 2. Constraints & Rules
-
-- **Strict Mode:** Always enable `strict: true` in TypeScript configurations.
-- **Package Manager Check:** If the user uses `pnpm`, do NOT run `npm install`. Stick to one package manager.
-
-## 🤝 3. Handoff Pipeline
-
-1. `engineering-standard`: Verify the generated folder structure.
-2. `complete`: Output the Bootstrap Report.
-
-## 📝 4. Output Format
-
-Vui lòng trả kết quả bằng Tiếng Việt.
-
-- **Tóm tắt (Summary):** Dự án đã được khởi tạo với Stack nào.
-- **Chi tiết (Changes):** Cấu trúc thư mục mới và các file cấu hình.
-- **Xác thực (Verification):** Cách chạy dự án.
+# qk-project-bootstrap
+
+## Scope
+- Initializing new projects with best practices (Execute)
+
+## Constraints
+```yaml
+must:
+  - Setup linters, formatters, and standard directory structures
+  - Follow the organization's existing templates if available
+must_not:
+  - Hardcode outdated dependency versions
+  - Skip adding basic README instructions
+```
+
+## Policies
+```yaml
+prefer:
+  - Standard tooling over custom scripts
+```
+
+## Escalation
+```yaml
+ask:
+  - To clarify preferred framework/language if not specified
+```
+
+## Output
+- Bootstrapped repository structure
+```