ai-developer-skill-os 1.5.3 → 1.6.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ai-developer-skill-os",
-  "version": "1.5.3",
+  "version": "1.6.0",
   "description": "Multi-agent skill package cho AI coding agents (Claude, Cursor, Windsurf, Antigravity) với 23 skills chuyên nghiệp.",
   "main": "bin/install.js",
   "bin": {

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

@@ -37,239 +37,6 @@ Activate this skill when the user provides any of:
 - ✅ Generate typed service/client, hooks/queries, and TypeScript types
 - ✅ Follow and extend existing architecture — never duplicate it
 - ✅ Handle special cases: file upload, file download, pagination, auth, WebSocket
-
----
-
-## Non-goals
-
-- ❌ Do NOT create a new HTTP client if one already exists
-- ❌ Do NOT introduce a new state system if one is already in use
-- ❌ Do NOT write UI logic inside the API layer
-- ❌ Do NOT hardcode URLs, tokens, or secrets
-- ❌ Do NOT use `any` when types can be inferred
-- ❌ Do NOT overwrite existing files without explicit user approval
-
----
-
-## Severity Levels
-
-| Level | Meaning |
-|-------|---------|
-| P0 | Conflict with existing endpoint or type — must resolve before generating |
-| P1 | Missing critical info (auth, response schema) — ask before proceeding |
-| P2 | Naming or structure inconsistency — warn and apply best guess |
-| P3 | Missing optional fields — document assumption and proceed |
-
----
-
-## Workflow
-
-### Phase 1 — Input Validation
-
-Before parsing, verify:
-- URL is valid and method is correct (GET/POST/PUT/PATCH/DELETE)
-- Auth format is identifiable (Bearer, API Key, OAuth2, Basic, Cookie)
-- Request info is present (path params, query params, body)
-- Response structure is clear (JSON, binary, stream, paginated)
-- Error cases are documented
-
-If critical info is missing → **stop and ask**. Do not guess.
-
-```json
-{
-  "validation": {
-    "status": "VALID | INVALID | INCOMPLETE",
-    "confidence": 0.95,
-    "errors": [],
-    "warnings": [],
-    "input_type": "curl | openapi | postman | docs | code"
-  }
-}
-```
-
----
-
-### Phase 2 — API Contract Extraction
-
-Extract the full contract:
-
-```
-metadata:
-  name, domain, endpoint, method, version, description
-
-request:
-  pathParams:    { name, type, required }
-  queryParams:   { name, type, required, default }
-  headers:       { name, value, required }
-  body:          { contentType, schema { field, type, required, nullable } }
-  auth:          { type, location, name }
-
-response:
-  success:       { statusCode, contentType, schema, pagination? }
-  errors:        [ { statusCode, message, businessCode? } ]
-
-special:
-  rateLimit, timeout, retryable, streaming
-```
-
-Map each field: `type`, `required`, `nullable`, `enum`, `example`.
-
----
-
-### Phase 3 — Project Profile Detection
-
-1. Check for `.api-config.json` at project root → use if present
-2. Otherwise infer from:
-   - Framework: `package.json`, config files, imports
-   - HTTP client: existing axios instance, fetch wrapper, custom client
-   - State management: React Query, Redux, Zustand, Pinia, Apollo, Vuex
-   - Type system: `tsconfig.json`, JSDoc, plain JS
-   - Folder conventions: `services/`, `hooks/`, `api/`, `types/`, `adapters/`
-   - Naming: camelCase, PascalCase, snake_case, file patterns
-3. Read 1-2 existing API files to capture exact patterns for imports, typing, error handling, naming
-
-If project context is ambiguous → use conservative defaults and document all assumptions.
-
----
-
-### Phase 4 — Conflict Detection
-
-Before generating code, check for:
-
-| Conflict | Action |
-|----------|--------|
-| `ENDPOINT_DUPLICATE` — endpoint already exists | Reuse if same, warn if different |
-| `FUNCTION_DUPLICATE` — function name conflicts | Warn, propose new name |
-| `TYPE_DUPLICATE` — type already defined | Extend or reuse existing |
-| `LOGIC_OVERLAP` — logic exists in another service | Consolidate, don't duplicate |
-| `IMPORT_CONFLICT` — import path conflicts | Resolve before generating |
-
-**P0 conflict → stop, report, wait for user decision before proceeding.**
-
----
-
-### Phase 5 — Code Generation
-
-Generate the minimum necessary set for the task:
-
-#### TypeScript Types
-```typescript
-// Request types
-export interface CreateUserRequest {
-  name: string;
-  email: string;
-  role?: UserRole;
-}
-
-// Response types
-export interface CreateUserResponse {
-  id: string;
-  name: string;
-  email: string;
-  createdAt: string;
-}
-
-// Error types
-export interface ApiError {
-  code: string;
-  message: string;
-  details?: Record<string, unknown>;
-}
-```
-
-#### Service / API Layer
-```typescript
-// Thin layer: HTTP + mapping only. No UI, no business logic.
-export const createUser = async (
-  data: CreateUserRequest
-): Promise<CreateUserResponse> => {
-  const response = await apiClient.post<CreateUserResponse>('/users', data);
-  return response.data;
-};
-```
-
-#### Hook / Query (if project uses React Query)
-```typescript
-export const useCreateUser = () => {
-  return useMutation<CreateUserResponse, ApiError, CreateUserRequest>({
-    mutationFn: createUser,
-    onSuccess: () => {
-      queryClient.invalidateQueries({ queryKey: ['users'] });
-    },
-  });
-};
-```
-
-**If project uses Redux** → follow existing slice/thunk pattern.
-**If project uses Zustand** → follow existing store pattern.
-**If project uses Pinia/Vuex** → follow existing composable/action pattern.
-
-Do NOT mix patterns.
-
----
-
-### Phase 6 — Special Case Handling
-
-#### File Upload (`multipart/form-data`)
-```typescript
-// Always use FormData — never send File object in JSON
-const formData = new FormData();
-formData.append('file', file);
-formData.append('name', name);
-await apiClient.post('/upload', formData, {
-  headers: { 'Content-Type': 'multipart/form-data' },
-});
-```
-
-#### File Download (binary response)
-```typescript
-const response = await apiClient.get('/export', { responseType: 'blob' });
-const url = URL.createObjectURL(response.data);
-const a = document.createElement('a');
-a.href = url;
-a.download = filename;
-a.click();
-URL.revokeObjectURL(url);
-```
-
-#### Pagination
-```typescript
-interface PaginatedResponse<T> {
-  items: T[];
-  total: number;
-  page: number;
-  limit: number;
-}
-// Implement consistently with existing project pagination pattern
-```
-
-#### Authentication
-- Follow existing auth mechanism (interceptor, header injection, cookie)
-- Never hardcode tokens or credentials
-- Refresh token logic belongs in the existing interceptor
-
----
-
-### Phase 7 — Quality Validation
-
-Before marking as ready:
-
-- [ ] TypeScript strict — compiles clean, no `any` without justification
-- [ ] All functions/params have explicit types and return types
-- [ ] No unused imports, no debug code
-- [ ] Error handling complete (try/catch, `.catch`, fallback)
-- [ ] No hardcoded URLs, tokens, or secrets — use env vars
-- [ ] Naming matches project conventions
-- [ ] Reuses existing HTTP client, interceptors, and query client
-- [ ] JSDoc added for public API if project convention requires it
-- [ ] React: dependency arrays correct, cleanup present, no race conditions
-
----
-
-## Decision Tree
-
-```
-Is required info complete?
   ├── No  → Ask for missing info (auth, response schema, base URL)
   └── Yes → Check for conflicts
               ├── P0 conflict → Stop, report, wait for user decision