@edupia-tutor/spec-driven-docs 0.14.0 → 0.14.2

package/skills/code/SKILL.tmpl

@@ -1,10 +1,10 @@
 ---
-description: Generates implementation code from approved BDD specs with traceability tags, or performs a read-only code review against spec compliance and architecture rules. Trigger when: "/generate-code", "/review-code", "sinh code", "generate code", "viết code", "implement feature", "review code", "kiểm tra code", "code review", "check implementation".
+description: Sinh implementation code từ BDD spec đã duyệt kèm tag traceability, hoặc review code read-only đối chiếu spec compliance và quy tắc kiến trúc. Trigger when: "/generate-code", "/review-code", "sinh code", "generate code", "viết code", "implement feature", "review code", "kiểm tra code", "code review", "check implementation".
 ---
 
 # Code Skills — Generate & Review
 
-This skill handles `/generate-code` (implementation) and `/review-code` (read-only review).
+Skill này xử lý `/generate-code` (implementation) và `/review-code` (review read-only).
 
 ---
 
@@ -15,10 +15,10 @@ This skill handles `/generate-code` (implementation) and `/review-code` (read-on
 <!-- Directory: specs/*/*/bdd/*.feature -->
 {{include:steps/gate.md}}
 
-4. Check for existing trace state: read `.trace/{domain}/{prd-slug}/{UC-ID}.tsv` if it exists.
-   - Identify: new scenarios vs. drifted (changed) vs. synced (skip)
+4. Kiểm tra trace state có sẵn: đọc `.trace/{domain}/{prd-slug}/{UC-ID}.tsv` nếu tồn tại.
+   - Xác định: scenario mới vs. drifted (đã đổi) vs. synced (skip)
 
-5. Show **CHECKPOINT — Comprehension**:
+5. Hiện **CHECKPOINT — Comprehension**:
    ```
    I understand:
    - Feature: {name} | Ticket: {TICKET_ID if known}
@@ -29,20 +29,20 @@ This skill handles `/generate-code` (implementation) and `/review-code` (read-on
 
    Proceed? (Y/N)
    ```
-   Wait for confirmation.
+   Chờ xác nhận.
 
 ### Context Load
 
 {{include:steps/context-loader.md}}
 
-Also read:
-- `.feature` file (what to implement)
-- Tech doc `specs/{domain}/{prd-slug}/tech-docs/{UC-ID}-tech-design.md` (if exists)
-- Existing entity/model files in this domain (to follow patterns)
+Cũng đọc:
+- File `.feature` (cần implement gì)
+- Tech doc `specs/{domain}/{prd-slug}/tech-docs/{UC-ID}-tech-design.md` (nếu tồn tại)
+- File entity/model có sẵn trong domain này (để theo pattern)
 
 ### Branch
 
-Create a feature branch:
+Tạo feature branch:
 ```bash
 git checkout -b feature/{TICKET_ID}-{slug}
 # If no ticket ID: feature/{UC-ID}-{slug}
@@ -50,37 +50,37 @@ git checkout -b feature/{TICKET_ID}-{slug}
 
 ### Generate
 
-Generate code in layer order (adapt to your stack):
+Sinh code theo thứ tự layer (thích ứng theo stack của bạn):
 
-**For a typical layered backend (e.g., Controller → Service → Repository):**
+**Cho một backend phân lớp điển hình (vd Controller → Service → Repository):**
 
-1. **DTOs / Request-Response models** — input validation, output shape
-2. **Domain entity / model** — data representation
-3. **Repository / Data Access** — queries, filters
+1. **DTOs / Request-Response models** — validate input, shape output
+2. **Domain entity / model** — biểu diễn dữ liệu
+3. **Repository / Data Access** — query, filter
 4. **Service interface** — contract
-5. **Service implementation** — business logic, `@Transactional` where needed
-6. **Facade interface** (if architecture uses facade layer) — orchestration contract
-7. **Facade implementation** — cross-service orchestration
-8. **Controller / Handler** — HTTP mapping, auth, `@trace` tags
+5. **Service implementation** — business logic, `@Transactional` khi cần
+6. **Facade interface** (nếu kiến trúc dùng facade layer) — contract orchestration
+7. **Facade implementation** — orchestration liên-service
+8. **Controller / Handler** — HTTP mapping, auth, tag `@trace`
 
-**Critical: Traceability tags on every controller method:**
+**Quan trọng: Tag traceability trên mỗi controller method:**
 ```
 # @trace.implements={UC-ID}-SC{N}
 # @trace.source=specs/{domain}/{prd-slug}/bdd/{UC-ID}.feature
 ```
-(Use your language's comment syntax)
+(Dùng cú pháp comment của ngôn ngữ bạn)
 
-### Self-Review (3 rounds)
+### Self-Review (3 vòng)
 
-After generating, verify:
-- [ ] Every scenario in .feature has a corresponding controller endpoint
-- [ ] `@trace.implements` tag on every endpoint
-- [ ] Architecture layer rules respected (from CLAUDE.md)
-- [ ] Error handling matches CLAUDE.md §error_handling
-- [ ] No magic numbers, no debug logging
-- [ ] Coding standards from CLAUDE.md followed
+Sau khi sinh, verify:
+- [ ] Mỗi scenario trong .feature có controller endpoint tương ứng
+- [ ] Tag `@trace.implements` trên mỗi endpoint
+- [ ] Tôn trọng quy tắc layer kiến trúc (từ CLAUDE.md)
+- [ ] Error handling khớp CLAUDE.md §error_handling
+- [ ] Không magic number, không debug logging
+- [ ] Theo coding standards từ CLAUDE.md
 
-If issues found → fix inline before proceeding.
+Nếu phát hiện issue → fix inline trước khi tiếp tục.
 
 ### Build Verify
 
@@ -88,11 +88,11 @@ If issues found → fix inline before proceeding.
 {BUILD_COMMAND}   # from project-context.yaml, max 3 retries
 ```
 
-If build fails: read error, fix, retry. After 3 failures, report to user with diagnosis.
+Nếu build fail: đọc lỗi, fix, retry. Sau 3 lần fail, report cho user kèm diagnosis.
 
 ### Write Trace State
 
-Update `.trace/{domain}/{prd-slug}/{UC-ID}.tsv`:
+Cập nhật `.trace/{domain}/{prd-slug}/{UC-ID}.tsv`:
 ```
 UC-ID\tSC-ID\tsc_version\timplemented_by\tlast_updated
 {UC-ID}\tSC1\t{hash of scenario text}\t{ControllerClass}.{method}\t{date}
@@ -119,38 +119,38 @@ git commit -m "{commit_format from CLAUDE.md}: {description}"
 
 ---
 
-## /review-code — Read-Only Code Review
+## /review-code — Code Review chỉ-đọc
 
-**IMPORTANT**: This is READ-ONLY. Report issues but do NOT make changes.
+**QUAN TRỌNG**: Đây là READ-ONLY. Report issue nhưng KHÔNG sửa.
 
 ### Input
 
-Accept: UC-ID, file path, or current branch name.
+Nhận: UC-ID, file path, hoặc tên branch hiện tại.
 
 ### Review Dimensions
 
 #### 1. Traceability
-- [ ] Every controller endpoint has `@trace.implements` tag?
-- [ ] Every test file has `@trace.verifies` tag?
-- [ ] No `@trace` tags on non-controller layers (Service, Repository, etc.)?
-- [ ] `.trace/{domain}/{prd-slug}/{UC-ID}.tsv` is up to date?
-
-#### 2. Layer Architecture (from CLAUDE.md)
-- [ ] Each class is in the correct layer?
-- [ ] Layer dependencies flow in the right direction?
-- [ ] No layer is bypassed (e.g., Controller calling Repository directly)?
-
-#### 3. Coding Standards (from CLAUDE.md)
-- [ ] Naming conventions followed?
-- [ ] Response wrapper used consistently?
-- [ ] Exceptions thrown (not swallowed or manually built into responses)?
-- [ ] No magic numbers?
-- [ ] No sensitive data in logs?
-- [ ] Transaction annotations correct?
+- [ ] Mỗi controller endpoint có tag `@trace.implements`?
+- [ ] Mỗi test file có tag `@trace.verifies`?
+- [ ] Không có tag `@trace` ở layer không phải controller (Service, Repository, v.v.)?
+- [ ] `.trace/{domain}/{prd-slug}/{UC-ID}.tsv` cập nhật chưa?
+
+#### 2. Layer Architecture (từ CLAUDE.md)
+- [ ] Mỗi class ở đúng layer?
+- [ ] Phụ thuộc giữa layer đi đúng chiều?
+- [ ] Không layer nào bị bypass (vd Controller gọi Repository trực tiếp)?
+
+#### 3. Coding Standards (từ CLAUDE.md)
+- [ ] Tuân theo naming convention?
+- [ ] Response wrapper dùng nhất quán?
+- [ ] Exception được throw (không bị nuốt hoặc tự build vào response)?
+- [ ] Không magic number?
+- [ ] Không dữ liệu nhạy cảm trong log?
+- [ ] Annotation transaction đúng?
 
 #### 4. Spec Compliance
-- [ ] Every scenario in .feature has an implementation?
-- [ ] No undocumented endpoints (code not backed by spec)?
+- [ ] Mỗi scenario trong .feature có implementation?
+- [ ] Không có endpoint không tài liệu (code không có spec backing)?
 
 ### Output
 
@@ -171,6 +171,6 @@ Critical: {X}  |  Major: {Y}  |  Minor: {Z}
 Verdict: APPROVED ✅ | NEEDS_FIX ❌
 ```
 
-If `NEEDS_FIX`: list specific files to change and run `/fix-bug` or correct inline.
+Nếu `NEEDS_FIX`: liệt kê file cụ thể cần đổi và chạy `/fix-bug` hoặc sửa inline.
 
 {{include:steps/report-footer.md}}