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

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

@@ -1,72 +1,38 @@
 ---
 name: qk-api-lifecycle
-version: 3.1.5
-updated: 2026-07-02
-description: Thiết kế, triển khai, và tích hợp các API endpoints.
-category: engineering
-behavior: development
-intent: implement-feature
-priority: high
-tags: [api, backend, frontend-integration, endpoints]
-platforms: [claude-code, cursor, windsurf, gemini-cli]
-trigger: User wants to create a new API, fix an API, or integrate frontend with backend API.
-inputs: [API requirements, JSON schema, or Backend URL]
-outputs: [API routes, Service classes, API Hooks]
-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-api-lifecycle - Standard Operating Procedure
+# qk-api-lifecycle
 
-> **Goal:** Quản lý toàn bộ vòng đời của một API, từ việc thiết kế Spec (Swagger/Types) cho đến khi Backend code xong và Frontend gọi thành công.
+## Scope
+- API design, endpoints, contracts, and lifecycle management (Plan & Execute)
 
-## 🔄 1. Chain of Thought (SOP)
-
-1. **Analyze (Contract Definition):**
-   - Read the user requirements.
-   - Define the exact API contract (Request Body, Query Params, Response DTO) in TypeScript interfaces or OpenAPI spec.
-2. **Plan (Architecture Selection):**
-   - Determine if the task is Backend (creating the endpoint) or Frontend (consuming the endpoint).
-   - If Frontend: Load `knowledge/frontend/react.md` to decide between React Query vs raw fetch.
-   - If Backend: Choose the appropriate layer (Controller -> Service -> Repository).
-3. **Execute (Implementation):**
-   - Write the backend handler/controller with strict validation (e.g., Zod, Class Validator).
-   - **Security:** Integrate Auth Middleware (JWT/RBAC) before the Controller. DO NOT expose public endpoints unless explicitly requested.
-   - Write the frontend API client (e.g., Axios instance wrapper).
-4. **Verify (Validation):**
-   - Handle Error Status Codes (400, 401, 403, 404, 500) gracefully.
-   - Ensure loading states are managed on the frontend.
-
-## 🛡️ 2. Constraints & Rules
-
-- **No Hardcoded URLs:** Never hardcode `http://localhost:3000` inside frontend components. Always use environment variables (`process.env.API_URL`).
-- **Separation of Concerns:** Do NOT write `fetch` or `axios.get` directly inside a React UI component. Extract it to a custom hook or an API service file.
-- **Pagination & Rate Limit:** Any `GET` API returning a list MUST include Pagination by default to prevent server OOM.
-
-## 🌳 3. Decision Tree
-
-```text
-Is this a Backend or Frontend task?
-  ├── BACKEND → Does the API need Database access?
-  │       ├── YES → Handoff to `qk-data-lifecycle` to create models first.
-  │       └── NO → Write Controller and Service.
-  └── FRONTEND → Are we fetching data to display or mutating data?
-          ├── FETCH → Use React Query `useQuery` or equivalent.
-          └── MUTATE → Use React Query `useMutation` or equivalent.
+## Constraints
+```yaml
+must:
+  - Define clear request/response contracts (OpenAPI/Swagger)
+  - Ensure backward compatibility on existing endpoints
+must_not:
+  - Introduce breaking changes without versioning
+  - Bypass authentication or authorization checks
 ```
 
-## 🤝 4. Handoff Pipeline
-
-1. `engineering-standard`: Verify API naming conventions (e.g., `GET /users` instead of `POST /getUsers`).
-2. `validate`: Run API tests and Type-checks.
-3. `complete`: Generate the final report.
-
-## 📝 5. Output Format
+## Policies
+```yaml
+prefer:
+  - RESTful resource naming conventions
+  - Meaningful HTTP status codes
+```
 
-Vui lòng trả kết quả bằng Tiếng Việt. Sử dụng template chuẩn của hệ thống:
+## Escalation
+```yaml
+stop:
+  - Required API contracts or models are missing
+  - Major breaking change detected on production APIs
+```
 
-- **Tóm tắt (Summary):** Các endpoint đã tạo hoặc tích hợp.
-- **Chi tiết (Changes):** File nào chứa logic API.
-- **Kiến trúc (Reasoning):** Lý do chọn thư viện hoặc cách bắt lỗi (Error handling).
-- **Xác thực (Verification):** Cách gọi thử API.
-- **Rủi ro (Risks):** Vấn đề bảo mật CORS hoặc Rate Limit (nếu có).
+## Output
+- API endpoints, controllers, and documentation
+```

package/skills/qk-bug-resolution/SKILL.md

@@ -1,76 +1,39 @@
 ---
 name: qk-bug-resolution
-version: 3.1.5
-updated: 2026-07-02
-description: Xử lý và sửa các lỗi (bugs), đồng thời ngăn ngừa lỗi hồi quy.
-category: engineering
-behavior: development
-intent: fix-bug
-priority: high
-tags: [bug, debug, regression]
-platforms: [claude-code, cursor, windsurf, gemini-cli]
-trigger: User reports an error or crash.
-inputs: [Error log, Bug description, File path]
-outputs: [Fixed code, Verification report]
-allowed_tools: [run_command, read_file, grep_search]
-pipeline: [analyze, implement, engineering-standard, validate, complete]
+category: maintenance
+version: 6.0.0
 ---
 
-# 🛠️ qk-bug-resolution - Standard Operating Procedure
+# qk-bug-resolution
 
-> **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).
+## Scope
+- Existing defects only (Diagnose)
 
-## 🔄 1. Chain of Thought (SOP)
-
-1. **Analyze (Root Cause Analysis & Reproduce):**
-   - Read the provided error log or bug description.
-   - Identify how to reproduce the bug. Ask the user for more info if it is unclear.
-   - Trace the error to the exact file and line of code.
-   - Identify if the bug is a syntax error, logic error, state issue, or boundary case.
-2. **Plan (Fix Strategy):**
-   - Determine the minimal change required to fix the bug.
-   - If the bug is UI-related, refer to frontend knowledge (e.g., `knowledge/frontend/react.md`).
-3. **Execute (Implement Fix):**
-   - Modify the source code exactly where needed.
-   - Do NOT rewrite unrelated code blocks.
-4. **Verify (Validation):**
-   - Provide steps to test the fix.
-   - Ensure backward compatibility.
-
-## 🛡️ 3. Constraints & Rules
-
-- **No Guesses:** Do not assume the shape of an API response. Print it or read the type definitions first.
-- **Minimal Fix:** Always prefer a 1-line fix over a 100-line refactor, unless the architecture is fundamentally broken.
-- **Clean Up:** Remove any `console.log()` or debugger statements introduced during the debugging process.
-- **Regression Test:** Add at least 1 Unit or Integration Test to prevent this bug from recurring.
-
-## 🌳 3. Decision Tree
-
-```text
-Is there a Stack Trace?
-  ├── YES → Use grep_search to find the exact file and line number.
-  └── NO → Ask the user for the file path or use grep_search with keywords from the bug description.
-
-Is the bug related to State/Re-rendering?
-  ├── YES → Load `knowledge/frontend/react.md` to check for stale closures or missing dependencies.
-  └── NO → Proceed with standard logic debugging.
+## Constraints
+```yaml
+must:
+  - Collect evidence (stack trace/logs) before diagnosis
+  - Verify fix before completion
+must_not:
+  - Rewrite modules
+  - Guess root cause without evidence
 ```
 
-## 🤝 4. Handoff Pipeline
-
-After implementing the fix, map to the pipeline:
-
-1. `engineering-standard`: Ensure the fix follows naming and architecture rules.
-2. `validate`: Run linters and tests (via `qk-validation-gate` equivalent).
-3. `complete`: Output the final report.
-
-## 📝 5. Output Format
+## Policies
+```yaml
+prefer:
+  - Minimal patch
+  - Regression prevention
+```
 
-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:
+## Escalation
+```yaml
+stop:
+  - Missing logs/evidence
+  - Fix requires major architectural changes
+```
 
-- Summary
-- Changes
-- Root Cause
-- Verification
-- Risks
-- Next Action
+## Output
+- Minimal patch
+- Risk summary
+```

package/skills/qk-context-loader/SKILL.md

@@ -1,55 +1,36 @@
 ---
 name: qk-context-loader
-version: 3.1.5
-updated: 2026-07-02
-description: Tải các file liên quan và vẽ biểu đồ phụ thuộc (dependency graph) cho một tác vụ.
 category: utilities
-behavior: static-analysis
-intent: review-code
-priority: medium
-tags: [context, filesystem, dependencies, graph]
-platforms: [claude-code, cursor, windsurf, gemini-cli]
-trigger: AI needs to understand the surrounding files before modifying a core component.
-inputs: [Target File]
-outputs: [Loaded Context, Dependency Graph]
-allowed_tools: [grep_search, read_file, list_dir]
-pipeline: [analyze, implement, complete]
+version: 6.0.0
 ---
 
-# 🛠️ qk-context-loader - Standard Operating Procedure
+# qk-context-loader
 
-> **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.
+## Scope
+- Context collection and dependency mapping (Collect)
 
-## 🔄 1. Chain of Thought (SOP)
-
-1. **Analyze (Target Identification):**
-   - Identify the main file that needs modification.
-2. **Implement (Graph Traversal):**
-   - **Load Parents:** Search for files that import the target file.
-   - **Load Children:** Read the target file to see what it imports.
-   - Gather the essential chunks of these related files.
-3. **Complete (Context Mapping):**
-   - Build a mental map of how the data flows.
-
-## 🛡️ 2. Constraints & Rules
-
-- **Token Optimization:** Do not load `node_modules` or massive minified build files. Extract only the exact logic needed.
-
-## 🌳 3. Decision Tree
-
-```text
-Is the target file a UI Component?
-  ├── YES → Load its CSS/Theme tokens and any nested Child components.
-  └── NO (API Service) → Load the corresponding Controller and Database Model.
+## Constraints
+```yaml
+must:
+  - Find and load related dependency files
+must_not:
+  - Modify code
+  - Load entire repo or node_modules
+  - Hallucinate filenames
 ```
 
-## 🤝 4. Handoff Pipeline
-
-1. `complete`: Provide the context map to the Orchestrator or Target Skill.
-
-## 📝 5. Output Format
+## Policies
+```yaml
+prefer:
+  - Build dependency graph
+```
 
-Vui lòng trả kết quả bằng Tiếng Việt.
+## Escalation
+```yaml
+stop:
+  - Repo or files are inaccessible
+```
 
-- **Tóm tắt (Summary):** Đã nạp thành công ngữ cảnh.
-- **Chi tiết (Changes):** Các file có liên quan trực tiếp.
+## Output
+- Context mapping
+```

package/skills/qk-data-lifecycle/SKILL.md

@@ -1,68 +1,35 @@
 ---
 name: qk-data-lifecycle
-version: 3.1.5
-updated: 2026-07-02
-description: Quản lý Database Schema, Migrations, và Repositories.
-category: database
-behavior: development
-intent: implement-feature
-priority: medium
-tags: [database, sql, migration, schema, orm]
-platforms: [claude-code, cursor, windsurf, gemini-cli]
-trigger: User asks to create a new database table, modify schema, or write complex queries.
-inputs: [Data model requirements]
-outputs: [Migration scripts, Models, Repositories]
-allowed_tools: [run_command, read_file, write_to_file]
-pipeline: [analyze, design, implement, engineering-standard, validate, complete]
+category: infrastructure
+version: 6.0.0
 ---
 
-# 🛠️ qk-data-lifecycle - Standard Operating Procedure
+# qk-data-lifecycle
 
-> **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.
+## Scope
+- Database Schema, Migrations, and Repositories management (Plan & Execute)
 
-## 🔄 1. Chain of Thought (SOP)
-
-1. **Analyze (Requirements):**
-   - Understand the entities and their relationships (1:1, 1:N, N:N).
-   - Identify the ORM/Query Builder used in the project (e.g., Prisma, TypeORM, Drizzle).
-2. **Design (Schema & Normalization):**
-   - Design the schema. Ensure foreign keys and indices are applied to frequently queried columns.
-   - Always include audit columns (`created_at`, `updated_at`).
-3. **Implement (Migration & Models):**
-   - Write the Migration script. MUST include both `up` (apply) and `down` (rollback) logic.
-   - Write/Update the Model/Entity files.
-   - Create Repository layer functions if necessary.
-4. **Verify (Safety Check):**
-   - Review the migration script for destructive operations (e.g., `DROP TABLE`, `DROP COLUMN`).
-
-## 🛡️ 2. Constraints & Rules
-
-- **No Data Loss:** NEVER execute a migration that drops data on Production without explicit User approval and a backup plan.
-- **Decoupling:** Do not write SQL queries directly in Controllers. Always use the Repository or DAO pattern.
-- **Index Rule:** Any column used in a `WHERE`, `JOIN`, or `ORDER BY` clause should be evaluated for an index.
-
-## 🌳 3. Decision Tree
-
-```text
-Is this modifying an existing table in Production?
-  ├── YES → Does it drop a column or change a data type destructively?
-  │       ├── YES → STOP. Create a new column, migrate data, then drop the old one (Expand & Contract Pattern).
-  │       └── NO → Proceed with safe migration (e.g., ADD COLUMN).
-  └── NO (New Table) → Ensure Primary Key, Timestamps, and Foreign Keys are defined.
+## Constraints
+```yaml
+must:
+  - Ensure data schema matches application domain models
+  - Generate reversible migration scripts
+must_not:
+  - Perform destructive schema changes without explicit user approval
 ```
 
-## 🤝 4. Handoff Pipeline
-
-1. `engineering-standard`: Verify naming conventions (e.g., snake_case for DB columns if required).
-2. `validate`: Run dry-run migrations or unit tests.
-3. `complete`: Generate the Database report.
-
-## 📝 5. Output Format
+## Policies
+```yaml
+prefer:
+  - Declarative schema definitions over imperative scripts
+```
 
-Vui lòng trả kết quả bằng Tiếng Việt.
+## Escalation
+```yaml
+stop:
+  - Migration script risks massive data loss
+```
 
-- **Tóm tắt (Summary):** Bảng nào được tạo/sửa.
-- **Chi tiết (Changes):** File migration và Model đã sinh ra.
-- **Kiến trúc (Reasoning):** Lý do thiết kế quan hệ bảng và các Index.
-- **Rủi ro (Risks):** Đánh giá mức độ an toàn của Migration (Có làm mất data không?).
-- **Hành động tiếp (Next Action):** Hướng dẫn user chạy lệnh migrate.
+## Output
+- Database schemas and migration scripts
+```

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

@@ -1,63 +1,35 @@
 ---
 name: qk-db-optimizer
-version: 1.0.0
-updated: 2026-07-02
-description: Tối ưu hóa Database (đánh Index, xử lý N+1 Queries, Slow Queries).
-category: database
-behavior: development
-intent: implement-feature
-priority: high
-tags: [database, optimize, sql, index, performance]
-platforms: [claude-code, cursor, windsurf, gemini-cli]
-trigger: User asks to optimize database, fix slow queries, add index, or resolve N+1 issues.
-inputs: [Database Schema, Slow Query Log or ORM code]
-outputs: [Optimized Query/ORM code, Migration script for Indexes]
-allowed_tools: [run_command, read_file, write_to_file, grep_search]
-pipeline: [analyze, plan, implement, validate, complete]
+category: infrastructure
+version: 6.0.0
 ---
 
-# 🛠️ qk-db-optimizer - Standard Operating Procedure
+# qk-db-optimizer
 
-> **Goal:** Tối ưu hóa hiệu suất cơ sở dữ liệu. Đóng vai trò là một Database Administrator (DBA) / Performance Engineer. Giải quyết các bài toán cổ điển như N+1 queries, thiếu Index, truy vấn chậm.
+## Scope
+- Database optimization (Indexes, N+1 Queries, Slow Queries) (Diagnose & Evaluate)
 
-## 🔄 1. Chain of Thought (SOP)
-
-1. **Analyze (Bottleneck Identification):**
-   - Read the relevant ORM code (Prisma, TypeORM, Drizzle) or raw SQL.
-   - Identify the source of the slowdown (e.g., fetching in a loop causing N+1).
-2. **Plan (Optimization Strategy):**
-   - Decide whether to optimize the query structure (e.g., using `JOIN` / `include`) or add an Index to the database schema.
-3. **Implement (Code & Schema changes):**
-   - Refactor the code to eliminate N+1 queries.
-   - Write migration scripts or update the ORM schema to add necessary Indexes.
-4. **Verify (Explain & Test):**
-   - Ensure the new query yields the same correct result.
-
-## 🛡️ 2. Constraints & Rules
-
-- **No Destructive Operations:** Never drop tables or columns unless explicitly asked by the user to do so.
-- **Explain First:** Always explain why a query is slow and how your index/refactor fixes it.
-
-## 🌳 3. Decision Tree
-
-```text
-Is it an N+1 Query problem?
-  ├── YES → Use Eager Loading (e.g., `.include()` in Prisma) or a DataLoader pattern.
-  └── NO → Is it a slow filtering/sorting issue?
-             ├── YES → Add a database Index (B-Tree, Hash, etc.) to the relevant columns.
-             └── NO → Refactor the raw SQL/ORM logic to be more efficient.
+## Constraints
+```yaml
+must:
+  - Analyze query execution plans if available
+  - Suggest non-breaking performance fixes
+must_not:
+  - Change database engine or major architecture without consent
 ```
 
-## 🤝 4. Handoff Pipeline
-
-1. `validate`: Run tests using `qk-validation-gate` to ensure no data regressions.
-2. `complete`: Generate the Database Optimization report.
-
-## 📝 5. Output Format
+## Policies
+```yaml
+prefer:
+  - Adding indexes before rewriting complex queries
+```
 
-Vui lòng trả kết quả bằng Tiếng Việt.
+## Escalation
+```yaml
+ask:
+  - For exact slow query logs if not provided
+```
 
-- **Tóm tắt (Summary):** Vấn đề gì đã được giải quyết.
-- **Chi tiết (Changes):** Cách khắc phục (đánh index hay refactor code).
-- **Hiệu năng (Performance):** Giải thích tại sao cách mới lại nhanh hơn.
-- **Xác thực (Verification):** ...
+## Output
+- Optimization plan and SQL patches
+```

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

@@ -1,53 +1,37 @@
 ---
 name: qk-design-to-code
-version: 3.1.5
-updated: 2026-07-02
-description: Chuyển đổi thiết kế từ Figma/Images thành các UI component hoàn chỉnh, chuẩn pixel.
 category: frontend
-behavior: development
-intent: implement-feature
-priority: high
-tags: [ui, figma, frontend, styling, css]
-platforms: [claude-code, cursor, windsurf, gemini-cli]
-trigger: User uploads an image mockup or provides a design requirement for a UI component.
-inputs: [Image/Mockup, Framework choice]
-outputs: [Code component, CSS/Tailwind classes]
-allowed_tools: [write_to_file, read_file]
-pipeline: [analyze, implement, engineering-standard, validate, complete]
+version: 6.0.0
 ---
 
-# 🛠️ qk-design-to-code - Standard Operating Procedure
-
-> **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.
-
-## 🔄 1. Chain of Thought (SOP)
-
-1. **Analyze (Deconstruct Design):**
-   - Look at the provided mockup.
-   - Break it down from Outside-In (Container -> Rows -> Columns -> Elements).
-2. **Plan (Token Mapping):**
-   - Map colors, fonts, and spacings to existing Design System Tokens (e.g., Tailwind classes `text-primary-500`, `gap-4`).
-3. **Implement (Code Construction):**
-   - Write the semantic HTML (`<article>`, `<section>`, `<nav>`).
-   - Apply styling.
-4. **Validate (Responsive Check):**
-   - Ensure the component uses relative units where necessary and scales on mobile.
-
-## 🛡️ 2. Constraints & Rules
-
-- **No Magic Values:** Do not use random hex codes or pixel values if a Design System is available.
-- **Accessibility:** Always include `alt` for images and `aria-label` for icon-only buttons.
-
-## 🤝 3. Handoff Pipeline
-
-1. `engineering-standard`: Ensure the UI component has no business logic.
-2. `validate`: Trigger `qk-ui-audit` checks.
-3. `complete`: Generate the UI Component Report.
-
-## 📝 4. Output Format
-
-Vui lòng trả kết quả bằng Tiếng Việt.
-
-- **Tóm tắt (Summary):** Tên Component vừa tạo.
-- **Chi tiết (Changes):** File chứa component.
-- **Rủi ro (Risks):** Vấn đề responsive nếu có.
+# qk-design-to-code
+
+## Scope
+- Converting Figma/UI designs into pixel-perfect frontend code (Execute)
+
+## Constraints
+```yaml
+must:
+  - Use the project's existing design system / tokens
+  - Ensure responsive layouts
+must_not:
+  - Hardcode magic numbers for spacing/colors
+  - Invent new UI components if existing ones suffice
+```
+
+## Policies
+```yaml
+prefer:
+  - Semantic HTML elements
+  - CSS Grid / Flexbox over absolute positioning
+```
+
+## Escalation
+```yaml
+stop:
+  - Design assets or requirements are ambiguous
+```
+
+## Output
+- Frontend components and stylesheets
+```

package/skills/qk-docs/SKILL.md

@@ -1,62 +1,36 @@
 ---
 name: qk-docs
-version: 3.1.5
-updated: 2026-07-02
-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
-behavior: static-analysis
-intent: maintain
-priority: low
-tags: [docs, markdown, jsdoc, readme, architecture, mermaid]
-platforms: [claude-code, cursor, windsurf, gemini-cli]
-trigger: User asks to write docs, generate architecture diagrams, update README, or write JSDoc.
-inputs: [Source code, Task context]
-outputs: [Markdown Documentation, JSDoc]
-allowed_tools: [read_file, write_to_file]
-pipeline: [analyze, implement, validate, complete]
+category: utilities
+version: 6.0.0
 ---
 
-# 🛠️ qk-docs - Standard Operating Procedure
+# qk-docs
 
-> **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.
+## Scope
+- Writing and maintaining project documentation for human readability (Execute)
 
-## 🔄 1. Chain of Thought (SOP)
-
-1. **Analyze (Context Extraction):**
-   - Read the target source code to understand its Inputs, Outputs, and side effects.
-2. **Implement (Drafting):**
-   - Write Markdown or JSDoc comments.
-   - Structure: Description -> Parameters -> Returns -> Warnings/Notes.
-3. **Validate (Review Examples):**
-   - ALWAYS provide 1-2 real-world code examples demonstrating how to use the function/API.
-4. **Complete (Format):**
-   - Ensure proper Markdown syntax (bolding, code blocks with languages).
-
-## 🛡️ 2. Constraints & Rules
-
-- **Human Friendly:** Avoid overly academic language. Explain it as if explaining to a junior developer.
-- **Language Hybrid:** If writing Vietnamese documentation, keep technical keywords (props, state, endpoint, fetch) in English.
-
-## 🌳 3. Decision Tree
-
-```text
-Is this a System Architecture or Flow?
-  ├── YES → Create Mermaid diagrams (Architecture, Sequence) and save to `/docs/`.
-  └── NO → Is this an API Documentation?
-             ├── YES → Use standard REST/GraphQL documentation layout (Endpoint, Method, Body, Response).
-             └── NO → Is it a Component Documentation?
-                        ├── YES → Document the Props interface and usage examples.
-                        └── NO → Write standard JSDoc or update README.
+## Constraints
+```yaml
+must:
+  - Keep documentation in sync with the actual codebase
+  - Use clear, accessible language
+must_not:
+  - Generate overly verbose or redundant docs
+  - Invent features that don't exist in the code
 ```
 
-## 🤝 4. Handoff Pipeline
-
-1. `complete`: Generate the Docs and save them to the project files.
-
-## 📝 5. Output Format
+## Policies
+```yaml
+prefer:
+  - Examples and code snippets over pure text
+```
 
-Vui lòng trả kết quả bằng Tiếng Việt.
+## Escalation
+```yaml
+stop:
+  - The codebase logic is too ambiguous to document accurately
+```
 
-- **Tóm tắt (Summary):** Tài liệu nào đã được tạo/cập nhật.
-- **Chi tiết (Changes):** Cấu trúc tài liệu.
-- **Xác thực (Verification):** Yêu cầu User đọc lướt qua tài liệu.
+## Output
+- Markdown documentation files
+```