ai-developer-skill-os 6.0.3 → 7.0.1

package/skills/qk-db-optimizer/SKILL.md

@@ -1,36 +1,41 @@
 ---
 name: qk-db-optimizer
-category: infrastructure
-version: 6.0.3
-description: "Tối ưu hóa Database (đánh Index, xử lý N+1 Queries, Slow Queries)."
+category: backend
+version: 7.0.0
+description: "Tối ưu hóa Database (đánh Index, xử lý N+1 Queries, Slow Queries) dựa trên bằng chứng."
 ---
 
 # qk-db-optimizer
 
 ## Scope
-- Database optimization (Indexes, N+1 Queries, Slow Queries) (Diagnose & Evaluate)
+- Database Optimization and Performance Auditing (Diagnose & Execute)
+
+## Verbs
+- `[OPTIMIZE]`: Analyze query plans and apply targeted indexes.
 
 ## Constraints
 ```yaml
 must:
-  - Analyze query execution plans if available
-  - Suggest non-breaking performance fixes
+  - "Analyze EXPLAIN or Query Plans BEFORE adding indexes"
+  - "Solve N+1 queries using Data Loaders or explicit Joins"
+  - "Validate query performance improvements"
 must_not:
-  - Change database engine or major architecture without consent
+  - "Guess missing indexes without slow query logs"
+  - "Add overlapping or redundant indexes"
 ```
 
 ## Policies
 ```yaml
 prefer:
-  - Adding indexes before rewriting complex queries
+  - "Compound indexes for multi-column queries"
+  - "Eager loading over lazy loading for known data relations"
 ```
 
 ## Escalation
 ```yaml
-ask:
-  - For exact slow query logs if not provided
+stop:
+  - "No evidence of slow queries or performance bottlenecks"
 ```
 
 ## Output
-- Optimization plan and SQL patches
-```
+- Optimized queries and index migration files.

package/skills/qk-design-to-code/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: qk-design-to-code
 category: frontend
-version: 6.0.3
+version: 7.0.0
 description: "Chuyển đổi thiết kế từ Figma/Images thành các UI component hoàn chỉnh, chuẩn pixel."
 ---
 
@@ -9,15 +9,22 @@ description: "Chuyển đổi thiết kế từ Figma/Images thành các UI comp
 
 ## Scope
 - Converting Figma/UI designs into pixel-perfect frontend code (Execute)
+- Rejecting generic templates and enforcing bespoke, high-quality aesthetics.
+
+## Verbs
+- `[REDESIGN]`: Discard generic UI structure, keep data, and rebuild with strict Hallmark/Open Design principles.
+- `[BUILD]`: Generate UI adhering 100% to `DESIGN.md`.
 
 ## Constraints
 ```yaml
 must:
-  - Use the project's existing design system / tokens
-  - Ensure responsive layouts
+  - Use the project's existing `DESIGN.md` design system / tokens ONLY
+  - Ensure responsive layouts and generous whitespace
+  - Include micro-interactions and smooth transitions
 must_not:
   - Hardcode magic numbers for spacing/colors
   - Invent new UI components if existing ones suffice
+  - Use generic "AI-slop" aesthetics (e.g., default Tailwind blue/red, cluttered layouts, 1px default borders)
 ```
 
 ## Policies
@@ -25,14 +32,15 @@ must_not:
 prefer:
   - Semantic HTML elements
   - CSS Grid / Flexbox over absolute positioning
+  - High-end aesthetics (glassmorphism, organic shadows, exact typography)
 ```
 
 ## Escalation
 ```yaml
 stop:
-  - Design assets or requirements are ambiguous
+  - "Design assets or requirements are ambiguous"
+  - "DESIGN.md is missing"
 ```
 
 ## Output
-- Frontend components and stylesheets
-```
+- Frontend components and stylesheets (Anti-Slop compliant)

package/skills/qk-docs/SKILL.md

@@ -1,37 +1,40 @@
 ---
 name: qk-docs
-category: utilities
-version: 6.0.3
-description: "Viết và duy trì tài liệu dự án để con người có thể dễ dàng đọc hiểu."
+category: documentation
+version: 7.0.0
+description: "Viết và duy trì tài liệu dự án chính xác tuyệt đối, cấm bịa đặt."
 ---
 
 # qk-docs
 
 ## Scope
-- Writing and maintaining project documentation for human readability (Execute)
+- Technical documentation, Readme files, and inline comments (Execute)
+
+## Verbs
+- `[DOCUMENT]`: Synchronize documentation with the actual implementation.
 
 ## Constraints
 ```yaml
 must:
-  - Keep documentation in sync with the actual codebase
-  - Use clear, accessible language
+  - "Ensure documentation matches the exact implementation in the codebase"
+  - "Update documentation whenever corresponding code is changed"
 must_not:
-  - Generate overly verbose or redundant docs
-  - Invent features that don't exist in the code
+  - "Hallucinate or guess API parameters not present in the code"
+  - "Write generic or useless comments (e.g., '// gets the user')"
 ```
 
 ## Policies
 ```yaml
 prefer:
-  - Examples and code snippets over pure text
+  - "Self-documenting code over excessive inline comments"
+  - "Living documentation (e.g., Swagger/JSDoc) over isolated Markdown files"
 ```
 
 ## Escalation
 ```yaml
 stop:
-  - The codebase logic is too ambiguous to document accurately
+  - "Documentation requests conflict with actual codebase implementation"
 ```
 
 ## Output
-- Markdown documentation files
-```
+- Accurate documentation files or inline comments.

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

@@ -1,39 +1,42 @@
 ---
 name: qk-engineering-standard
-category: conventions
-version: 6.0.3
-description: "Ép buộc áp dụng SOLID, DRY, Clean Code, và các quy tắc đặt tên."
+category: qa
+version: 7.0.0
+description: "Ép buộc áp dụng SOLID, DRY, Clean Code, và chống Spaghetti code."
 ---
 
 # qk-engineering-standard
 
 ## Scope
-- Readability and structural improvements (Evaluate)
+- Code Quality, Architecture, and Standards Enforcement (Audit)
+
+## Verbs
+- `[ENFORCE]`: Reject code that violates engineering standards.
 
 ## Constraints
 ```yaml
 must:
-  - Preserve business logic exactly
-  - Ensure tests pass after refactor
+  - "Enforce SOLID principles and DRY"
+  - "Keep cyclomatic complexity low (Functions must do ONE thing)"
+  - "Enforce strict naming conventions"
 must_not:
-  - Invent new requirements
-  - Change public API signature
+  - "Allow spaghetti code or mega-functions"
+  - "Merge logic that mixes UI, State, and Network in one file"
 ```
 
 ## Policies
 ```yaml
 prefer:
-  - Readability over cleverness
-  - Explain trade-offs
+  - "Composition over inheritance"
+  - "Early returns and guard clauses"
 ```
 
 ## Escalation
 ```yaml
 stop:
-  - Tests fail
+  - "Cyclomatic complexity exceeds acceptable thresholds"
+  - "Code violates V7 Anti-Slop architectural rules"
 ```
 
 ## Output
-- Evaluation summary
-- Refactored code
-```
+- Refactored code or Audit rejection report.

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

@@ -1,40 +1,48 @@
 ---
 name: qk-feature-delivery
 category: fullstack
-version: 6.0.3
-description: "Phát triển tính năng mới hoàn chỉnh từ Frontend đến Backend."
+version: 7.0.0
+description: "Phát triển tính năng mới tuân thủ biểu đồ bối cảnh và Khế ước Thiết kế (DESIGN.md)."
 ---
 
 # qk-feature-delivery
 
 ## Scope
-- New capabilities (Execute)
+- New capabilities (Plan & Execute)
+- Fullstack delivery conforming to V7 Anti-Slop and Graphing requirements.
+
+## Verbs
+- `[DELIVER]`: Orchestrate the creation of a feature end-to-end.
 
 ## Constraints
 ```yaml
 must:
-  - Clarify requirements if unclear
-  - Implement complete end-to-end flow
+  - "For logic: MUST demand a Structural Map (Dependency Graph) from qk-context-loader before coding"
+  - "For UI: MUST strictly adhere to DESIGN.md and Anti-Slop aesthetics"
+  - "Clarify requirements if ambiguous"
+  - "Implement complete end-to-end flow"
 must_not:
-  - Mix refactoring into feature work
-  - Ignore backward compatibility
+  - "Mix refactoring into feature work"
+  - "Ignore backward compatibility"
+  - "Emit generic 'AI-slop' UI or unverified logic"
 ```
 
 ## Policies
 ```yaml
 prefer:
-  - Plan before implementing
-  - Cover UI loading/error states
+  - "Plan before implementing"
+  - "Cover UI loading/error states"
+  - "Self-audit against DESIGN.md and Context Graph"
 ```
 
 ## Escalation
 ```yaml
 stop:
-  - Requirements are ambiguous
+  - "Requirements are ambiguous"
+  - "DESIGN.md or Context Graph is missing/unavailable"
 ask:
-  - Before adding heavy dependencies
+  - "Before adding heavy dependencies"
 ```
 
 ## Output
-- Feature implementation
-```
+- Feature implementation conforming to V7 quality standards.

package/skills/qk-help/SKILL.md

@@ -1,35 +1,38 @@
 ---
 name: qk-help
-category: core
-version: 6.0.3
-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
+version: 7.0.0
+description: "Hiển thị danh sách các kỹ năng V7 hiện có và các lệnh khắt khe."
 ---
 
 # qk-help
 
 ## Scope
-- Displaying available skills and usage tips (Collect & Delegate)
+- Skill discovery and usage assistance (Collect)
+
+## Verbs
+- `[HELP]`: Display strict V7 guidelines and available skills.
 
 ## Constraints
 ```yaml
 must:
-  - Present information clearly and concisely
+  - "List all available V7 skills and their core 'must' constraints"
+  - "Emphasize the Zero-Trust and Anti-Slop philosophy"
 must_not:
-  - Hallucinate skills that do not exist in the repository
+  - "Display outdated V6 instructions or deprecated skills"
 ```
 
 ## Policies
 ```yaml
 prefer:
-  - Short, actionable examples over long descriptions
+  - "Clear, formatted Markdown output"
 ```
 
 ## Escalation
 ```yaml
 ask:
-  - If the user's intent is unclear when asking for help
+  - "If the user is looking for a skill that does not exist"
 ```
 
 ## Output
-- List of available skills and usage instructions
-```
+- List of skills and V7 usage guidelines.

package/skills/qk-orchestrator/SKILL.md

@@ -1,36 +1,42 @@
 ---
 name: qk-orchestrator
 category: core
-version: 6.0.3
-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."
+version: 7.0.0
+description: "Điều hướng yêu cầu của người dùng với kỷ luật thép, kiểm tra DESIGN.md và Context Graph."
 ---
 
 # qk-orchestrator
 
 ## Scope
-- Request analysis and task delegation (Coordinate)
+- Request analysis, task delegation, and strict process enforcement (Coordinate)
+
+## Verbs
+- `[ROUTE]`: Dispatch tasks strictly to specialist skills based on V7 architecture constraints.
 
 ## Constraints
 ```yaml
 must:
-  - Route user request to the correct sub-skill
+  - Route user request to the correct sub-skill.
+  - For UI tasks: MUST ensure `DESIGN.md` exists (or delegate to `qk-project-bootstrap`).
+  - For Logic tasks: MUST ensure `qk-context-loader` generates a map first.
 must_not:
   - Write code directly
   - Hallucinate non-existent skills
+  - Allow UI work without a Design Contract
 ```
 
 ## Policies
 ```yaml
 prefer:
-  - Delegate to specialist skills
+  - Strict sequencing (Context Map -> Audit -> Code -> Verify) over chaotic parallel generation.
 ```
 
 ## Escalation
 ```yaml
 stop:
   - No matching skill is found
+  - The task violates the Zero-Trust or Anti-Slop philosophy of V7.
 ```
 
 ## Output
-- Delegation plan
-```
+- Delegation plan with hard prerequisites checked.

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

@@ -1,36 +1,39 @@
 ---
 name: qk-policy-engine
 category: security
-version: 6.0.3
+version: 7.0.0
 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."
 ---
 
 # qk-policy-engine
 
 ## Scope
-- System policy evaluation for safe and authorized actions (Govern)
+- Security policies, authorization rules, and compliance (Evaluate)
+
+## Verbs
+- `[AUTHORIZE]`: Evaluate requests against the strict policy matrix.
 
 ## Constraints
 ```yaml
 must:
-  - Evaluate requested actions against defined system constraints
-  - Enforce OS-level invariants
+  - "Enforce Principle of Least Privilege (PoLP) on all operations"
+  - "Log all authorization failures for audit purposes"
 must_not:
-  - Allow destructive commands (e.g. rm -rf /) to bypass checks
+  - "Bypass security checks for 'admin' or 'dev' accounts in production"
+  - "Hardcode plain-text secrets in policy rules"
 ```
 
 ## Policies
 ```yaml
 prefer:
-  - Strict adherence to policy over convenience
+  - "Explicit Deny by default"
 ```
 
 ## Escalation
 ```yaml
 stop:
-  - Action explicitly violates core safety policies
+  - "Policy evaluation fails (Unauthorized Action)"
 ```
 
 ## Output
-- Policy evaluation result (Allow/Deny)
-```
+- Policy evaluation result (Allow/Deny) and audit trail.

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

@@ -1,36 +1,41 @@
 ---
 name: qk-production-release
 category: devops
-version: 6.0.3
-description: "Chuẩn bị codebase để phát hành lên production (Build, CI/CD, Security)."
+version: 7.0.0
+description: "Chuẩn bị codebase phát hành Production với các cổng kiểm duyệt an ninh tuyệt đối."
 ---
 
 # qk-production-release
 
 ## Scope
-- Preparing codebase for production release including Build, CI/CD, and Security checks (Plan & Govern)
+- Production builds, CI/CD pipelines, and Security gating (Execute)
+
+## Verbs
+- `[RELEASE]`: Prepare and sign off on a production-ready artifact.
 
 ## Constraints
 ```yaml
 must:
-  - Verify that all tests pass and linters are clean
-  - Check for exposed secrets or misconfigurations
+  - "Run full suite of linters, tests, and security scans (Validation Gate) before release"
+  - "Minify and strip out all debug/console logs"
 must_not:
-  - Deploy code that fails security audits
+  - "Release if ANY high-priority bug is unresolved"
+  - "Deploy with dev-environment secrets or configurations"
 ```
 
 ## Policies
 ```yaml
 prefer:
-  - Immutable artifacts and deterministic builds
+  - "Automated CI/CD validation over manual checks"
+  - "Immutable build artifacts"
 ```
 
 ## Escalation
 ```yaml
 stop:
-  - Security vulnerabilities or critical test failures are detected
+  - "Tests fail during the release build"
+  - "Environment variables for production are missing"
 ```
 
 ## Output
-- Release checklist and deployment readiness status
-```
+- Production-ready build artifacts and deployment scripts.

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

@@ -1,7 +1,7 @@
 ---
 name: qk-project-bootstrap
 category: fullstack
-version: 6.0.3
+version: 7.0.0
 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."
 ---
 
@@ -15,6 +15,7 @@ description: "Khởi tạo dự án mới với các best practices, linters, v
 must:
   - Setup linters, formatters, and standard directory structures
   - Follow the organization's existing templates if available
+  - ALWAYS generate a `DESIGN.md` file in the project root to serve as the Brand Contract (Open Design standard). MUST prompt the user for design constraints if none are provided.
 must_not:
   - Hardcode outdated dependency versions
   - Skip adding basic README instructions

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

@@ -1,37 +1,40 @@
 ---
 name: qk-project-health
-category: maintenance
-version: 6.0.3
-description: "Kiểm toán toàn diện về Code Smells, Tech Debt, và Architecture."
+category: qa
+version: 7.0.0
+description: "Kiểm toán toàn diện Code Smells, Tech Debt, và Architecture."
 ---
 
 # qk-project-health
 
 ## Scope
-- Comprehensive auditing of Code Smells, Tech Debt, and Architecture (Diagnose & Evaluate)
+- Technical Debt Auditing and System Health Monitoring (Evaluate)
+
+## Verbs
+- `[AUDIT]`: Evaluate the entire project's health.
 
 ## Constraints
 ```yaml
 must:
-  - Analyze dependency graphs and code complexity metrics
-  - Highlight architectural anti-patterns
+  - "Identify deprecated packages and security vulnerabilities"
+  - "Map out technical debt explicitly"
 must_not:
-  - Rewrite major components without user consent
-  - Focus purely on stylistic lints (leave that to linter)
+  - "Ignore compiler or strict-mode warnings"
+  - "Hide systemic architectural flaws"
 ```
 
 ## Policies
 ```yaml
 prefer:
-  - Structural and performance improvements over minor refactors
+  - "Automated static analysis tools"
+  - "Actionable refactoring roadmaps"
 ```
 
 ## Escalation
 ```yaml
 stop:
-  - The project lacks basic structure making analysis impossible
+  - "Critical security vulnerabilities detected (CVSS High/Critical)"
 ```
 
 ## Output
-- Health report and refactoring plan
-```
+- Health report and Tech Debt mitigation plan.

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

@@ -1,36 +1,40 @@
 ---
 name: qk-project-memory
 category: core
-version: 6.0.3
-description: "Lưu trữ và truy xuất ngữ cảnh dự án dài hạn qua các phiên làm việc."
+version: 7.0.0
+description: "Lưu trữ và truy xuất ngữ cảnh dự án dài hạn qua các phiên làm việc với độ chính xác cao."
 ---
 
 # qk-project-memory
 
 ## Scope
-- Storing and retrieving long-term project context across sessions (Collect)
+- Long-term context storage and retrieval (Plan & Collect)
+
+## Verbs
+- `[MEMORIZE]`: Store verified facts about the project.
+- `[RECALL]`: Retrieve facts strictly based on recorded memory.
 
 ## Constraints
 ```yaml
 must:
-  - Organize context logically so it can be retrieved efficiently
-  - Update memory artifacts when major architectural decisions are made
+  - "Verify facts against the actual codebase before storing them"
+  - "Timestamp and categorize memory entries"
 must_not:
-  - Store sensitive user data or secrets in project memory
+  - "Store assumptions or unverified AI hypotheses"
+  - "Overwrite fundamental architectural rules without explicit user consent"
 ```
 
 ## Policies
 ```yaml
 prefer:
-  - Concise summaries over verbose logs for long-term memory
+  - "Structured data formats (JSON/Markdown) for memory storage"
 ```
 
 ## Escalation
 ```yaml
-ask:
-  - To clarify contradictory information found in the project memory
+stop:
+  - "Memory conflicts with the core AGENTS.md rules"
 ```
 
 ## Output
-- Updated memory artifacts
-```
+- Context retrieval results or stored memory artifacts.

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

@@ -1,36 +1,40 @@
 ---
 name: qk-system-evolution
-category: infrastructure
-version: 6.0.3
-description: "Cập nhật an toàn các thư viện dependencies, di chuyển frameworks và quản lý quá trình rollback."
+category: maintenance
+version: 7.0.0
+description: "Cập nhật an toàn các thư viện, di chuyển frameworks với kế hoạch rollback nghiêm ngặt."
 ---
 
 # qk-system-evolution
 
 ## Scope
-- Safely updating dependencies, migrating frameworks, and managing rollbacks (Plan & Execute)
+- Dependency upgrades, Framework migrations, and rollback management (Execute)
+
+## Verbs
+- `[UPGRADE]`: Migrate systems with zero-trust testing.
 
 ## Constraints
 ```yaml
 must:
-  - Check compatibility matrices before upgrading dependencies
-  - Provide a rollback plan for major framework updates
+  - "MUST have a Rollback Plan before executing any major upgrade"
+  - "Verify all dependencies against the Context Graph to catch breaking changes"
 must_not:
-  - Perform destructive migrations without a backup strategy
+  - "Upgrade major versions without reading the Changelog/Migration Guide"
+  - "Blindly run 'npm update' or equivalent"
 ```
 
 ## Policies
 ```yaml
 prefer:
-  - Incremental updates over 'big bang' migrations
+  - "Incremental upgrades over 'big bang' migrations"
 ```
 
 ## Escalation
 ```yaml
 stop:
-  - Critical dependencies are completely incompatible with the target framework version
+  - "Dependency upgrades break existing test suites"
+  - "No Rollback Plan provided"
 ```
 
 ## Output
-- Migration scripts, updated package files, and rollback plans
-```
+- Upgraded dependencies and migration logs.