ai-developer-skill-os 1.8.1 → 2.0.0

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

@@ -0,0 +1,371 @@
+---
+name: qk-bug-resolution
+purpose: Tái hiện lỗi, tìm root cause, sửa lỗi và chống hồi quy (Regression check).
+mode_supported: [standard]
+input: [Bug report]
+output: [Fixed code, Regression test]
+workflow: [1. Reproduce -> 2. Root Cause -> 3. Fix -> 4. Test]
+allowed_tools: [grep_search, run_command, replace_file_content]
+handoff_to: [qk-validation-gate]
+---
+
+# 🛠️ qk-bug-resolution - Quy Trình Vận Hành Chuẩn (SOP)
+
+> **Mô tả:** Tái hiện lỗi, tìm root cause, sửa lỗi và chống hồi quy (Regression check).
+
+## 🎯 1. Mục Tiêu (Goal)
+- Hoàn thành thành công tác vụ được giao liên quan đến nhiệm vụ của skill.
+- Đảm bảo chất lượng mã nguồn và tính nhất quán của hệ thống.
+
+## 🔄 2. Chuỗi Hành Động (Chain of Thought / SOP)
+*(Bắt buộc AI phải suy nghĩ và làm theo đúng thứ tự)*
+1. **Phân tích (Analyze):** Thu thập ngữ cảnh và hiểu rõ yêu cầu đầu vào.
+2. **Lên kế hoạch (Plan):** Xác định các bước cần thay đổi/tạo mới dựa trên bộ luật (rules).
+3. **Thực thi (Execute):** Tiến hành sửa đổi mã nguồn hoặc tạo tài liệu.
+4. **Xác thực (Verify):** Đảm bảo đầu ra đáp ứng đúng yêu cầu và không vi phạm quy định.
+
+## 🛡️ 3. Ràng Buộc & Quy Tắc (Constraints)
+- CẤM bỏ qua việc kiểm tra `qk-engineering-standard` trước khi viết code.
+- Mọi quyết định kỹ thuật phải dựa trên nội dung tại phần Deep Knowledge (nếu có).
+
+## 🤝 4. Giao Thức Bàn Giao (Handoff Protocol)
+- Đích đến: `qk-validation-gate`
+- Nội dung bàn giao: Chuyển toàn bộ ngữ cảnh và kết quả đã thực thi cho bước tiếp theo.
+
+## 📚 5. Kiến Thức Chuyên Sâu (Deep Knowledge)
+
+*(Nền tảng kiến thức và quy tắc chi tiết kế thừa từ kỹ sư)*
+
+---
+
+
+
+# Bug Fix — Diagnose & Repair
+
+> **Language rule:**
+> Use English for: code, identifiers, file names, architecture terms, technical decisions.
+> Use the user's language for: explanations, questions, summaries, and feedback.
+> The user may write in any language — detect and match it automatically.
+
+---
+
+## Trigger
+
+Activate this skill when:
+- User reports a specific bug with a stack trace, error message, or behavior description
+- A test is failing
+- The app crashes or hangs
+- A regression occurred after a code change
+- User says "it's broken", "this doesn't work", "I'm getting an error"
+
+**Not this skill** → Use `project-audit` if the problem is unknown and needs discovery first.
+
+---
+
+## Scope
+
+- ✅ Reproduce the reported bug
+- ✅ Identify the root cause (not just the symptom)
+- ✅ Apply a minimal, targeted fix
+- ✅ Verify the fix with evidence (tests, logs, comparison)
+- ✅ Prevent recurrence with guards or tests
+
+---
+
+## Non-goals
+
+- ❌ Do NOT refactor code outside the buggy area
+- ❌ Do NOT change public APIs unless the bug requires it
+- ❌ Do NOT silence errors with empty `try/catch` or blind `?.` / `!`
+- ❌ Do NOT change formatting or unrelated code
+- ❌ Do NOT mark as done without verifying the fix
+
+---
+
+## Severity Levels
+
+| Level | Meaning |
+|-------|---------|
+| P0 | Production down, data loss, security breach |
+| P1 | Core feature broken, blocking users |
+| P2 | Non-critical feature broken, workaround exists |
+| P3 | Edge case, cosmetic, minor annoyance |
+
+---
+
+## Workflow
+
+### Phase 1 — Triage & Understand
+
+Before touching code, gather:
+- What is the symptom? (error message, wrong behavior, crash)
+- What is the expected behavior?
+- How to reproduce? (steps, conditions, environment)
+- What changed recently? (git log, deployment, dependency update)
+- What is the severity and impact scope?
+
+If critical information is missing → ask before proceeding.
+
+---
+
+### Phase 2 — Reproduce the Issue
+
+1. Write a failing test or script that triggers the bug
+2. Confirm the bug is consistently reproducible
+3. For intermittent bugs → identify timing, data, or environment conditions
+4. Document the exact reproduction steps
+
+> Rule: **Never skip reproduction.** A fix without a repro is a guess.
+
+---
+
+### Phase 3 — Localize the Problem
+
+1. Read the stack trace top-down, following frames inside project code
+2. Use logs, breakpoints, or `git blame` / `git bisect` to narrow scope
+3. Identify the exact file and line where the failure originates
+4. Trace the data flow that leads to the failure
+
+---
+
+### Phase 4 — Root Cause Analysis
+
+Answer: *Why does this happen? What condition triggers it?*
+
+Common root cause categories:
+- Logic error (wrong condition, wrong operator)
+- Off-by-one or boundary case
+- Null / undefined / missing data
+- Async timing or race condition
+- Type mismatch
+- Stale state or stale closure
+- Config or environment issue
+- API contract change
+- Dependency version change
+
+Use 5 Whys: keep asking "why" until you reach the actual cause, not just the symptom.
+
+---
+
+### Phase 5 — Apply the Fix
+
+Rules:
+- Fix the root cause, not the symptom
+- Smallest possible change that fully resolves the issue
+- Keep existing code style, naming, and conventions
+- Handle related edge cases to prevent similar bugs
+- Remove all debug code, console.logs, and temporary patches
+- Do not change public APIs unless strictly required
+
+---
+
+### Phase 6 — Verify the Result
+
+- [ ] The failing test from Phase 2 now passes
+- [ ] Run the related test suite — no new failures
+- [ ] Run lint and type-check — clean
+- [ ] Manually reproduce the original steps — bug is gone
+- [ ] No regressions in adjacent functionality
+
+---
+
+### Phase 7 — Report & Prevent
+
+Summarize and propose prevention:
+- What was the root cause?
+- What was changed and why?
+- Are there similar patterns elsewhere in the codebase?
+- Should a test be added to prevent regression?
+
+---
+
+## Decision Tree
+
+```
+Is the bug reproducible?
+  ├── No  → Isolate timing, data, environment conditions first
+  └── Yes → Is the root cause known?
+              ├── No  → Run Phase 3-4 (localize + analyze)
+              └── Yes → Apply minimal fix → verify → report
+```
+
+```
+Is the fix risky (touches shared code / public API)?
+  ├── Yes → Confirm scope with user before applying
+  └── No  → Apply fix
+```
+
+---
+
+## Output Format
+
+```
+🐛 Bug Report
+─────────────────────────────────────────────────
+Symptom:     [What broke + how to reproduce]
+Root cause:  [Exact file:line — why it happens]
+Severity:    [P0 / P1 / P2 / P3]
+
+🔧 Fix Applied
+─────────────────────────────────────────────────
+Changed:     [File(s) modified]
+Change:      [What was changed and why it's minimal]
+
+✅ Verification
+─────────────────────────────────────────────────
+Tests:       [Test name / command — PASSED]
+Lint/Types:  [Clean / warnings noted]
+Manual:      [Reproduced original steps — bug gone]
+Regression:  [No new failures]
+
+🛡️ Prevention
+─────────────────────────────────────────────────
+Test added:  [Yes / No — reason]
+Similar areas to check: [file or pattern to review]
+```
+
+---
+
+## Validation Checklist
+
+- [ ] Bug was reproduced before fixing
+- [ ] Root cause identified at exact file:line with explanation
+- [ ] Fix is minimal — only changes what's needed
+- [ ] Failing test now passes
+- [ ] Related tests and lint/type-check clean
+- [ ] No debug code left behind
+- [ ] Side effects documented
+- [ ] Prevention strategy noted
+
+---
+
+## Examples
+
+See `examples/` folder.
+
+---
+
+
+
+# Frontend Debugger
+
+> **Language rule:**
+> Use English for: code, identifiers, file names, architecture terms, technical decisions.
+> Use the user's language for: explanations, questions, summaries, and feedback.
+> The user may write in any language — detect and match it automatically.
+
+---
+
+## Trigger
+
+Activate this skill when:
+- User reports a UI-specific bug ("screen is blank", "button doesn't work")
+- React throws a Hydration Error (`Text content did not match. Server: "A" Client: "B"`)
+- React throws an infinite loop error (`Too many re-renders`)
+- CSS styling is broken or overflowing unexpectedly
+- Form validation behaves incorrectly
+
+**Note:** For backend or general logic bugs, use `bug-fix`. For performance issues, use `frontend-performance`.
+
+---
+
+## Scope
+
+- ✅ Diagnose and fix React hydration mismatches (Next.js / SSR)
+- ✅ Fix infinite loops in `useEffect` and missing dependencies
+- ✅ Resolve state staleness (stale closures in async functions or hooks)
+- ✅ Fix CSS layout issues (Flexbox/Grid blowouts, z-index stacking context)
+- ✅ Provide a targeted, minimal fix that doesn't break other UI elements
+
+---
+
+## Non-goals
+
+- ❌ Do NOT rewrite the entire component to fix a small CSS bug
+- ❌ Do NOT disable hydration checks (`suppressHydrationWarning`) unless absolutely necessary and justified
+- ❌ Do NOT apply quick-fixes (like `// @ts-ignore` or wrapping everything in `setTimeout`) without understanding the root cause
+
+---
+
+## Workflow
+
+### Phase 1 — Reproduction & Isolation
+
+1. Identify the exact error message or visual symptom.
+2. Isolate the component causing the issue.
+3. Determine the environment (SSR, CSR, mobile, specific browser).
+
+---
+
+### Phase 2 — Common Issue Diagnosis
+
+**Hydration Errors (Next.js/SSR):**
+- Cause: Rendering `window`, `localStorage`, or random data (e.g., `Math.random()`, Dates) on the first pass.
+- Fix: Move client-only rendering inside a `useEffect` (isMounted pattern) or use dynamic imports with `ssr: false`.
+
+**Too many re-renders:**
+- Cause: Updating state directly in the render body, or inside a `useEffect` without proper dependencies.
+- Fix: Move state updates into event handlers, or fix `useEffect` dependencies.
+
+**Stale Closures:**
+- Cause: A `useEffect` or `useCallback` is using old state because it's missing from the dependency array.
+- Fix: Add dependencies, use refs (`useRef`) for mutable values, or use functional state updates (`setState(prev => prev + 1)`).
+
+**CSS Z-Index/Stacking Issues:**
+- Cause: Missing `position: relative/absolute` on parent, or a new stacking context was created.
+- Fix: Inspect parent elements, adjust `z-index`, or use Portals for modals.
+
+---
+
+### Phase 3 — Fix Application
+
+Apply the minimal fix required to resolve the issue while preserving surrounding logic and styles.
+
+---
+
+## Decision Tree
+
+```
+Is it a Hydration Error?
+  ├── Yes → Is it caused by client-side APIs (window/localStorage)?
+  │           ├── Yes → Use `useEffect` to delay rendering until mounted
+  │           └── No  → Check for mismatched HTML tags (e.g., <p> inside <p>)
+  └── No  → Proceed to next check
+
+Is it an infinite loop?
+  ├── Yes → Check `useEffect` dependencies. Are objects/arrays re-created every render?
+  │           ├── Yes → Memoize them (`useMemo`) or move outside component
+  │           └── No  → Ensure `setState` isn't called unconditionally in render
+  └── No  → Proceed
+```
+
+---
+
+## Output Format
+
+```
+🪲 Frontend Debug Report
+─────────────────────────────────────────────────
+Symptom:    [Description of the bug]
+Root Cause: [Explanation of why it failed, e.g., Stale Closure in useEffect]
+
+🔧 Fix Applied:
+  [Brief description of the code change]
+
+✅ Verification:
+  - Error no longer throws
+  - UI renders correctly
+
+⚠️ Notes:
+  [Any side effects or things to watch out for]
+```
+
+---
+
+## Validation Checklist
+
+- [ ] Root cause clearly identified (not just patched)
+- [ ] Fix is minimal and targeted
+- [ ] No Hydration warnings remain
+- [ ] Component doesn't infinitely loop
+- [ ] No regression on related UI

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

@@ -0,0 +1,206 @@
+---
+name: qk-context-loader
+purpose: Load ngữ cảnh thực tại (file, folder, logic) liên quan trực tiếp đến task.
+mode_supported: [standard]
+input: [Workflow task]
+output: [Context summaries, loaded files]
+workflow: [1. Quét file bị ảnh hưởng -> 2. Gom nhóm ngữ cảnh -> 3. Handoff]
+allowed_tools: [grep_search, read_file, list_dir]
+handoff_to: [qk-policy-engine]
+---
+
+# 🛠️ qk-context-loader - Quy Trình Vận Hành Chuẩn (SOP)
+
+> **Mô tả:** Load ngữ cảnh thực tại (file, folder, logic) liên quan trực tiếp đến task.
+
+## 🎯 1. Mục Tiêu (Goal)
+- Hoàn thành thành công tác vụ được giao liên quan đến nhiệm vụ của skill.
+- Đảm bảo chất lượng mã nguồn và tính nhất quán của hệ thống.
+
+## 🔄 2. Chuỗi Hành Động (Chain of Thought / SOP)
+*(Bắt buộc AI phải suy nghĩ và làm theo đúng thứ tự)*
+1. **Phân tích (Analyze):** Thu thập ngữ cảnh và hiểu rõ yêu cầu đầu vào.
+2. **Lên kế hoạch (Plan):** Xác định các bước cần thay đổi/tạo mới dựa trên bộ luật (rules).
+3. **Thực thi (Execute):** Tiến hành sửa đổi mã nguồn hoặc tạo tài liệu.
+4. **Xác thực (Verify):** Đảm bảo đầu ra đáp ứng đúng yêu cầu và không vi phạm quy định.
+
+## 🛡️ 3. Ràng Buộc & Quy Tắc (Constraints)
+- CẤM bỏ qua việc kiểm tra `qk-engineering-standard` trước khi viết code.
+- Mọi quyết định kỹ thuật phải dựa trên nội dung tại phần Deep Knowledge (nếu có).
+
+## 🤝 4. Giao Thức Bàn Giao (Handoff Protocol)
+- Đích đến: `qk-policy-engine`
+- Nội dung bàn giao: Chuyển toàn bộ ngữ cảnh và kết quả đã thực thi cho bước tiếp theo.
+
+## 📚 5. Kiến Thức Chuyên Sâu (Deep Knowledge)
+
+*(Nền tảng kiến thức và quy tắc chi tiết kế thừa từ kỹ sư)*
+
+---
+
+
+
+# Context Manager
+
+> **Language rule:**
+> Use **English** for: file paths, architecture terms, module names, technical labels.
+> Use **the user's language** for: explanations, summaries, and questions.
+
+---
+
+## Trigger
+
+Activate this skill when:
+- Starting work on an unfamiliar or large codebase
+- About to read many files and need to prioritize
+- Context window is at risk of overflowing
+- User asks "where is X", "what does Y do", "how is this project structured"
+- Another skill (e.g. `project-audit`, `frontend-architecture`) needs project context first
+
+---
+
+## Scope
+
+- ✅ Identify which files are relevant to the current task
+- ✅ Summarize project architecture in structured format
+- ✅ Map folder structure to responsibilities
+- ✅ Track what has been read and what still needs reading
+- ✅ Flag context window risks
+- ✅ Maintain a working memory summary for multi-turn sessions
+
+---
+
+## Non-goals
+
+- ❌ Do NOT modify any files
+- ❌ Do NOT fix bugs
+- ❌ Do NOT make architectural decisions
+- ❌ Do NOT read every file blindly — be selective and efficient
+
+---
+
+## Workflow
+
+### Phase 1 — Project Discovery
+
+Read only top-level signals first:
+1. `package.json` / `pyproject.toml` / `Cargo.toml` → detect framework, language, scripts
+2. Root config files → `.env.example`, `tsconfig.json`, `vite.config.ts`, `next.config.js`
+3. Folder structure (1-2 levels deep) → identify key directories
+4. Entry points → `src/index.ts`, `app/`, `pages/`, `main.py`
+
+Produce: **Project Profile** (framework, language, key directories, architecture style)
+
+---
+
+### Phase 2 — Task-Scoped File Selection
+
+Given the current task, identify the minimum relevant set of files:
+
+```
+Task type → Files to read
+─────────────────────────────────────────────────────
+UI work         → components/, pages/, styles/, design system files
+API work        → services/, hooks/, api/, types/
+State work      → store/, context/, hooks/
+Bug fix         → files mentioned in error, related modules
+Architecture    → folder structure, key abstractions
+```
+
+Rules:
+- Read **entry points** before diving into details
+- Prefer **index files** as anchors
+- Skip `node_modules`, `dist`, `build`, `.git`
+- If uncertain which file → check imports, not the file itself
+
+---
+
+### Phase 3 — Architecture Summary
+
+Produce a concise summary:
+
+```
+Project:    [Name / repo]
+Framework:  [React 18 / Next.js 14 / Vue 3 / etc.]
+Language:   [TypeScript / JavaScript / Python]
+Structure:  [Feature-based / Layer-based / Domain-based]
+
+Key directories:
+  src/components/  → Shared UI components
+  src/features/    → Feature modules (collocated)
+  src/services/    → API and data services
+  src/hooks/       → Custom React hooks
+  src/types/       → TypeScript interfaces
+
+State:       [Zustand / Redux / React Query / Pinia]
+HTTP client: [axios instance at src/lib/axios.ts]
+Auth:        [JWT stored in httpOnly cookie]
+```
+
+---
+
+### Phase 4 — Working Memory Maintenance
+
+During multi-turn sessions:
+- Track which files have been read (avoid re-reading)
+- Track decisions made (e.g. "we decided to use feature-based structure")
+- Flag when context is approaching limits
+- Offer to summarize and compress if needed
+
+---
+
+## Decision Tree
+
+```
+Is this a new project / first time seeing this codebase?
+  ├── Yes → Run full Phase 1 + Phase 2 + Phase 3
+  └── No  → Has something changed since last context load?
+              ├── Yes → Re-run Phase 2 for affected area
+              └── No  → Use cached architecture summary
+```
+
+```
+Is context window at risk?
+  ├── Yes → Summarize what's been read, drop low-relevance files
+  └── No  → Continue loading relevant files
+```
+
+---
+
+## Output Format
+
+```
+🗂️  Project Context Loaded
+
+Framework:  [framework]
+Language:   [language]
+Structure:  [style]
+
+Relevant files for this task:
+  📄 [path/to/file.ts]     — [why it's relevant]
+  📄 [path/to/file.ts]     — [why it's relevant]
+
+Architecture summary:
+  [2-4 lines describing how this codebase is organized]
+
+⚠️  Context notes:
+  [Any risks, unknowns, or files that couldn't be read]
+
+✅ Ready. Proceeding with: [next skill or action]
+```
+
+---
+
+## Validation Checklist
+
+- [ ] Framework and language correctly identified
+- [ ] Only task-relevant files selected (no noise)
+- [ ] Architecture summary is accurate and concise
+- [ ] Context window usage is reasonable
+- [ ] Working memory updated for this session
+
+---
+
+## Examples
+
+See `examples/` folder.

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

@@ -0,0 +1,135 @@
+---
+name: qk-data-lifecycle
+purpose: Quản lý Schema, Migration, Repository, Query Tuning.
+mode_supported: [enterprise]
+input: [Data requirement]
+output: [Schema, Migration files]
+workflow: [1. Schema -> 2. Migration -> 3. Repository -> 4. Index]
+allowed_tools: [write_to_file, run_command]
+handoff_to: [qk-validation-gate]
+---
+
+# 🛠️ qk-data-lifecycle - Quy Trình Vận Hành Chuẩn (SOP)
+
+> **Mô tả:** Quản lý Schema, Migration, Repository, Query Tuning.
+
+## 🎯 1. Mục Tiêu (Goal)
+- Hoàn thành thành công tác vụ được giao liên quan đến nhiệm vụ của skill.
+- Đảm bảo chất lượng mã nguồn và tính nhất quán của hệ thống.
+
+## 🔄 2. Chuỗi Hành Động (Chain of Thought / SOP)
+*(Bắt buộc AI phải suy nghĩ và làm theo đúng thứ tự)*
+1. **Phân tích (Analyze):** Thu thập ngữ cảnh và hiểu rõ yêu cầu đầu vào.
+2. **Lên kế hoạch (Plan):** Xác định các bước cần thay đổi/tạo mới dựa trên bộ luật (rules).
+3. **Thực thi (Execute):** Tiến hành sửa đổi mã nguồn hoặc tạo tài liệu.
+4. **Xác thực (Verify):** Đảm bảo đầu ra đáp ứng đúng yêu cầu và không vi phạm quy định.
+
+## 🛡️ 3. Ràng Buộc & Quy Tắc (Constraints)
+- CẤM bỏ qua việc kiểm tra `qk-engineering-standard` trước khi viết code.
+- Mọi quyết định kỹ thuật phải dựa trên nội dung tại phần Deep Knowledge (nếu có).
+
+## 🤝 4. Giao Thức Bàn Giao (Handoff Protocol)
+- Đích đến: `qk-validation-gate`
+- Nội dung bàn giao: Chuyển toàn bộ ngữ cảnh và kết quả đã thực thi cho bước tiếp theo.
+
+## 📚 5. Kiến Thức Chuyên Sâu (Deep Knowledge)
+
+*(Nền tảng kiến thức và quy tắc chi tiết kế thừa từ kỹ sư)*
+
+---
+
+
+
+# Database Engineer
+
+> **Language rule:**
+> Use English for: code, identifiers, file names, architecture terms, technical decisions.
+> Use the user's language for: explanations, questions, summaries, and feedback.
+> The user may write in any language — detect and match it automatically.
+
+---
+
+## Trigger
+
+Activate this skill when:
+- User says "create a new table", "add a column", "design the schema"
+- Writing complex data retrieval logic (joins, aggregations)
+- A query is running slowly and needs optimization (indexing)
+- Running or generating database migrations
+
+---
+
+## Scope
+
+- ✅ **Schema Design:** Model tables, relations (1:1, 1:N, N:M), and constraints (Unique, FK).
+- ✅ **ORM Integration:** Generate code for Prisma, Drizzle, TypeORM, Sequelize, or Mongoose.
+- ✅ **Migrations:** Generate SQL or ORM migration files safely.
+- ✅ **Query Optimization:** Prevent N+1 queries, add indexes, use efficient aggregations.
+
+---
+
+## Non-goals
+
+- ❌ Do NOT execute destructive migrations (DROP TABLE) on production environments without extreme warnings and approval.
+- ❌ Do NOT mix raw SQL into ORM logic unless necessary for performance.
+
+---
+
+## Workflow
+
+### Phase 1 — Schema Design
+
+Understand the business entities and relations.
+- Identify primary keys (UUID vs Auto-increment ID).
+- Identify foreign keys and cascade rules (`ON DELETE CASCADE`).
+- Ensure proper normalization (usually 3NF) or denormalization (if NoSQL).
+
+### Phase 2 — ORM / Migration Generation
+
+Map the design to the project's tool:
+- **Prisma:** Update `schema.prisma`.
+- **Drizzle:** Update `schema.ts`.
+- **Raw SQL:** Write `V1__create_table.sql`.
+
+### Phase 3 — Query Implementation
+
+Write the data access methods (Repository pattern or direct ORM calls).
+- Avoid fetching `SELECT *` if only 2 columns are needed.
+- Batch queries or use joins to prevent N+1 issues.
+
+---
+
+## Decision Tree
+
+```
+Is the project using an ORM?
+  ├── Prisma  → Modify `schema.prisma`, use `prisma.entity.findMany()`
+  ├── Drizzle → Modify schema TS files, use Drizzle query builder
+  └── No      → Write raw SQL or use query builder (Knex)
+
+Does the schema change drop data or alter existing columns?
+  ├── Yes → Flag as High Risk. Provide rollback strategy. Ask for approval.
+  └── No  → Standard migration (e.g., adding a nullable column).
+```
+
+---
+
+## Output Format
+
+```
+🗄️ Database Engineering Report
+─────────────────────────────────────────────────
+Action:     [Schema Update / Query Optimization]
+Tooling:    [Prisma / Raw SQL / etc.]
+
+Changes:
+  ✅ Added model: `User` (1:N with `Post`)
+  ✅ Added index on `User.email`
+  ✅ Generated query: `getUserWithPosts`
+
+⚠️ Risk Assessment:
+  [Low / High — e.g., "Safe addition, no data loss"]
+
+🔗 Next Steps:
+  Run `npx prisma migrate dev` to apply these changes locally.
+```