ai-developer-skill-os 7.0.1 → 7.5.0

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

@@ -1,42 +1,351 @@
----
-name: qk-engineering-standard
-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
-- Code Quality, Architecture, and Standards Enforcement (Audit)
-
-## Verbs
-- `[ENFORCE]`: Reject code that violates engineering standards.
-
-## Constraints
-```yaml
-must:
-  - "Enforce SOLID principles and DRY"
-  - "Keep cyclomatic complexity low (Functions must do ONE thing)"
-  - "Enforce strict naming conventions"
-must_not:
-  - "Allow spaghetti code or mega-functions"
-  - "Merge logic that mixes UI, State, and Network in one file"
-```
-
-## Policies
-```yaml
-prefer:
-  - "Composition over inheritance"
-  - "Early returns and guard clauses"
-```
-
-## Escalation
-```yaml
-stop:
-  - "Cyclomatic complexity exceeds acceptable thresholds"
-  - "Code violates V7 Anti-Slop architectural rules"
-```
-
-## Output
-- Refactored code or Audit rejection report.
+---
+name: qk-engineering-standard
+category: qa
+version: 7.5.0
+description: "Ép buộc SOLID, DRY, Clean Code với ngưỡng số liệu cụ thể — không có rule mơ hồ."
+platforms: [antigravity, claude-code, cursor, windsurf, kilo-code]
+execution_mode: deterministic
+
+cost: medium
+latency: medium
+risk: low
+side_effects: read_only
+produces: [report]
+consumes: [source-code]
+
+token_budget:
+  max_files_read: 5
+  max_lines_per_read: 150
+  max_shell_commands: 1
+  stop_early: true
+
+exit_codes: [SUCCESS, BLOCKED, FAILED, PARTIAL]
+skill_version: 7.5.0
+runtime_version: 1
+schema_version: 2
+---
+
+# qk-engineering-standard — Code Quality Enforcer
+
+> **Language rule:** Code, identifiers, file names ? English. Explanations, summaries ? Vietnamese.
+
+skill_version: 7.5.0
+runtime_version: 1
+schema_version: 2
+---
+
+## Preconditions
+- [ ] Target file(s) or module(s) are specified
+
+```
+On missing precondition:
+  EXIT: BLOCKED
+  Message: "Vui lòng chỉ định file hoặc module cần kiểm tra."
+```
+
+skill_version: 7.5.0
+runtime_version: 1
+schema_version: 2
+---
+
+## Scope
+- ✅ Detect violations with exact file:line references
+- ✅ Classify by severity with concrete thresholds
+- ✅ Suggest minimal, targeted refactors
+
+## Non-Goals
+- ❌ Auto-fix code — report only (fixes go to qk-bug-resolution or qk-feature-delivery)
+- ❌ Rewrite architecture
+- ❌ Touch files outside the specified scope
+
+skill_version: 7.5.0
+runtime_version: 1
+schema_version: 2
+---
+
+## Concrete Thresholds (Non-Negotiable)
+
+```yaml
+function:
+  max_lines: 30              # Lines of code, excluding comments/blanks
+  max_cyclomatic_complexity: 10
+  max_parameters: 4
+
+file:
+  max_lines: 300
+  max_public_methods_per_class: 10  # God Class threshold
+
+dry:
+  violation_threshold: 3    # Same logic duplicated in ≥ 3 places
+
+separation_of_concerns:
+  violation: "File mixes UI rendering + API calls + State management"
+
+naming:
+  min_variable_name_length: 2  # Single-letter vars (except i,j,k in loops)
+  max_abbreviation_ratio: 0.3  # > 30% abbreviations in identifiers = violation
+
+dependency:
+  max_imports_per_file: 15  # Beyond this: likely a God File
+```
+
+skill_version: 7.5.0
+runtime_version: 1
+schema_version: 2
+---
+
+## Priority Order
+
+| Priority | Check | Severity | Skip Threshold |
+|----------|-------|----------|----------------|
+| P1 | Security violations (hardcoded secrets, SQL injection) | CRITICAL | Never |
+| P2 | God Functions > 30 lines / complexity > 10 | HIGH | Budget < 30% |
+| P3 | God Files > 300 lines / God Classes | HIGH | Budget < 40% |
+| P4 | DRY violations (3+ duplicates) | MEDIUM | Budget < 50% |
+| P5 | Mixed concerns in single file | MEDIUM | Budget < 60% |
+| P6 | Naming convention violations | LOW | Budget < 70% |
+| P7 | Excessive imports / coupling | LOW | Budget < 80% |
+
+skill_version: 7.5.0
+runtime_version: 1
+schema_version: 2
+---
+
+## Workflow
+
+### Phase 1 — Scan for Critical & High Violations
+
+**Steps:**
+1. `grep_search` — search for: hardcoded secrets, `console.log`, `eval(`, `any` types
+2. `view_file[targeted]` — read function definitions to count lines and parameters
+3. Log each violation with Evidence Format
+
+**Decision:**
+```
+IF CRITICAL violation found (e.g., hardcoded API key)
+  → Report immediately, mark EXIT: FAILED
+  → Still continue scanning (don't stop at first critical)
+
+IF function line count > 30 OR complexity > 10
+  → Log as [HIGH]
+
+IF file line count > 300
+  → Log as [HIGH] — God File suspected
+```
+
+**Exit When:**
+- All P1+P2+P3 checks done → go to Phase 2
+- Token budget < 30% → go to Phase 3 directly with PARTIAL flag
+
+skill_version: 7.5.0
+runtime_version: 1
+schema_version: 2
+---
+
+### Phase 2 — Scan for Medium & Low Violations
+
+**Steps:**
+1. `grep_search` — find duplicate logic patterns (copy-paste code)
+2. Check import counts per file
+3. Check naming conventions
+
+**Decision:**
+```
+IF same logic block appears ≥ 3 times
+  → Log as [MEDIUM] DRY violation
+
+IF file has > 15 imports
+  → Log as [LOW] — potential God File or tight coupling
+
+IF token budget < 50%
+  → Skip P6+P7, go to Phase 3
+```
+
+skill_version: 7.5.0
+runtime_version: 1
+schema_version: 2
+---
+
+### Phase 3 — Score & Report
+
+**Steps:**
+1. Count violations by severity
+2. Calculate health score: start at 100, deduct per violation
+3. Generate report
+
+**Deduction Scale:**
+```
+CRITICAL: -25 pts each
+HIGH:     -10 pts each
+MEDIUM:   -5 pts each
+LOW:      -2 pts each
+```
+
+**Decision:**
+```
+IF score ≥ 80 AND no CRITICAL violations
+  → EXIT: SUCCESS
+
+IF score 60–79 OR any HIGH violations
+  → EXIT: PARTIAL — list fixes needed
+
+IF score < 60 OR any CRITICAL violations
+  → EXIT: FAILED — requires immediate action
+```
+
+skill_version: 7.5.0
+runtime_version: 1
+schema_version: 2
+---
+
+## Confidence Model
+
+| Level | Condition | Action |
+|-------|-----------|--------|
+| HIGH | Direct line count, exact pattern match | Report as violation |
+| MEDIUM | Inferred cyclomatic complexity without tool | Note estimate |
+| LOW | Architectural smell inferred from structure | Mark as "suspected — verify manually" |
+
+skill_version: 7.5.0
+runtime_version: 1
+schema_version: 2
+---
+
+## Severity
+
+| Level | Definition | Example |
+|-------|-----------|---------|
+| CRITICAL | Security risk or data integrity | Hardcoded secret, SQL injection via string concat |
+| HIGH | Technical debt that blocks scaling | Function 80 lines, God Class 15+ methods |
+| MEDIUM | DRY or SoC violation, fixable in < 1 hour | Same validation logic in 3 components |
+| LOW | Style/naming issue, non-blocking | Single-letter variable `x` outside loop |
+
+skill_version: 7.5.0
+runtime_version: 1
+schema_version: 2
+---
+
+## Evidence Format
+
+```
+[SEVERITY] path/to/file.ts:LINE
+Rule:       [FUNCTION_LENGTH | COMPLEXITY | DRY | SOC | NAMING | GOD_CLASS | SECRET]
+Reason:     [specific measurement vs threshold]
+Confidence: [HIGH|MEDIUM|LOW]
+Fix:        [one-line suggestion]
+Deduction:  -N pts
+```
+
+**Example:**
+```
+[HIGH] src/services/order.service.ts:45
+Rule:       FUNCTION_LENGTH
+Reason:     Function `processOrder` is 87 lines (threshold: 30)
+Confidence: HIGH
+Fix:        Extract payment logic to `processPayment()`, shipping to `scheduleShipment()`
+Deduction:  -10 pts
+```
+
+skill_version: 7.5.0
+runtime_version: 1
+schema_version: 2
+---
+
+## Retry Policy
+```
+Audit is read-only — no retry needed.
+If file is inaccessible → skip and note in report as PARTIAL.
+```
+
+skill_version: 7.5.0
+runtime_version: 1
+schema_version: 2
+---
+
+## Escalation Rules
+
+```
+BLOCKED: No target specified
+Missing:
+  - File path or module name to audit
+Questions:
+  1. Bạn muốn kiểm tra file nào hoặc toàn bộ module nào?
+  2. Có ngưỡng cụ thể nào bạn muốn thay đổi không? (mặc định: 30 lines/function)
+```
+
+skill_version: 7.5.0
+runtime_version: 1
+schema_version: 2
+---
+
+## Handoff Contract
+
+### Consumes
+```json
+{
+  "from": "user or qk-orchestrator",
+  "required_fields": ["target_files_or_module"],
+  "optional_fields": ["custom_thresholds"]
+}
+```
+
+### Produces
+```json
+{
+  "to": "user",
+  "output_fields": ["health_score", "violations_list", "severity_counts", "exit_code"]
+}
+```
+
+skill_version: 7.5.0
+runtime_version: 1
+schema_version: 2
+---
+
+## Output Format
+
+```
+⚙️ Engineering Standard Audit
+─────────────────────────────────────────────────
+Target:      [file or module]
+
+Health Score: [X/100]
+  CRITICAL violations: [N] (-Npts)
+  HIGH violations:     [N] (-Npts)
+  MEDIUM violations:   [N] (-Npts)
+  LOW violations:      [N] (-Npts)
+
+Violations (priority order):
+  [SEVERITY] file:LINE — Rule — reason — Fix — (-Xpts)
+
+Required Actions:
+  1. [Most critical fix]
+  2. [Second fix]
+
+Exit Code:   [SUCCESS | PARTIAL | FAILED]
+```
+
+skill_version: 7.5.0
+runtime_version: 1
+schema_version: 2
+---
+
+## Exit Codes
+
+| Code | Meaning | When |
+|------|---------|------|
+| SUCCESS | Score ≥ 80, no CRITICAL | Code meets V7.5 standards |
+| PARTIAL | Score 60–79 or incomplete scan | Some categories skipped |
+| BLOCKED | No target specified | Cannot audit without scope |
+| FAILED | Score < 60 or CRITICAL found | Immediate action required |
+
+skill_version: 7.5.0
+runtime_version: 1
+schema_version: 2
+---
+
+## References
+- Detailed thresholds with rationale: `references/thresholds.md`
+
+---
+

package/skills/qk-fe-api-integration/SKILL.md

@@ -0,0 +1,326 @@
+---
+name: qk-fe-api-integration
+category: frontend
+version: 7.5.0
+description: "Consume API Backend, quản lý State, bind vào UI — tuân thủ kiến trúc Base dự án"
+platforms: [antigravity, claude-code, cursor, windsurf, kilo-code]
+execution_mode: deterministic
+
+cost: medium
+latency: medium
+risk: low
+side_effects: edit_files
+produces: [code]
+consumes: [json-payload, context-graph]
+
+token_budget:
+  max_files_read: 3
+  max_lines_per_read: 100
+  max_shell_commands: 1
+  stop_early: true
+
+exit_codes: [SUCCESS, BLOCKED, FAILED, PARTIAL]
+skill_version: 7.5.0
+runtime_version: 1
+schema_version: 2
+---
+
+# qk-fe-api-integration — Frontend API Consumer
+
+> **Language rule:** Code, identifiers, file names → English. Explanations, summaries → Vietnamese.
+
+---
+
+## Preconditions
+- [ ] Backend JSON payload hoặc API endpoint schema được cung cấp
+- [ ] Project's API client pattern được xác định (Axios wrapper, RTK Query, React Query, etc.)
+
+```
+On missing precondition:
+  EXIT: BLOCKED
+  Message: "Cần cung cấp: JSON response mẫu VÀ xác nhận API client pattern hiện tại của dự án."
+```
+
+---
+
+## Scope
+- ✅ Identify existing API client pattern (NEVER default to raw fetch if wrapper exists)
+- ✅ Generate strict TypeScript interfaces from JSON payload
+- ✅ Implement service layer (API calls separated from UI)
+- ✅ Handle all 3 UI states: Loading, Success, Error
+- ✅ Map backend payload → DTO before injecting into UI components
+
+## Non-Goals
+- ❌ Hardcode API Base URLs in UI components — use env vars or centralized config
+- ❌ Inject API logic inside presentational (dumb) components
+- ❌ Introduce new state management libraries without explicit user approval
+- ❌ Hallucinate data fields not in provided JSON payload
+- ❌ Create Node.js/Python scripts to patch — edit files directly
+- ❌ Read entire files > 100 lines — use targeted reads
+- ❌ Default to raw fetch if wrapper exists — ALWAYS reuse existing client
+
+---
+
+## Priority Order
+
+| Priority | Task | Skip Threshold |
+|----------|------|----------------|
+| P1 | Identify existing API client (grep package.json, src/api/) | Never |
+| P2 | Generate TypeScript interfaces from JSON payload | Never |
+| P3 | Implement service layer (API calls) | Never |
+| P4 | Bind to UI with Loading + Success + Error states | Budget < 30% |
+| P5 | Cache invalidation after mutations (POST/PUT/DELETE) | Budget < 60% |
+| P6 | DTO mapping (backend payload → clean UI data) | Budget < 70% |
+
+---
+
+## Workflow
+
+### Phase 1 — Identify Base Architecture
+
+**Steps:**
+1. `grep_search` in `package.json` → identify: axios, react-query, rtk-query, swr, or custom
+2. `view_file[src/api/]` (first 30 lines) → confirm wrapper pattern
+3. Identify: base URL config, auth header injection, error interceptor location
+
+**Decision:**
+```
+IF wrapper/client found (e.g., apiClient.ts, axiosInstance.ts)
+  → Use it. NEVER bypass with raw fetch/axios.
+  → Confidence: HIGH → go to Phase 2
+
+ELSE IF no wrapper found
+  → Confirm with user: "Dùng raw fetch hay tạo wrapper mới?"
+  → Confidence: MEDIUM → go to Phase 2
+
+ELSE IF conflicting patterns found (mix of fetch + axios + rtk)
+  → EXIT: BLOCKED — ask which pattern to follow
+```
+
+**Exit When:**
+- API client pattern identified → go to Phase 2
+- `max_files_read` reached → go to Phase 2 with MEDIUM confidence
+
+---
+
+### Phase 2 — Generate Types
+
+**Steps:**
+1. Parse provided JSON payload → extract all fields with types
+2. Generate TypeScript interface (Request + Response)
+3. Flag any field that could be `null` or optional
+
+**Decision:**
+```
+IF all fields clearly typed from JSON
+  → Confidence: HIGH → go to Phase 3
+
+ELSE IF some fields ambiguous (null | undefined)
+  → Mark as optional (?:) + add comment "// verify with backend"
+  → Confidence: MEDIUM → go to Phase 3
+
+ELSE IF nested objects contain mixed null/non-null patterns
+  → EXIT: BLOCKED — cannot safely generate types without backend clarification
+```
+
+---
+
+### Phase 3 — Implement Service + UI Binding
+
+**Steps:**
+1. Create/update service file (API calls only — no UI logic)
+2. Bind to component: implement Loading state (skeleton/spinner)
+3. Bind Success state: render data using generated types
+4. Bind Error state: handle HTTP errors per table below
+
+**HTTP Error Handling (mandatory for ALL integrations):**
+```
+401 Unauthorized → redirect to login or show auth error toast
+403 Forbidden    → show permission error toast
+404 Not Found    → show empty state component (not a crash)
+422 Validation   → map field errors to form fields
+500 Server Error → show generic error toast + retry button
+Network Error    → show offline banner or retry prompt
+```
+
+**Decision:**
+```
+IF all 3 states (Loading, Success, Error) implemented + service created → go to Phase 4
+ELSE IF error state incomplete → EXIT: PARTIAL — missing HTTP error handling
+ELSE → EXIT: BLOCKED — cannot complete binding
+```
+
+**Exit When:**
+- All 3 states implemented + service created → go to Phase 4
+
+---
+
+### Phase 4 — Self-Audit
+
+**Steps:**
+1. Re-read service file: confirm no hardcoded URLs, no UI logic
+2. Re-read component: confirm no API calls inside JSX
+3. Verify cache invalidation if mutation (POST/PUT/DELETE)
+
+**Decision:**
+```
+IF all audit points pass → EXIT: SUCCESS
+ELSE IF 1–2 minor issues → fix inline → EXIT: SUCCESS
+ELSE IF architectural violation found → fix → EXIT: PARTIAL
+ELSE IF hardcoded URL (http://localhost, 127.0.0.1) found → EXIT: FAILED — do not ship
+```
+
+---
+
+## Confidence Model
+
+| Level | Condition | Action |
+|-------|-----------|--------|
+| HIGH | API client found, JSON payload complete, all types inferred | Implement directly |
+| MEDIUM | Some fields ambiguous, wrapper partially identified | Note assumptions, proceed |
+| LOW | No JSON payload provided OR conflicting API patterns OR nested nulls unresolved | EXIT: BLOCKED |
+
+---
+
+## Severity
+
+| Level | Definition | Example |
+|-------|-----------|---------|
+| CRITICAL | Security data leakage from improper DTO mapping | Auth token in dumb component |
+| HIGH | Missing error state causes white screen of death | No 500 handler |
+| MEDIUM | Hardcoded URL breaks in production | `axios.get("http://localhost:3000/api")` |
+| LOW | Missing cache invalidation after mutation | Stale data after POST |
+
+---
+
+## Evidence Format
+
+```
+[SEVERITY] path/to/component.tsx:LINE
+Issue:      [specific violation]
+Confidence: [HIGH|MEDIUM|LOW]
+Fix:        [one-line suggestion]
+```
+
+**Example:**
+```
+[HIGH] src/pages/Dashboard.tsx:45
+Issue:      API call `axios.get('/api/data')` inside JSX render — violates smart/dumb separation
+Confidence: HIGH
+Fix:        Move to `src/services/dashboard.service.ts`, inject via hook
+```
+
+---
+
+## Retry Policy
+
+```
+API call fails (runtime verification)
+  └─ Check error type
+       ├─ Network error → show retry button (user-triggered retry, not auto)
+       ├─ 401/403 → do NOT retry — redirect or show permission error
+       ├─ 500 → auto-retry once after 1s delay
+       │        └─ Still fails → show error toast with "Try again" button
+       └─ Never auto-retry more than 1 time (avoid hammering server)
+
+Skill execution fails
+  └─ Check failure type
+       ├─ Syntax error in generated code → fix and retry once
+       └─ Architectural mismatch → EXIT: FAILED, do NOT retry
+```
+
+---
+
+## Escalation Rules
+
+```
+BLOCKED: Cannot determine API client pattern
+Missing:
+  - package.json contents OR
+  - Location of existing API client file (e.g., src/lib/api.ts)
+Questions:
+  1. Dự án dùng thư viện nào để gọi API? (axios / fetch / react-query / rtk-query)
+  2. Có file API wrapper/client nào sẵn không? (ví dụ: src/api/client.ts)
+Recommended Assumptions (if proceeding):
+  - Create new Axios instance with interceptors for auth + error handling
+```
+
+---
+
+## Handoff Contract
+
+### Consumes
+```json
+{
+  "from": "user or qk-context-loader",
+  "required_fields": ["json_payload_sample", "api_endpoint"],
+  "optional_fields": ["existing_api_client_path", "component_to_bind"]
+}
+```
+
+### Produces
+```json
+{
+  "to": "user",
+  "output_fields": ["types_file", "service_file", "component_file", "states_implemented", "exit_code"]
+}
+```
+
+---
+
+## Output Format
+
+```
+🔌 FE API Integration
+─────────────────────────────────────────────────
+API Client:  [identified — axiosInstance.ts | created new]
+Types:       [src/types/[resource].types.ts]
+Service:     [src/services/[resource].service.ts]
+
+States implemented:
+  ✅ Loading (skeleton/spinner)
+  ✅ Success (data rendered)
+  ✅ Error (toast/empty state per HTTP code)
+  ⚠️ [any state skipped — reason]
+
+Assumptions:
+  - [any assumption made]
+
+Exit Code:   [SUCCESS | PARTIAL | BLOCKED | FAILED]
+```
+
+---
+
+## Exit Codes
+
+| Code | Meaning | When |
+|------|---------|------|
+| SUCCESS | Types + service + UI binding complete with all 3 states | Full integration |
+| PARTIAL | Integration done, missing error/loading state or cache invalidation | Follow-up needed |
+| BLOCKED | No JSON payload or conflicting API patterns | Ask user |
+| FAILED | Cannot integrate without breaking existing architecture | Escalate |
+
+---
+
+Consume backend API safely in frontend: identify existing client, generate types, implement service layer, and bind to UI with proper states.
+Triggered when user needs to integrate a backend API endpoint into a frontend application. Requires JSON payload sample and knowledge of existing API client patterns.
+- JSON payload sample (request/response)
+- API endpoint specification
+- Existing API client path (if any)
+- Component to bind (if specified)
+- Context graph (for existing patterns)
+1. **Identify:** Find existing API client or confirm need for new one
+2. **Generate:** Create TypeScript interfaces from JSON payload
+3. **Implement:** Build service layer with proper HTTP methods
+4. **Bind:** Connect to UI with Loading/Success/Error states
+5. **Audit:** Verify no hardcoded URLs, no API in JSX, proper error handling
+- NEVER bypass existing wrapper with raw fetch/axios
+- MUST generate strict TypeScript interfaces (no `any`)
+- MUST handle all 3 UI states: Loading, Success, Error
+- MUST NOT exceed token_budget (max 3 files, 100 lines each, 1 shell command)
+- MUST stop early if confidence threshold reached
+- Zero-Trust: Use existing client pattern, never invent new one without approval
+- Type Safety: All API responses must have explicit TypeScript types
+- Error Handling: All HTTP errors must be handled per mandatory table
+- Separation: Service layer only — no API calls in presentational components
+---