pi-skill-search 0.1.0

package/skills/vetc-analyze-codebase/SKILL.md

@@ -0,0 +1,118 @@
+---
+name: vetc-analyze-codebase
+description: PROACTIVELY activate khi mới vào project, cần bản đồ kiến trúc, hoặc trước khi thiết kế API. Scan codebase → codebase-spec.md + data-model.md. Chạy 1 lần per project.
+---
+
+# VETC Analyze Codebase
+
+Tạo "bản đồ kiến trúc machine-readable" của toàn bộ VETC project — để các skill khác (vetc-analyze-ba, vetc-api-design, vetc-java-patterns) bám theo khi implement.
+
+## When to Activate
+
+- Vào project VETC mới lần đầu
+- Trước khi chạy `vetc-analyze-ba` (Phase 4 yêu cầu có codebase-spec.md)
+- Trước khi thiết kế API mới hoặc refactor kiến trúc lớn
+- Khi muốn có bản đồ codebase để AI không đoán mò về patterns, packages, conventions
+
+## Do NOT Activate When
+
+- Chỉ cần sửa 1 file đơn giản, không cần hiểu toàn bộ kiến trúc
+- Requirement đã cụ thể và rõ ràng, không cần codebase analysis
+- Chỉ fix bug cụ thể (dùng `vetc-runbook` hoặc `vetc-build-resolver`)
+
+## Output Files
+
+- `docs/architecture/codebase-spec.md` — Kiến trúc + conventions + modules + APIs
+- `docs/architecture/data-model.md` — 5 Mermaid diagrams
+- `docs/architecture/project-knowledge.md` — Entity registry, pattern catalog, lessons learned (optional, enhance over time)
+
+## Workflow (7 Phases)
+
+### Phase 1 — LOAD-SPEC
+Nếu `docs/architecture/codebase-spec.md` đã tồn tại → đọc và merge (incremental). Tôn trọng sections đã đánh dấu completed.
+
+### Phase 2 — COLLECT
+```bash
+# Tìm project config
+Glob("**/pom.xml", "**/build.gradle", "**/application*.yml")
+
+# Tìm Java classes
+Grep("@RestController", src/main/java/) → danh sách controllers
+Grep("@Service",        src/main/java/) → danh sách services
+Grep("@Repository",     src/main/java/) → danh sách repositories
+Grep("@Entity",         src/main/java/) → danh sách entities
+Grep("@ControllerAdvice", src/main/java/) → exception handlers
+```
+
+### Phase 3 — INFER-ARCH
+Từ kết quả collect, suy luận:
+- `LAYERED` nếu có `controller/ + service/ + repository/` (flat packages)
+- `HEXAGONAL` nếu có `application/ + domain/ + infrastructure/`
+- Conventions: naming suffix, REST base path, response wrapper, injection style
+
+#### 3.1 INFER-SECURITY
+Detect auth pattern chi tiết:
+```
+Grep("SecurityFilterChain|WebSecurityConfigurerAdapter", src/) → filter chain class
+Grep("@PreAuthorize|@Secured|@RolesAllowed", src/) → method-level auth
+Grep("x-api-key|X-API-KEY|apiKey", src/) → API key auth
+Grep("jwt|JWT|Bearer", src/) → JWT auth
+Grep("OAuth2|oauth2", src/) → OAuth2 auth
+```
+
+### Phase 4 — INFER-MODULES & APIS
+Đọc từng controller → group theo base path → tạo module list:
+| Module | Base Path | Controllers | APIs count |
+
+Với mỗi API: method, path, summary, request_dto, response_dto, auth_required
+
+### Phase 5 — INFER-DATA-MODEL
+```bash
+Grep("@Entity", src/main/java/) → phân loại theo package:
+  entities/         → primary_datasource (Oracle)
+  secondsource.*    → secondary_datasource
+  tertiarysource.*  → tertiary_datasource
+
+### Phase 6 — INFER-BUSINESS-CONTEXTS
+Từ modules → tạo business contexts: tên, mô tả, modules liên quan, capabilities (use case)
+
+### Phase 7 — VALIDATE & PERSIST
+
+#### 7.1 Validation
+Trước khi ghi output, cross-check:
+- Declared vs used dependencies: flag deps trong pom.xml mà không có import nào dùng
+- Commented-out code: flag `@KafkaListener`, `@Entity`, `@Scheduled` bị comment → không tính active
+- Empty stubs: flag interface/class không có implementation
+- Entity/sequence naming: verify UPPER_SNAKE_CASE tables, AUTOID PK, allocationSize=1
+
+#### 7.2 Persist
+Ghi 2 files output theo template chuẩn.
+
+### Phase 8 — KNOWLEDGE EXTRACTION (Optional, enhance over time)
+
+Tạo `docs/architecture/project-knowledge.md` — persistent knowledge base:
+
+```markdown
+# Project Knowledge: {Project Name}
+
+## Entity Registry
+| Entity | Table | Key Fields | Business Domain |
+|--------|-------|------------|-----------------|
+| Wallet | WALLET | userId, balance, status | E-Wallet |
+| Transaction | WALLET_TRANSACTION | walletId, amount, type | E-Wallet |
+| ... | | | |
+
+## Pattern Catalog
+| Pattern | Where Used | Notes |
+|---------|-----------|-------|
+| ResultResp<T> wrapper | All controllers | Standard response format |
+| CustomizeException | All services | Error handling with code |
+| ... | | |
+
+## VETC Domain Terms
+| Term | Meaning | Domain |
+|------|---------|--------|
+| Bút toán | Journal entry | ACS |
+| Đối soát | Reconciliation | Reconcile |
+
+

package/skills/vetc-api-design/SKILL.md

@@ -0,0 +1,103 @@
+---
+name: vetc-api-design
+description: PROACTIVELY activate khi có Structured Spec cần thiết kế DB + API. Dùng sau vetc-spec-driven, trước vetc-planner. Sinh ERD, Entity skeleton, API contract, data flow.
+---
+
+# VETC API Design
+
+Từ Spec → ERD + API Contract → sẵn sàng để implement.
+
+## When to Activate
+
+- Có Structured Spec (từ vetc-spec-driven), cần thiết kế DB + API
+- Thiết kế schema mới cho tính năng
+- Cần API contract để team FE/BE đồng bộ trước khi code
+- Design review trước implementation
+
+## Do NOT Activate When
+
+- Chỉ fix bug trong API đã tồn tại, không thay đổi contract
+- Chỉ làm UI/frontend work, không liên quan API design
+- Spec đã finalized và API contract đã được sign-off
+
+## Workflow
+
+1. Đọc spec (Section 7 Data Model, Section 8 API Sketch)
+2. Thiết kế ERD → Entity skeletons
+3. Thiết kế API contract chi tiết
+4. Vẽ data flow diagram
+
+## ERD Format
+
+```
+## ERD: [Feature Name]
+
+TABLE: TABLE_NAME
+| Column       | Type             | Nullable | Notes                    |
+|-------------|------------------|----------|--------------------------|
+| AUTOID      | NUMBER           | NO       | PK, sequence             |
+| CUSTOMER_ID | NUMBER           | NO       | FK → CUSTOMER_INFOS      |
+| AMOUNT      | NUMBER(20,4)     | NO       | monetary value           |
+| STATUS      | NVARCHAR2(20)    | NO       | PENDING/ACTIVE/FAILED    |
+| DESCRIPTION | NVARCHAR2(500)   | YES      | Vietnamese text          |
+| CREATED_DATE| DATE             | NO       | audit                    |
+
+Status transitions: PENDING → ACTIVE → FAILED/CANCELLED
+
+Relationships:
+
+## API Contract Format
+
+```yaml
+# Feature: [Name]
+# Base: /api/v{N}/{domain}
+
+POST /endpoint:
+  auth: Bearer JWT (Keycloak)
+  request:
+    customerId: Long, required
+    amount: BigDecimal, required, > 0
+    description: String, optional, max 500 chars
+  responses:
+    200: { code: "00", data: { id: Long, status: "PENDING" } }
+    400: { code: "VALIDATION_ERROR", field: "amount", message: "..." }
+    404: { code: "CUSTOMER_NOT_FOUND" }
+    422: { code: "INSUFFICIENT_BALANCE" }
+    429: { code: "RATE_LIMIT_EXCEEDED" }
+  notes:
+
+## Data Flow Diagram
+
+```
+[React Client]
+    → POST /api/v1/wallet/transfer
+    → [WalletTransferController] validate (JWT + @Valid)
+    → [WalletTransferService]
+        ↓ check balance [WalletRepository]
+        ↓ debit source [WalletRepository] @Transactional
+        ↓ credit target [WalletRepository]
+        ↓ create journal entry [ACS REST Client] (external)
+        ↓ save transaction [TransactionRepository]
+        ↓ publish event [RabbitMQ] "TransferCompleted" (async)
+    → [WalletTransferController] → ResultResp.success(result)
+```
+
+## Design Checklist
+
+- [ ] Tất cả FK đã được xác định
+- [ ] Status transition diagram (nếu có state machine)
+- [ ] Index cho query phổ biến
+- [ ] Backward compatibility với API version hiện tại
+- [ ] Idempotency key nếu endpoint có thể retry
+- [ ] Rate limiting cho sensitive endpoints (OTP, transfer)
+- [ ] External dependencies và failure mode
+
+## References
+
+- API design chuẩn: `../../shared/api-design.md`
+- Architecture profiles: `../../shared/architecture-profiles.md`
+- Java patterns: `../../shared/java-spring-boot.md`
+
+## After Design
+
+

package/skills/vetc-brainstorming/SKILL.md

@@ -0,0 +1,116 @@
+---
+name: vetc-brainstorming
+description: PROACTIVELY activate khi user cần khám phá ý tưởng trước khi spec — open-ended exploration, trade-off analysis, viable options, không phải clarification. Pre-spec phase. Dùng TRƯỚC vetc-spec-driven hoặc vetc-deep-interview.
+---
+
+# VETC Brainstorming — Pre-Spec Exploration
+
+Khám phá không gian giải pháp trước khi commit vào spec. Generate options, explore trade-offs, find hidden opportunities. Inspired by superpowers `brainstorming` skill.
+
+## When to Activate
+
+- User muốn "explore ý tưởng", "cho tôi vài options", "có cách khác không?"
+- Problem chưa đủ định hình để spec — cần explore solution space
+- Trade-off analysis giữa nhiều approaches khả thi
+- Pre-feasibility: "có khả thi không?", "ballpark effort?"
+- Stakeholder hỏi "nên làm gì tiếp theo?" (roadmap decision)
+- Trước cả `vetc-deep-interview` khi requirement chưa form
+
+## Do NOT Activate When
+
+- User đã có requirement rõ → dùng `vetc-spec-driven` hoặc `vetc-deep-interview`
+- Đang trong implementation phase → skill này làm mất focus
+- Chỉ cần 1 answer cụ thể → trả lời trực tiếp, không brainstorm
+- Bug fix / debugging → dùng `vetc-systematic-debugging`
+- Review feedback đã rõ → dùng `vetc-receiving-review`
+
+## Core Pattern: Divergent → Convergent
+
+```
+[Problem statement]
+       ↓
+DIVERGENT (expand)
+  - Generate 5-8 options (fair, not straw-man)
+  - Consider: dùng existing, build new, buy, hybrid, punt
+  - Include unusual options (AI-assist, low-tech fallback, manual)
+       ↓
+ANALYZE (understand)
+  - Each option: effort, risk, strategic fit, user impact
+  - Surface hidden tradeoffs
+  - Find unasked questions
+       ↓
+
+## Workflow
+
+### Step 1 — Frame the Problem
+
+Không hỏi requirement — hỏi motivation (from GSD Dream Extraction):
+
+- "Điều gì thúc đẩy câu hỏi này?" (motivation)
+- "Thành công trông như thế nào?" (outcome)
+- "Cái gì đang block user hiện tại?" (pain)
+
+Output: 1 paragraph problem statement.
+
+### Step 2 — Divergent Thinking (Generate Options)
+
+Aim for **5-8 options**. Types to cover:
+
+| Option Type | Example |
+|-------------|---------|
+| **Do nothing** | Keep status quo, measure actual pain |
+| **Existing tool** | Use Spring Actuator for health check instead of custom |
+| **Build minimal** | MVP version covering 60% cases |
+| **Build full** | Complete version covering 95% cases |
+| **Buy / Integrate** | Third-party OTP service (Twilio) vs self-hosted |
+| **Hybrid** | Self-host core, third-party for edge cases |
+| **AI-assisted** | Let LLM handle classification/routing |
+| **Defer / Punt** | Wait for v2, ship without this |
+| **Simplify requirement** | Challenge: do we really need X, or can we drop it? |
+
+### Step 3 — Analyze Each Option
+
+Per option, surface:
+
+| Dimension | Questions |
+|-----------|-----------|
+| **Effort** | Dev hours? Testing hours? Migration cost? |
+| **Risk** | What could go wrong? Probability × Impact |
+| **User impact** | Does user notice? Is change positive? |
+| **Strategic fit** | Align with VETC Ewallet vision? Fintech compliance? |
+| **Reversibility** | Can we back out? Cost of reversal? |
+| **Dependencies** | Blocks on other teams? External systems? |
+| **Hidden cost** | Operational overhead? Support burden? Training? |
+
+Output matrix:
+
+### Step 4 — Convergent Thinking (Narrow Down)
+
+Apply **VETC-DR** (Drivers + Recommendation):
+
+**Drivers (top 3)** - what matters most for THIS decision:
+1. {Driver 1, e.g. compliance deadline}
+2. {Driver 2, e.g. engineering bandwidth}
+3. {Driver 3, e.g. user experience quality}
+
+**Recommend top 2-3** options with explicit rationale:
+
+```markdown
+## Recommended: Twilio Integration
+
+**Why**: Addresses compliance deadline (Driver 1), minimal eng bandwidth (Driver 2), faster OTP delivery improves UX (Driver 3).
+
+**Trade-offs acknowledged**:
+- Vendor lock-in (mitigated: abstract through OtpProvider interface)
+- Monthly cost ~$500/month (acceptable within ops budget)
+
+## Runner-up: Hybrid
+
+**Why**: Better long-term architecture, graceful degradation.
+**Why not top choice**: Effort XL exceeds compliance deadline. Can retrofit later.
+
+## Explicitly Rejected: Self-hosted OTP
+
+**Why rejected**: Effort L + new infra risk + distraction from core features. LOW strategic fit.
+
+

package/skills/vetc-change-proposal/SKILL.md

@@ -0,0 +1,111 @@
+---
+name: vetc-change-proposal
+description: PROACTIVELY activate khi spec đã APPROVED nhưng cần thay đổi — compliance update, new edge case, scope adjustment. Tạo delta spec (OpenSpec-style) thay vì sửa trực tiếp. Lifecycle DRAFT → PROPOSED → APPROVED → APPLIED → ARCHIVED.
+---
+
+# VETC Change Proposal — OpenSpec-Style Delta Management
+
+Quản lý spec changes có cấu trúc. Spec đã APPROVED KHÔNG được sửa trực tiếp — tạo change proposal với impact analysis, review, và archive.
+
+## When to Activate
+
+- Spec status = APPROVED hoặc IMPLEMENTING, cần thay đổi
+- User: "sửa spec", "thêm requirement", "loại requirement X"
+- Compliance update (SBV, NHNN, internal policy)
+- New edge case discovered during implementation
+- External system contract changed (Bank GW update, ACS API v2)
+- Feature scope adjustment mid-development
+
+## Do NOT Activate When
+
+- Spec ở DRAFT status → sửa spec trực tiếp
+- Bug fix không thay đổi requirements → không cần change proposal
+- Typo / formatting fix → sửa trực tiếp
+- Implementation detail clarification (không thay behavior) → sửa plan.md, không cần change proposal
+
+## Core Pattern: Delta Spec Lifecycle
+
+```
+[Spec APPROVED]
+       ↓
+  CREATE PROPOSAL (DRAFT)
+       ↓
+  IMPACT ANALYSIS
+       ↓
+  REVIEW (architect + critic)
+       ↓
+  [PROPOSAL APPROVED]
+       ↓
+  IMPLEMENT CHANGES (vetc-ralph)
+       ↓
+
+## Workflow
+
+### Step 1 — Classify Change
+
+| Change Type | When | Example |
+|-------------|------|---------|
+| **ADDED** | New requirement/section | "Add OTP verification for > 500K" |
+| **MODIFIED** | Change existing requirement | "Change timeout from 5min to 15min" |
+| **REMOVED** | Drop requirement | "Remove QR refresh button (moved to separate feature)" |
+
+**Impact level** quyết định rigor:
+
+| Level | Tasks affected | Rigor |
+|-------|----------------|-------|
+| LOW | 0-1 task, no rework | Quick proposal, inline review |
+| MEDIUM | 2-5 tasks, some rework | Full proposal + architect review |
+| HIGH | 5+ tasks, significant rework | Full proposal + Planner+Architect+Critic consensus |
+| CRITICAL | Fundamental scope shift | Pause implementation, re-spec with `vetc-deep-interview` |
+
+### Step 2 — Create Proposal Directory
+
+```
+specs/{NNN}-{slug}/changes/
+├── 001-add-otp-verification/
+│   ├── proposal.md       ← From templates/change-proposal-template.md
+│   └── delta.md          ← Section-by-section diff
+├── 002-adjust-timeout/
+│   ├── proposal.md
+│   └── delta.md
+└── archive.md            ← Applied changes summary
+```
+
+Numbering: sequential (001, 002, ...).
+
+### Step 3 — Fill Proposal Template
+
+Use `templates/change-proposal-template.md`. Required sections:
+
+1. **Why** — Motivation, external driver (compliance, user feedback, tech debt)
+2. **What Changed** — Section-level changes table (Before / After)
+3. **Impact Analysis** — Tasks affected, data model changes, API contract, security, performance
+4. **Risk Assessment** — Probability × Impact table with mitigation
+5. **Acceptance Criteria** — How to verify change is correctly applied
+6. **Review Sign-offs** — Spec Author / Planner / Architect / Critic / Security / PO
+
+### Step 4 — Create Delta.md
+
+Section-by-section diff format:
+
+```markdown
+# Delta: {Change Title}
+
+## §4 Happy Path — MODIFIED
+
+**Before**:
+1. Customer scans QR
+2. System validates QR
+3. Customer confirms amount
+4. Transaction processed
+
+**After**:
+1. Customer scans QR
+2. System validates QR
+3. Customer confirms amount
+4. **(NEW)** If amount > 500K: system requests OTP
+5. **(NEW)** Customer enters OTP (60s timeout)
+6. **(NEW)** System validates OTP
+
+## §5 Edge Cases — ADDED
+

package/skills/vetc-cicd/SKILL.md

@@ -0,0 +1,113 @@
+---
+name: vetc-cicd
+description: PROACTIVELY activate khi cần setup CI/CD, tạo build pipeline, thêm GitHub Actions, hoặc troubleshoot build/deploy. Maven/Gradle/npm build commands, coverage, Docker.
+---
+
+# VETC CI/CD — Build, Test, Deploy
+
+Commands và templates cho CI/CD workflows trong VETC project.
+
+## When to Activate
+
+- Cần build/test/deploy commands
+- Tạo hoặc update GitHub Actions workflow
+- Chạy coverage report
+- Debug CI pipeline failure
+- Setup Docker build
+
+## Do NOT Activate When
+
+- Viết business logic / application code (dùng `vetc-java-patterns` hoặc `vetc-frontend-patterns`)
+- Chỉ cần code review (dùng reviewer agents)
+- CI/CD đã configured và đang hoạt động ổn định, không cần thay đổi
+
+## Build Commands
+
+### Maven (Backend)
+
+```bash
+# Compile only (fast check)
+mvn clean compile -q
+
+# Compile + tests
+mvn clean test -q
+
+# Full package (jar/war)
+mvn clean package -DskipTests -q
+
+# Multi-module — specific module
+mvn clean compile -pl wallet-service -am -q
+
+# With profile
+mvn clean package -Pprod -DskipTests -q
+
+# Check dependencies
+mvn dependency:tree | grep <dependency>
+```
+
+### npm (Frontend)
+
+```bash
+# Type check
+npx tsc --noEmit
+
+# Build production
+npm run build
+
+# Test with coverage
+npm test -- --coverage
+
+# Lint
+npx eslint src/ --ext .ts,.tsx
+
+# Bundle analysis
+npx vite-bundle-visualizer
+```
+
+## GitHub Actions Templates
+
+### Backend CI
+
+```yaml
+name: Backend CI
+on:
+  push:
+    paths: ['backend/**']
+  pull_request:
+    paths: ['backend/**']
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-java@v4
+
+### Frontend CI
+
+```yaml
+name: Frontend CI
+on:
+  push:
+    paths: ['frontend/**']
+  pull_request:
+    paths: ['frontend/**']
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-node@v4
+
+## Coverage Commands
+
+```bash
+# Backend — JaCoCo report
+mvn verify -pl <module> -q
+open <module>/target/site/jacoco/index.html
+
+# Backend — check threshold
+mvn verify -Djacoco.threshold=0.80
+
+# Frontend — Jest coverage
+npm test -- --coverage --watchAll=false
+```

package/skills/vetc-continuous-learning/SKILL.md

@@ -0,0 +1,115 @@
+---
+name: vetc-continuous-learning
+description: PROACTIVELY extract reusable patterns từ sessions — khi phát hiện recurring bug, project-specific workaround, hoặc debugging technique hiệu quả. Instinct-based learning v2 với confidence scoring, project scoping, và automatic promotion.
+---
+
+# VETC Continuous Learning v2
+
+Instinct-based learning system: observe → detect → create/update → evolve. Biến session knowledge thành atomic "instincts" với confidence scoring.
+
+## When to Activate
+
+- Phát hiện recurring bug pattern (xuất hiện 2+ lần)
+- Tìm workaround cho framework issue
+- Discover VETC domain-specific pattern đáng nhớ
+- Debugging technique hiệu quả cần reuse
+- Configuration pattern phức tạp đã giải quyết
+- Instinct observer hook phát hiện pattern tự động
+- **HARNESS_BACKLOG entries** có status `accepted` → candidate for skill creation
+
+## Do NOT Activate When
+
+- Bug chỉ xuất hiện 1 lần, chưa recurrent → dùng `vetc-systematic-debugging`
+- Pattern chỉ áp dụng cho 1 project cụ thể, không reusable
+- Đã có skill chính thức cover pattern đó → extend skill, không tạo instinct
+- Đang implement code, chưa ở phase review/reflection
+
+## V2 Architecture: Instincts
+
+### What is an Instinct?
+
+Instinct là atomic learned behavior — nhỏ hơn skill, lớn hơn rule. Mỗi instinct có:
+
+```
+{
+  id: "inst_1713288000000_abc123",
+  pattern: "Oracle NVARCHAR2 cần @Nationalized annotation",
+  action: "Thêm @Nationalized cho Oracle NVARCHAR2 columns",
+  category: "code",          // code | debug | workflow | domain
+  scope: "project",           // project | global
+  projectId: "abc123",        // hash của git remote URL
+  confidence: 0.7,            // 0.3-0.9
+  source: "edit-observation", // session | edit-observation | bash-observation | manual
+  uses: 3,                    // times applied
+
+### Confidence Scoring
+
+| Score | Meaning | Trigger |
+|-------|---------|---------|
+| 0.3 | Tentative — observed once, unverified | First observation |
+| 0.5 | Noted — observed, seems useful | 2 observations |
+| 0.7 | Reliable — used successfully 3+ times | 3+ uses with ≥60% hit rate |
+| 0.9 | Core — consistently useful, promoted to global | 5+ uses with ≥80% hit rate |
+
+### Scopes
+
+- **project**: Instinct chỉ apply cho current project (stored in `~/.vetc/instincts/project-{id}.json`)
+- **global**: Instinct apply cho tất cả projects (stored in `~/.vetc/instincts/global.json`)
+
+### Promotion Pipeline
+
+```
+Observation → project instinct (0.3) → use → confidence grows → promote to global (0.7+)
+```
+
+Instinct tự động promote khi:
+- Confidence ≥ 0.7
+- Uses ≥ 5
+- Hit rate ≥ 70%
+
+## Learning Sources
+
+### 1. Hook Observation (Automatic)
+
+`instinct-observer.js` hook tự động detect patterns từ Edit/Write/Bash tool use:
+- Edit patterns: @Nationalized, @Transactional, validation annotations, parameterized queries
+- Write patterns: new Controller/Service/Repository creation
+- Bash patterns: dependency investigation, git grep, curl testing
+
+Rate limit: max 5 new instincts per session (avoid noise).
+
+### 2. Manual Extraction (`/vetc-learn`)
+
+User-triggered pattern extraction:
+1. Scan conversation cho patterns
+2. Classify theo 4 types
+3. Tìm unique insight
+4. Create instinct với higher confidence (0.5)
+
+### 3. Session End Review
+
+Khi session kết thúc, review instincts created:
+- Show summary: new instincts, reinforced instincts
+- Suggest promotions if applicable
+
+## Instinct Categories
+
+| Category | Trigger | Example |
+|----------|---------|---------|
+| **code** | Implementation pattern | Oracle NVARCHAR2 cần @Nationalized |
+| **debug** | Troubleshooting technique | Feign 503 → check ACS health endpoint |
+| **workflow** | Process/procedure | Journal entry: validate → reserve → create → confirm |
+| **domain** | Business logic insight | Smart OTP có 2 phases với khác session type |
+| **security** | Security pattern | Sensitive URL params cần encode |
+
+## Commands
+
+### Check Status
+
+```
+/instinct-status
+```
+Show: total instincts, by category, avg confidence, top 5 instincts.
+
+### Evolve Instincts
+```