@ojokesusu/lintasai 1.1.2

package/templates/feature-flags-advanced.md

@@ -0,0 +1,171 @@
+# Feature Flag Pattern (ADVANCED — Post-Launch Only)
+
+> ⚠️ **JANGAN PAKAI FILE INI DI EARLY-STAGE PROJECT (progress <50% / belum launch ke user nyata).**
+>
+> Default workflow tim = **staging-only** (Vercel Preview per PR). Lihat `CLAUDE_TEAM_GUIDE.md` section 7b (Risk Level Decision Tree).
+>
+> File ini cuma dipakai **post-launch** kalau project sudah punya user aktif dan butuh:
+> - Kill switch instant untuk fitur kritis (mis. payment toggle saat Black Friday)
+> - A/B test gradual rollout (10% → 50% → 100%)
+> - Per-user targeting (beta tester subset)
+
+---
+
+## Filosofi: Kapan UPGRADE dari Staging-Only ke Feature Flag?
+
+Project pertama kali = simpler is better. Tambah complexity HANYA kalau ada **pain point konkret**, bukan karena "best practice di tutorial".
+
+### Sinyal kamu butuh feature flag (post-launch):
+
+| Sinyal | Contoh |
+|---|---|
+| Rollback `git revert` sudah TIDAK cukup cepat | Bug payment terdeteksi jam 11 malam, butuh kill switch <30 detik (bukan 5 menit redeploy) |
+| Butuh test fitur ke subset user dulu | Beta launch ke 100 user terpilih sebelum public |
+| Butuh A/B test resmi | "Versi A vs Versi B landing page, monitor conversion 2 minggu" |
+| Butuh deploy kode tapi launch terpisah | Code deploy sekarang, launch announcement minggu depan |
+
+Kalau **tidak ada** sinyal di atas → **STAY di staging-only**. Feature flag tanpa pain point = premature optimization.
+
+---
+
+## Implementasi: Env Var Vercel
+
+Simple feature flag pakai env var Vercel (no library tambahan):
+
+```ts
+// lib/flags.ts
+export const flags = {
+  newDashboard: process.env.NEXT_PUBLIC_FF_NEW_DASHBOARD === 'true',
+  betaPayment: process.env.FF_BETA_PAYMENT === 'true', // server-only
+}
+
+// Pakai di Server Component
+import { flags } from '@/lib/flags'
+
+export default function Page() {
+  if (flags.newDashboard) return <NewDashboard />
+  return <OldDashboard />
+}
+```
+
+### Naming Convention
+
+Semua flag wajib pakai prefix `NEXT_PUBLIC_FF_<AREA>_<NAMA>`:
+- `FF` = Feature Flag
+- `<AREA>` = domain (mis. `BILLING`, `INBOX`, `AUTH`)
+- `<NAMA>` = nama fitur snake-uppercase
+
+Contoh: `NEXT_PUBLIC_FF_BILLING_NEW_PRICING`, `NEXT_PUBLIC_FF_INBOX_V2_FILTER`.
+
+**Wajib di-comment di kode** dengan tanggal lahir + target hapus:
+
+```tsx
+// FLAG: NEXT_PUBLIC_FF_INBOX_V2_FILTER
+// Created: 2026-06-15
+// Target removal: 2026-07-15 (setelah 100% rollout 2 minggu stabil)
+const showNewFilter = process.env.NEXT_PUBLIC_FF_INBOX_V2_FILTER === 'true';
+```
+
+---
+
+## Gradual Rollout
+
+1. Set `NEXT_PUBLIC_FF_NEW_DASHBOARD=false` di Production → fitur tersembunyi.
+2. Set `NEXT_PUBLIC_FF_NEW_DASHBOARD=true` di Preview → tim QA test.
+3. Saat siap launch → ubah Production env var ke `true` → redeploy 2-5 menit.
+4. Setelah 1-2 minggu stabil → hapus flag, code path lama dihapus (lihat **Cleanup Ritual**).
+
+> Prefix `NEXT_PUBLIC_` = ter-expose ke browser. Untuk flag rahasia (mis. feature internal), pakai env var tanpa prefix → cek di Server Component/Action only.
+
+---
+
+## Per-User Flag (Canary Rollout)
+
+Kalau butuh rollout ke 10% user random (bukan all-or-nothing), pakai hash deterministik dari userId. Jangan pakai `Math.random()` (user bakal kelap-kelip).
+
+```ts
+import { cookies } from 'next/headers'
+import { createHash } from 'crypto'
+
+export function isNewDashboardEnabled() {
+  const userId = cookies().get('userId')?.value ?? ''
+  if (!userId) return false
+
+  // sha256 = distribusi merata + stabil per userId
+  const hash = createHash('sha256').update(userId).digest('hex')
+  const bucket = parseInt(hash.slice(0, 4), 16) % 100
+  return bucket < 10 // 10% user
+}
+```
+
+> **Kenapa sha256?** Charcode sum (`'abc'` → 97+98+99 = 294) gampang collision. Sha256 merata & tahan collision.
+
+---
+
+## Cleanup Ritual (Cegah Flag Debt)
+
+Flag yang sudah "selesai" tapi dibiarkan = **flag debt** (kode penuh `if (flag) {}` zombie).
+
+Aturan:
+1. **1-2 minggu setelah flag = `true` stabil di prod tanpa bug**:
+   - Bikin PR baru: hapus pemanggilan env var dari kode (else branch lama dihapus).
+   - Hapus env var dari Vercel dashboard (Settings → Environment Variables → Delete) di semua environment.
+2. **Quarterly ritual**: review flag yang `Target removal`-nya lewat. Grep `NEXT_PUBLIC_FF_` di kode + cocokkan dengan Vercel dashboard.
+
+> Rule of thumb: **kalau flag sudah lebih lama dari fitur yang dilindunginya, itu flag debt.**
+
+---
+
+## Testing Flag
+
+Tiap flag wajib minimal 2 unit test (case ON + case OFF):
+
+```ts
+import { vi, describe, it, expect, afterEach } from 'vitest'
+import { isNewDashboardEnabled } from '@/lib/flags'
+
+describe('flag NEXT_PUBLIC_FF_NEW_DASHBOARD', () => {
+  afterEach(() => vi.unstubAllEnvs())
+
+  it('flag ON → render path baru', () => {
+    vi.stubEnv('NEXT_PUBLIC_FF_NEW_DASHBOARD', 'true')
+    expect(isNewDashboardEnabled()).toBe(true)
+  })
+
+  it('flag OFF → render path lama', () => {
+    vi.stubEnv('NEXT_PUBLIC_FF_NEW_DASHBOARD', 'false')
+    expect(isNewDashboardEnabled()).toBe(false)
+  })
+
+  it('flag undefined → default OFF (fail-safe)', () => {
+    vi.stubEnv('NEXT_PUBLIC_FF_NEW_DASHBOARD', '')
+    expect(isNewDashboardEnabled()).toBe(false)
+  })
+})
+```
+
+---
+
+## Trade-off Penting (Sebelum Pakai Flag)
+
+| Aspek | Implikasi |
+|---|---|
+| **NEXT_PUBLIC_ vs server-only** | Keduanya butuh redeploy Vercel saat flip (~2-5 menit). Tidak instant. |
+| **Staff access** | Staff tanpa akses Vercel TIDAK bisa toggle flag. Flag = owner-only operation. |
+| **Code complexity** | Kode jadi bercabang (`if/else`). Susah review, susah test full coverage. |
+| **Maintenance** | Wajib cleanup flag yang sudah stabil (else jadi flag debt). |
+
+Kalau butuh **instant toggle (sub-detik) tanpa redeploy** → migrasi ke **DB-backed flag** (Prisma `FeatureFlag` table + Server Action dengan cache TTL pendek). Tapi itu kompleksitas extra lagi — pertimbangkan dengan matang.
+
+---
+
+## Aktivasi Workflow Feature Flag (Saat Siap Post-Launch)
+
+Saat project sudah launch dan kamu mau pakai feature flag default:
+
+1. Update `CLAUDE_TEAM_GUIDE.md` section 7b: tambah sub-section "Decision Tree Branch + Flag" (lihat git history kit, sebelum stripped).
+2. Update `PROMPT_LIBRARY.md` Prompt 11: tambah field `[Flag?]` di template task.
+3. Update `AGENTS.md` proyek: tambah link ke file ini di section "Workflow & Komunikasi Task".
+4. Setup channel Slack/Discord untuk announce tiap flag flip (transparency).
+
+Atau: PR ke kit `lintasAI` untuk re-enable flag workflow di default kit (kalau team udah scale 20+).

package/templates/github/CODEOWNERS.template

@@ -0,0 +1,61 @@
+# .github/CODEOWNERS.template
+# Template GitHub CODEOWNERS
+#
+# Cara pakai:
+# 1. Copy file ini jadi `.github/CODEOWNERS` (tanpa `.template`).
+# 2. Ganti SEMUA placeholder `<...>` dengan GitHub username aktual (huruf kecil, prefix `@`).
+# 3. Commit. GitHub otomatis request review ke owner saat ada PR yang sentuh file terkait.
+#
+# Sintaks: <pola-path>  @user1 @user2
+# Pola lebih spesifik (di bawah) menang dari pola umum (di atas).
+# Dokumentasi resmi: https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners
+
+# ── Default owner (fallback untuk semua file yang tidak match rule lain) ──
+*                       @<owner-username>
+
+# ── Area sensitif: auth & payment wajib reviewer senior ──
+/src/auth/              @<senior-dev>
+/src/auth/**            @<senior-dev>
+/src/payment/           @<senior-dev>
+/src/payment/**         @<senior-dev>
+
+# ── Dokumentasi: owner + tech writer ──
+/docs/                  @<owner-username> @<tech-writer>
+/docs/**                @<owner-username> @<tech-writer>
+
+# ── Infra CI/CD & meta repo: cuma owner ──
+/.github/               @<owner-username>
+/.github/**             @<owner-username>
+
+# ── Konfigurasi env & secret-ish (kalau ada) ──
+/.env.example           @<owner-username> @<senior-dev>
+
+# ──────────────────────────────────────────────────────────────────
+# CONTOH POLA UNTUK SPLIT 2-TIER (Frontend / Backend / Shared)
+# ──────────────────────────────────────────────────────────────────
+# Pakai pola ini kalau proyek pakai monorepo dengan apps/ folder
+# (atau adaptasi pattern path-nya kalau pakai split-repo terpisah).
+#
+# Konvensi 2-tier:
+# - Frontend Staff (4 orang): akses Frontend area + Shared (CRUD via API, no DDL)
+# - Backend Staff  (2 orang): akses semua area (full DB control + DDL)
+# - Owner: fallback reviewer untuk semua area
+
+# Frontend area — Frontend + Backend + owner boleh review
+/apps/frontend/         @<frontend1> @<frontend2> @<frontend3> @<frontend4> @<backend1> @<backend2> @<owner-username>
+/apps/frontend/**       @<frontend1> @<frontend2> @<frontend3> @<frontend4> @<backend1> @<backend2> @<owner-username>
+
+# Backend area — Backend + owner saja (Frontend Staff dikecualikan)
+/apps/backend/          @<backend1> @<backend2> @<owner-username>
+/apps/backend/**        @<backend1> @<backend2> @<owner-username>
+
+# Shared area (types + zod schema) — semua staff + owner
+/apps/shared/           @<frontend1> @<frontend2> @<frontend3> @<frontend4> @<backend1> @<backend2> @<owner-username>
+/apps/shared/**         @<frontend1> @<frontend2> @<frontend3> @<frontend4> @<backend1> @<backend2> @<owner-username>
+
+# CATATAN:
+# - Username harus member repo dengan minimal write access supaya bisa dipanggil sebagai reviewer.
+# - Hapus baris yang tidak relevan untuk proyekmu.
+# - Jangan commit file ini dalam keadaan masih ada placeholder `<...>` — CI akan menolak.
+# - Kalau pakai split-repo (3 repo terpisah, bukan monorepo): salin pola di atas ke CODEOWNERS
+#   repo masing-masing, tanpa prefix `/apps/<area>/` — cukup pakai `*` per repo.

package/templates/github/GENERATE_TYPES_SCRIPT.md

@@ -0,0 +1,77 @@
+# Auto Types Generation Setup
+
+## Backend repo: package.json scripts
+
+```json
+{
+  "scripts": {
+    "generate:types": "prisma generate && tsup --config tsup.shared.config.ts",
+    "build:shared": "tsup --config tsup.shared.config.ts",
+    "publish:shared:dry": "cd shared-dist && npm publish --dry-run",
+    "publish:shared": "cd shared-dist && npm publish"
+  }
+}
+```
+
+## tsup.shared.config.ts
+
+```typescript
+import { defineConfig } from 'tsup'
+import pkg from './shared-package.json'
+
+export default defineConfig({
+  entry: ['src/shared/index.ts'],
+  format: ['esm', 'cjs'],
+  dts: true,
+  outDir: 'shared-dist',
+  clean: true,
+  external: ['@prisma/client'],
+  onSuccess: 'cp shared-package.json shared-dist/package.json',
+})
+```
+
+## shared-package.json (template untuk @<project>/shared)
+
+```json
+{
+  "name": "@<project>/shared",
+  "version": "1.0.0",
+  "main": "./index.js",
+  "module": "./index.mjs",
+  "types": "./index.d.ts",
+  "publishConfig": {
+    "registry": "https://npm.pkg.github.com"
+  },
+  "repository": {
+    "type": "git",
+    "url": "https://github.com/<owner>/<project>-backend.git"
+  },
+  "peerDependencies": {
+    "zod": "^3.0.0"
+  }
+}
+```
+
+## src/shared/index.ts (manual maintained)
+
+```typescript
+// Re-export selective Prisma types (yang aman di-share)
+export type { User, Order, Platform } from '@prisma/client'
+
+// Re-export domain types
+export * from './schemas/user'
+export * from './schemas/tracking'
+
+// Common API wrappers
+export type ApiResponse<T> = 
+  | { data: T; meta?: Record<string, any> }
+  | { error: string; code?: string }
+```
+
+## Verify
+
+```bash
+npm run generate:types
+ls shared-dist/
+# Should output: index.js, index.mjs, index.d.ts, package.json
+```

package/templates/github/PUBLISH_SHARED_WORKFLOW.yml

@@ -0,0 +1,52 @@
+name: Publish @<project>/shared
+
+on:
+  push:
+    branches: [main]
+    paths:
+      - 'prisma/schema.prisma'
+      - 'src/shared/**'
+      - 'package.json'
+  workflow_dispatch:
+
+jobs:
+  publish:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+      packages: write
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+      - uses: actions/setup-node@v4
+        with:
+          node-version: '20'
+          registry-url: 'https://npm.pkg.github.com'
+          scope: '@<project>'
+      - run: npm ci
+      - name: Generate types
+        run: npm run generate:types
+      - name: Bump version
+        run: |
+          cd shared-dist
+          npm version patch -m 'chore(shared): bump version [skip ci]'
+      - name: Publish to GitHub Packages
+        env:
+          NODE_AUTH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        run: |
+          cd shared-dist
+          npm publish
+      - name: Notify Discord
+        if: env.DISCORD_WEBHOOK_DEPS != ''
+        env:
+          DISCORD_WEBHOOK_DEPS: ${{ secrets.DISCORD_WEBHOOK_DEPS }}
+        run: |
+          VERSION=$(node -p "require('./shared-dist/package.json').version")
+          MESSAGE=$(printf '{"content":"🔔 **@<project>/shared v%s published**\\nFrontend tim: PR Renovate akan masuk dalam 24 jam, atau manual \`npm install @<project>/shared@latest\` untuk segera dapat update.\\nChangelog: https://github.com/<owner>/<project>-backend/commits/main"}' "$VERSION")
+          curl -X POST -H 'Content-Type: application/json' -d "$MESSAGE" "$DISCORD_WEBHOOK_DEPS"
+      - name: Push version commit
+        run: |
+          git config user.name 'github-actions[bot]'
+          git config user.email 'github-actions[bot]@users.noreply.github.com'
+          git push

package/templates/github/RECEIVE_BACKEND_UPDATE.yml

@@ -0,0 +1,106 @@
+name: Receive @<project>/shared update (Real-time)
+
+on:
+  repository_dispatch:
+    types: [shared-package-published]
+
+jobs:
+  update:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+      pull-requests: write
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - uses: actions/setup-node@v4
+        with:
+          node-version: '20'
+          registry-url: 'https://npm.pkg.github.com'
+          scope: '@<project>'
+
+      - name: Install new shared version
+        env:
+          NODE_AUTH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        run: |
+          npm install @<project>/shared@${{ github.event.client_payload.version }}
+
+      - name: Check if breaking change
+        id: breaking
+        run: |
+          IS_BREAKING="${{ github.event.client_payload.is_breaking }}"
+          if [ "$IS_BREAKING" = "true" ]; then
+            echo "is_breaking=true" >> $GITHUB_OUTPUT
+            echo "WARNING: This is a BREAKING change. Manual review required."
+          else
+            echo "is_breaking=false" >> $GITHUB_OUTPUT
+          fi
+
+      - name: Create PR
+        id: cpr
+        uses: peter-evans/create-pull-request@v6
+        with:
+          token: ${{ secrets.GITHUB_TOKEN }}
+          commit-message: "chore(deps): bump @<project>/shared to v${{ github.event.client_payload.version }}"
+          title: "${{ steps.breaking.outputs.is_breaking == 'true' && '⚠️ BREAKING' || '🔄 Auto' }}-update @<project>/shared to v${{ github.event.client_payload.version }}"
+          body: |
+            **Triggered by**: Backend publish (real-time)
+            **Version**: v${{ github.event.client_payload.version }}
+            **Breaking**: ${{ github.event.client_payload.is_breaking }}
+            **Backend commit**: [`${{ github.event.client_payload.commit }}`](${{ github.event.client_payload.changelog_url }})
+
+            ## Backend Commit Message
+            \`\`\`
+            ${{ github.event.client_payload.commit_message }}
+            \`\`\`
+
+            ## Action Required
+
+            **Untuk Frontend Staff**:
+            1. Pull branch ini di local
+            2. Test halaman yang affected (kalau yakin breaking change)
+            3. Approve + merge kalau OK
+
+            **Untuk Owner (if BREAKING)**:
+            - JANGAN auto-merge
+            - Review backend commit dulu
+            - Test di staging
+            - Plan rollback kalau perlu
+
+            ## Auto-Generated
+            Latency: 3-5 menit dari backend publish.
+            Workflow: `.github/workflows/receive-shared-update.yml`
+          branch: auto/shared-update-${{ github.event.client_payload.version }}
+          delete-branch: true
+          labels: |
+            auto-update
+            shared-types
+            ${{ steps.breaking.outputs.is_breaking == 'true' && 'breaking-change' || '' }}
+
+      - name: Notify Discord (optional)
+        if: env.DISCORD_WEBHOOK_FRONTEND != ''
+        env:
+          DISCORD_WEBHOOK_FRONTEND: ${{ secrets.DISCORD_WEBHOOK_FRONTEND }}
+        run: |
+          if [ "${{ steps.breaking.outputs.is_breaking }}" = "true" ]; then
+            EMOJI=":warning:"
+            TITLE="BREAKING change PR ready"
+          else
+            EMOJI=":arrows_counterclockwise:"
+            TITLE="Auto-update PR ready"
+          fi
+          curl -X POST -H 'Content-Type: application/json' \\
+            -d "{\"content\":\"$EMOJI **$TITLE**\\n@<project>/shared v${{ github.event.client_payload.version }}\\nPR: ${{ steps.cpr.outputs.pull-request-url }}\"}" \\
+            "$DISCORD_WEBHOOK_FRONTEND"
+
+# Setup:
+# Save sebagai .github/workflows/receive-shared-update.yml di FRONTEND repo (akses-frontend).
+# Default secrets (no setup needed):
+#   - GITHUB_TOKEN (auto-provided by GitHub Actions)
+# Optional secret untuk Discord:
+#   - DISCORD_WEBHOOK_FRONTEND
+#
+# Replace placeholder:
+# - <project> → project name (e.g. akses)

package/templates/github/RENOVATE_FRONTEND.json

@@ -0,0 +1,28 @@
+{
+  "$schema": "https://docs.renovatebot.com/renovate-schema.json",
+  "extends": ["config:recommended"],
+  "schedule": ["after 9am every weekday"],
+  "timezone": "Asia/Jakarta",
+  "labels": ["renovate"],
+  "packageRules": [
+    {
+      "matchPackageNames": ["@<project>/shared"],
+      "schedule": ["at any time"],
+      "automerge": false,
+      "groupName": "shared package",
+      "reviewers": ["<owner-username>"],
+      "labels": ["auto-update", "shared-types"],
+      "minimumReleaseAge": "5 minutes"
+    },
+    {
+      "matchDepTypes": ["devDependencies"],
+      "minimumReleaseAge": "7 days"
+    }
+  ],
+  "vulnerabilityAlerts": {
+    "enabled": true,
+    "labels": ["security"]
+  },
+  "rangeStrategy": "bump",
+  "rebaseWhen": "behind-base-branch"
+}

package/templates/github/TRIGGER_FRONTEND_UPDATE.yml

@@ -0,0 +1,29 @@
+# Append to .github/workflows/publish-shared.yml di akses-backend
+# Trigger frontend repo untuk auto-update setelah publish
+
+# Step ini ditambahkan SETELAH "Publish to GitHub Packages" + "Notify Discord"
+
+      - name: Trigger frontend repo update (real-time)
+        uses: peter-evans/repository-dispatch@v3
+        with:
+          token: ${{ secrets.FRONTEND_REPO_DISPATCH_TOKEN }}
+          repository: <owner>/<project>-frontend
+          event-type: shared-package-published
+          client-payload: |
+            {
+              "version": "${{ env.NEW_VERSION }}",
+              "commit": "${{ github.sha }}",
+              "commit_message": ${{ toJson(github.event.head_commit.message) }},
+              "changelog_url": "https://github.com/<owner>/<project>-backend/commits/main",
+              "is_breaking": "${{ contains(github.event.head_commit.message, 'BREAKING') }}"
+            }
+
+# Setup:
+# 1. Generate PAT di GitHub > Settings > Developer settings > Personal access tokens (classic)
+# 2. Scope: repo (full) + workflow
+# 3. Save as: FRONTEND_REPO_DISPATCH_TOKEN
+# 4. Tambah ke backend repo > Settings > Secrets > Actions
+#
+# Replace placeholder:
+# - <owner> → GitHub username/org (e.g. ojokesusu)
+# - <project> → project name (e.g. akses)

package/templates/github/pull_request_template.md

@@ -0,0 +1,44 @@
+<!--
+  .github/pull_request_template.md — template PR tim AI-first
+  Isi semua section di bawah. Yang tidak relevan: tulis "-" jangan dihapus.
+  Bahasa: Indonesia. Singkat, padat, konkret.
+-->
+
+## Ringkasan
+<!-- 1-3 kalimat: apa yang PR ini lakukan, dalam bahasa manusia. -->
+
+## Kenapa
+<!-- Link issue / task ID / keputusan. Contoh: Closes #123, ref TASK-456, diskusi di docs/decisions/2026-xx-xx.md -->
+
+## Apa yang berubah
+<!-- Bulleted list perubahan utama. Fokus ke "what", bukan baris kode. -->
+- 
+- 
+- 
+
+## Cara verifikasi
+<!-- Langkah konkret supaya reviewer (atau AI) bisa reproduce hasilnya. -->
+1. 
+2. 
+3. 
+
+## Risk + Rollback
+<!-- Risiko paling mungkin + cara balikin kalau ternyata bermasalah di produksi.
+     Tulis "-" kalau PR-nya pure docs/refactor tanpa risk. -->
+- Risk: 
+- Rollback: 
+
+## Checklist
+- [ ] Commit pakai **Conventional Commits** (`feat:`, `fix:`, `chore:`, `docs:`, dll.)
+- [ ] File `.md` terkait di `docs/` sudah diupdate (sesuai aturan AUTO-SYNC kit)
+- [ ] Edge case sudah dipikirkan (input kosong, null, error network, race)
+- [ ] Sudah manual test di **preview URL** / lokal (sertakan link kalau ada)
+- [ ] Kalau ada perubahan UI: **screenshot before/after** dilampirkan di bawah
+- [ ] Tidak ada secret / API key / data sensitif yang ke-commit
+- [ ] Reuse komponen yang sudah ada (cek `src/components/` & `docs/_PATTERNS.md`)
+
+## Screenshot (kalau UI berubah)
+<!-- Drag & drop gambar di sini. Hapus section ini kalau bukan perubahan UI. -->
+
+---
+<sub>Senior AI Reviewer akan otomatis posting review di PR ini. Tetap tunggu review manusia untuk perubahan kritis (auth, payment, migrasi DB).</sub>