vibes-plug 1.0.0 → 2.11.0

package/skills/state-management-expert/SKILL.md

@@ -1,272 +1,278 @@
----
-name: state-management-expert
-description: "Expert guide for modern client-side state management: Zustand, Jotai, Valtio, TanStack Store, Redux Toolkit, and server state patterns with TanStack Query / Panduan ahli untuk manajemen state client-side modern: Zustand, Jotai, Valtio, TanStack Store, Redux Toolkit, dan pola server state dengan TanStack Query."
+---
+name: state-management-expert
+description: "Expert guide for modern client-side state management: Zustand, Jotai, Valtio, TanStack Store, Redux Toolkit, and server state patterns with TanStack Query / Panduan ahli untuk manajemen state client-side modern: Zustand, Jotai, Valtio, TanStack Store, Redux Toolkit, dan pola server state dengan TanStack Query."
 author: "Roedy Rustam"
----
-
-# State Management Expert (Modern React Edition)
-
-[English](#english) | [Bahasa Indonesia](#bahasa-indonesia)
-
----
-
-<a name="english"></a>
-## English
-
-### Description
-Expert guide for selecting and implementing the right state management solution for React and Next.js applications. Covers **Zustand 5**, **Jotai 2**, **Valtio**, **TanStack Store**, and **Redux Toolkit 2**, with clear guidance on when to use each, proper separation of server state (TanStack Query) from client state, and advanced patterns like slices, persistence, and devtools integration.
-
-### Trigger Conditions
-- Choosing a state management library for a new React/Next.js project.
-- Refactoring prop drilling or complex Context API usage.
-- Implementing global UI state (modals, drawers, theme, auth session).
-- Managing complex form state across multiple steps.
-- Implementing undo/redo, optimistic updates, or derived state.
-- Migrating from Redux to a lighter alternative.
-
----
-
-### State Category Separation (Critical First Step)
-
-Before choosing a library, categorize your state:
-
-| Category | Description | Solution |
-|---|---|---|
-| **Server State** | Data from APIs, databases | TanStack Query / SWR |
-| **URL State** | Route params, search filters | `useSearchParams`, nuqs |
-| **Form State** | Input values, validation errors | React Hook Form + Zod |
-| **UI/Local State** | Modals, drawers, toggles | `useState` / `useReducer` |
-| **Global Client State** | Theme, auth, shopping cart | Zustand / Jotai |
-| **Cross-tab State** | Sync across browser tabs | Zustand + BroadcastChannel |
-
-**Rule**: Do NOT store server data in client state. Let TanStack Query own all async data.
-
----
-
-### Library Selection Guide
-
-| Criteria | Zustand 5 | Jotai 2 | Valtio | Redux Toolkit |
-|---|---|---|---|---|
-| **Mental Model** | Single store, actions | Atomic, bottom-up | Proxy-based, mutable | Flux, reducers |
-| **Bundle Size** | ~1KB | ~3KB | ~3KB | ~15KB+ |
-| **DevTools** | Redux DevTools | Jotai DevTools | Redux DevTools | Built-in |
-| **Async** | Manual or middleware | `atomWithQuery` | `snapshot` | `createAsyncThunk` |
-| **Best For** | General global state | Atomic derived state | Simple mutable state | Large teams, strict patterns |
-
-**Recommendation**: Use **Zustand** as the default. Use **Jotai** for fine-grained reactive atoms. Use **Redux Toolkit** only for large enterprise teams with strict conventions.
-
----
-
-### Zustand 5 — Best Practices
-
-#### Basic Store with TypeScript
-```typescript
-// stores/ui.store.ts
-import { create } from 'zustand';
-import { devtools, persist, subscribeWithSelector } from 'zustand/middleware';
-import { immer } from 'zustand/middleware/immer';
-
-interface UiState {
-  theme: 'light' | 'dark' | 'system';
-  sidebarOpen: boolean;
-  activeModal: string | null;
-  setTheme: (theme: UiState['theme']) => void;
-  toggleSidebar: () => void;
-  openModal: (modalId: string) => void;
-  closeModal: () => void;
-}
-
-export const useUiStore = create<UiState>()(
-  devtools(
-    persist(
-      subscribeWithSelector(
-        immer((set) => ({
-          theme: 'system',
-          sidebarOpen: true,
-          activeModal: null,
-          setTheme: (theme) => set((state) => { state.theme = theme; }),
-          toggleSidebar: () => set((state) => { state.sidebarOpen = !state.sidebarOpen; }),
-          openModal: (modalId) => set((state) => { state.activeModal = modalId; }),
-          closeModal: () => set((state) => { state.activeModal = null; }),
-        }))
-      ),
-      { name: 'ui-store', partialize: (s) => ({ theme: s.theme }) }
-    ),
-    { name: 'UiStore' }
-  )
-);
-```
-
-#### Slice Pattern for Large Stores
-```typescript
-// Pattern: separate slices, combine into one store
-import { StateCreator } from 'zustand';
-
-interface AuthSlice {
-  user: User | null;
-  isAuthenticated: boolean;
-  login: (user: User) => void;
-  logout: () => void;
-}
-
-interface CartSlice {
-  items: CartItem[];
-  addItem: (item: CartItem) => void;
-  removeItem: (id: string) => void;
-  total: () => number;
-}
-
-type AppStore = AuthSlice & CartSlice;
-
-const createAuthSlice: StateCreator<AppStore, [], [], AuthSlice> = (set) => ({
-  user: null,
-  isAuthenticated: false,
-  login: (user) => set({ user, isAuthenticated: true }),
-  logout: () => set({ user: null, isAuthenticated: false }),
-});
-
-const createCartSlice: StateCreator<AppStore, [], [], CartSlice> = (set, get) => ({
-  items: [],
-  addItem: (item) => set((s) => ({ items: [...s.items, item] })),
-  removeItem: (id) => set((s) => ({ items: s.items.filter((i) => i.id !== id) })),
-  total: () => get().items.reduce((sum, item) => sum + item.price * item.qty, 0),
-});
-
-export const useAppStore = create<AppStore>()(
-  devtools((...args) => ({
-    ...createAuthSlice(...args),
-    ...createCartSlice(...args),
-  }))
-);
-```
-
-#### Selective Subscriptions (Prevent Unnecessary Rerenders)
-```typescript
-// Only re-render when `theme` changes, not the entire store
-const theme = useUiStore((s) => s.theme);
-const isModalOpen = useUiStore((s) => s.activeModal === 'confirm-delete');
-
-// Subscribe outside React (side effects, non-component code)
-useUiStore.subscribe(
-  (s) => s.theme,
-  (theme) => document.documentElement.dataset.theme = theme,
-  { fireImmediately: true }
-);
-```
-
----
-
-### Jotai 2 — Atomic State Patterns
-
-```typescript
-// atoms/user.atoms.ts
-import { atom, loadable } from 'jotai';
-import { atomWithStorage, atomWithReset } from 'jotai/utils';
-
-// Primitive atom
-export const themeAtom = atomWithStorage<'light' | 'dark'>('theme', 'light');
-
-// Derived (read-only) atom
-export const isDarkAtom = atom((get) => get(themeAtom) === 'dark');
-
-// Async atom with loadable for Suspense-free usage
-export const userAtom = atom(async () => {
-  const res = await fetch('/api/me');
-  if (!res.ok) throw new Error('Failed to fetch user');
-  return res.json() as Promise<User>;
-});
-
-export const loadableUserAtom = loadable(userAtom);
-
-// In component:
-function UserWidget() {
-  const loadableUser = useAtomValue(loadableUserAtom);
-  if (loadableUser.state === 'loading') return <Spinner />;
-  if (loadableUser.state === 'hasError') return <Error />;
-  return <div>{loadableUser.data.name}</div>;
-}
-```
-
----
-
-### Redux Toolkit 2 — Modern Patterns
-
-```typescript
-// features/cart/cartSlice.ts
-import { createSlice, PayloadAction, createSelector } from '@reduxjs/toolkit';
-
-interface CartState {
-  items: CartItem[];
-  status: 'idle' | 'loading' | 'failed';
-}
-
-const cartSlice = createSlice({
-  name: 'cart',
-  initialState: { items: [], status: 'idle' } as CartState,
-  reducers: {
-    addItem(state, action: PayloadAction<CartItem>) {
-      state.items.push(action.payload); // Immer handles immutability
-    },
-    removeItem(state, action: PayloadAction<string>) {
-      state.items = state.items.filter((i) => i.id !== action.payload);
-    },
-  },
-});
-
-// Memoized selector
-export const selectCartTotal = createSelector(
-  (state: RootState) => state.cart.items,
-  (items) => items.reduce((sum, i) => sum + i.price * i.qty, 0)
-);
-
-export const { addItem, removeItem } = cartSlice.actions;
-export default cartSlice.reducer;
-```
-
----
-
-### Integration with Next.js App Router
-
-- **Server Components**: No client state. Fetch directly.
-- **Client Components**: Use Zustand/Jotai wrapped in providers.
-- **Hydration**: Initialize Zustand store from server-fetched data using `useHydrateAtoms` (Jotai) or a `HydrationBoundary` pattern.
-
-```typescript
-// providers/store-provider.tsx (App Router pattern)
-'use client';
-import { createStore, Provider } from 'jotai';
-import { useRef } from 'react';
-
-type Props = { children: React.ReactNode; initialUser?: User };
-
-export function StoreProvider({ children, initialUser }: Props) {
-  const store = useRef(createStore());
-  if (initialUser) store.current.set(userAtom, initialUser);
-  return <Provider store={store.current}>{children}</Provider>;
-}
-```
-
----
-
-<a name="bahasa-indonesia"></a>
-## Bahasa Indonesia
-
-### Deskripsi
-Panduan ahli untuk memilih dan mengimplementasikan solusi manajemen state yang tepat untuk aplikasi React dan Next.js. Mencakup **Zustand 5**, **Jotai 2**, **Valtio**, dan **Redux Toolkit 2**, dengan panduan pemilihan yang jelas, pemisahan server state (TanStack Query) dari client state, dan pola lanjutan seperti slices, persistensi, dan integrasi devtools.
-
-### Kondisi Pemicu
-- Memilih library state management untuk proyek React/Next.js baru.
-- Refaktor prop drilling atau penggunaan Context API yang rumit.
-- Mengimplementasikan global UI state (modal, drawer, tema, sesi auth).
-- Mengelola state form kompleks di beberapa langkah.
-- Mengimplementasikan undo/redo, optimistic update, atau derived state.
-- Migrasi dari Redux ke alternatif yang lebih ringan.
-
-### Prinsip Utama
-
-- **Pisahkan server state dari client state**: Server state (data dari API) dikelola TanStack Query. Client state (UI, preferensi) dikelola Zustand/Jotai.
-- **Gunakan Zustand sebagai default** untuk state global umum.
-- **Gunakan Jotai** untuk state atomik yang sangat granular dan reaktif.
-- **Hindari menyimpan data server di client state** — ini adalah sumber bug terbesar di aplikasi React.
-- **Selective subscription**: Selalu gunakan selector untuk menghindari re-render yang tidak perlu.
-- **DevTools**: Selalu integrasikan devtools di development untuk debugging yang efektif.
+---
+
+# State Management Expert (Modern React Edition)
+
+[English](#english) | [Bahasa Indonesia](#bahasa-indonesia)
+
+---
+
+<a name="english"></a>
+## English
+
+### Orchestration & Integration
+Connects and orchestrates with relevant domain skills like `brainstorming`, `zero-to-prod-orchestrator`, and `project-context-mapper` to ensure cohesive execution.
+
+### Description
+Expert guide for selecting and implementing the right state management solution for React and Next.js applications. Covers **Zustand 5**, **Jotai 2**, **Valtio**, **TanStack Store**, and **Redux Toolkit 2**, with clear guidance on when to use each, proper separation of server state (TanStack Query) from client state, and advanced patterns like slices, persistence, and devtools integration.
+
+### Trigger Conditions
+- Choosing a state management library for a new React/Next.js project.
+- Refactoring prop drilling or complex Context API usage.
+- Implementing global UI state (modals, drawers, theme, auth session).
+- Managing complex form state across multiple steps.
+- Implementing undo/redo, optimistic updates, or derived state.
+- Migrating from Redux to a lighter alternative.
+
+---
+
+### State Category Separation (Critical First Step)
+
+Before choosing a library, categorize your state:
+
+| Category | Description | Solution |
+|---|---|---|
+| **Server State** | Data from APIs, databases | TanStack Query / SWR |
+| **URL State** | Route params, search filters | `useSearchParams`, nuqs |
+| **Form State** | Input values, validation errors | React Hook Form + Zod |
+| **UI/Local State** | Modals, drawers, toggles | `useState` / `useReducer` |
+| **Global Client State** | Theme, auth, shopping cart | Zustand / Jotai |
+| **Cross-tab State** | Sync across browser tabs | Zustand + BroadcastChannel |
+
+**Rule**: Do NOT store server data in client state. Let TanStack Query own all async data.
+
+---
+
+### Library Selection Guide
+
+| Criteria | Zustand 5 | Jotai 2 | Valtio | Redux Toolkit |
+|---|---|---|---|---|
+| **Mental Model** | Single store, actions | Atomic, bottom-up | Proxy-based, mutable | Flux, reducers |
+| **Bundle Size** | ~1KB | ~3KB | ~3KB | ~15KB+ |
+| **DevTools** | Redux DevTools | Jotai DevTools | Redux DevTools | Built-in |
+| **Async** | Manual or middleware | `atomWithQuery` | `snapshot` | `createAsyncThunk` |
+| **Best For** | General global state | Atomic derived state | Simple mutable state | Large teams, strict patterns |
+
+**Recommendation**: Use **Zustand** as the default. Use **Jotai** for fine-grained reactive atoms. Use **Redux Toolkit** only for large enterprise teams with strict conventions.
+
+---
+
+### Zustand 5 — Best Practices
+
+#### Basic Store with TypeScript
+```typescript
+// stores/ui.store.ts
+import { create } from 'zustand';
+import { devtools, persist, subscribeWithSelector } from 'zustand/middleware';
+import { immer } from 'zustand/middleware/immer';
+
+interface UiState {
+  theme: 'light' | 'dark' | 'system';
+  sidebarOpen: boolean;
+  activeModal: string | null;
+  setTheme: (theme: UiState['theme']) => void;
+  toggleSidebar: () => void;
+  openModal: (modalId: string) => void;
+  closeModal: () => void;
+}
+
+export const useUiStore = create<UiState>()(
+  devtools(
+    persist(
+      subscribeWithSelector(
+        immer((set) => ({
+          theme: 'system',
+          sidebarOpen: true,
+          activeModal: null,
+          setTheme: (theme) => set((state) => { state.theme = theme; }),
+          toggleSidebar: () => set((state) => { state.sidebarOpen = !state.sidebarOpen; }),
+          openModal: (modalId) => set((state) => { state.activeModal = modalId; }),
+          closeModal: () => set((state) => { state.activeModal = null; }),
+        }))
+      ),
+      { name: 'ui-store', partialize: (s) => ({ theme: s.theme }) }
+    ),
+    { name: 'UiStore' }
+  )
+);
+```
+
+#### Slice Pattern for Large Stores
+```typescript
+// Pattern: separate slices, combine into one store
+import { StateCreator } from 'zustand';
+
+interface AuthSlice {
+  user: User | null;
+  isAuthenticated: boolean;
+  login: (user: User) => void;
+  logout: () => void;
+}
+
+interface CartSlice {
+  items: CartItem[];
+  addItem: (item: CartItem) => void;
+  removeItem: (id: string) => void;
+  total: () => number;
+}
+
+type AppStore = AuthSlice & CartSlice;
+
+const createAuthSlice: StateCreator<AppStore, [], [], AuthSlice> = (set) => ({
+  user: null,
+  isAuthenticated: false,
+  login: (user) => set({ user, isAuthenticated: true }),
+  logout: () => set({ user: null, isAuthenticated: false }),
+});
+
+const createCartSlice: StateCreator<AppStore, [], [], CartSlice> = (set, get) => ({
+  items: [],
+  addItem: (item) => set((s) => ({ items: [...s.items, item] })),
+  removeItem: (id) => set((s) => ({ items: s.items.filter((i) => i.id !== id) })),
+  total: () => get().items.reduce((sum, item) => sum + item.price * item.qty, 0),
+});
+
+export const useAppStore = create<AppStore>()(
+  devtools((...args) => ({
+    ...createAuthSlice(...args),
+    ...createCartSlice(...args),
+  }))
+);
+```
+
+#### Selective Subscriptions (Prevent Unnecessary Rerenders)
+```typescript
+// Only re-render when `theme` changes, not the entire store
+const theme = useUiStore((s) => s.theme);
+const isModalOpen = useUiStore((s) => s.activeModal === 'confirm-delete');
+
+// Subscribe outside React (side effects, non-component code)
+useUiStore.subscribe(
+  (s) => s.theme,
+  (theme) => document.documentElement.dataset.theme = theme,
+  { fireImmediately: true }
+);
+```
+
+---
+
+### Jotai 2 — Atomic State Patterns
+
+```typescript
+// atoms/user.atoms.ts
+import { atom, loadable } from 'jotai';
+import { atomWithStorage, atomWithReset } from 'jotai/utils';
+
+// Primitive atom
+export const themeAtom = atomWithStorage<'light' | 'dark'>('theme', 'light');
+
+// Derived (read-only) atom
+export const isDarkAtom = atom((get) => get(themeAtom) === 'dark');
+
+// Async atom with loadable for Suspense-free usage
+export const userAtom = atom(async () => {
+  const res = await fetch('/api/me');
+  if (!res.ok) throw new Error('Failed to fetch user');
+  return res.json() as Promise<User>;
+});
+
+export const loadableUserAtom = loadable(userAtom);
+
+// In component:
+function UserWidget() {
+  const loadableUser = useAtomValue(loadableUserAtom);
+  if (loadableUser.state === 'loading') return <Spinner />;
+  if (loadableUser.state === 'hasError') return <Error />;
+  return <div>{loadableUser.data.name}</div>;
+}
+```
+
+---
+
+### Redux Toolkit 2 — Modern Patterns
+
+```typescript
+// features/cart/cartSlice.ts
+import { createSlice, PayloadAction, createSelector } from '@reduxjs/toolkit';
+
+interface CartState {
+  items: CartItem[];
+  status: 'idle' | 'loading' | 'failed';
+}
+
+const cartSlice = createSlice({
+  name: 'cart',
+  initialState: { items: [], status: 'idle' } as CartState,
+  reducers: {
+    addItem(state, action: PayloadAction<CartItem>) {
+      state.items.push(action.payload); // Immer handles immutability
+    },
+    removeItem(state, action: PayloadAction<string>) {
+      state.items = state.items.filter((i) => i.id !== action.payload);
+    },
+  },
+});
+
+// Memoized selector
+export const selectCartTotal = createSelector(
+  (state: RootState) => state.cart.items,
+  (items) => items.reduce((sum, i) => sum + i.price * i.qty, 0)
+);
+
+export const { addItem, removeItem } = cartSlice.actions;
+export default cartSlice.reducer;
+```
+
+---
+
+### Integration with Next.js App Router
+
+- **Server Components**: No client state. Fetch directly.
+- **Client Components**: Use Zustand/Jotai wrapped in providers.
+- **Hydration**: Initialize Zustand store from server-fetched data using `useHydrateAtoms` (Jotai) or a `HydrationBoundary` pattern.
+
+```typescript
+// providers/store-provider.tsx (App Router pattern)
+'use client';
+import { createStore, Provider } from 'jotai';
+import { useRef } from 'react';
+
+type Props = { children: React.ReactNode; initialUser?: User };
+
+export function StoreProvider({ children, initialUser }: Props) {
+  const store = useRef(createStore());
+  if (initialUser) store.current.set(userAtom, initialUser);
+  return <Provider store={store.current}>{children}</Provider>;
+}
+```
+
+---
+
+<a name="bahasa-indonesia"></a>
+## Bahasa Indonesia
+
+### Integrasi Orkestrasi
+Terhubung dan mengorkestrasi skill domain yang relevan seperti `brainstorming`, `zero-to-prod-orchestrator`, dan `project-context-mapper` untuk memastikan eksekusi yang kohesif.
+
+### Deskripsi
+Panduan ahli untuk memilih dan mengimplementasikan solusi manajemen state yang tepat untuk aplikasi React dan Next.js. Mencakup **Zustand 5**, **Jotai 2**, **Valtio**, dan **Redux Toolkit 2**, dengan panduan pemilihan yang jelas, pemisahan server state (TanStack Query) dari client state, dan pola lanjutan seperti slices, persistensi, dan integrasi devtools.
+
+### Kondisi Pemicu
+- Memilih library state management untuk proyek React/Next.js baru.
+- Refaktor prop drilling atau penggunaan Context API yang rumit.
+- Mengimplementasikan global UI state (modal, drawer, tema, sesi auth).
+- Mengelola state form kompleks di beberapa langkah.
+- Mengimplementasikan undo/redo, optimistic update, atau derived state.
+- Migrasi dari Redux ke alternatif yang lebih ringan.
+
+### Prinsip Utama
+
+- **Pisahkan server state dari client state**: Server state (data dari API) dikelola TanStack Query. Client state (UI, preferensi) dikelola Zustand/Jotai.
+- **Gunakan Zustand sebagai default** untuk state global umum.
+- **Gunakan Jotai** untuk state atomik yang sangat granular dan reaktif.
+- **Hindari menyimpan data server di client state** — ini adalah sumber bug terbesar di aplikasi React.
+- **Selective subscription**: Selalu gunakan selector untuk menghindari re-render yang tidak perlu.
+- **DevTools**: Selalu integrasikan devtools di development untuk debugging yang efektif.

package/skills/supabase-migration/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: supabase-migration
 description: "A skill to create or apply a Supabase database migration / Kemampuan untuk membuat atau menerapkan migrasi database Supabase."
-author: "Roedy Rustam"
+author: "Roedy Rustam"
 ---
 
 # Supabase Migration Skill
@@ -26,6 +26,29 @@ When the user asks to create or apply a database migration for Supabase, follow
    - Run `npx supabase migration up` to test locally or use the remote MCP `apply_migration` if the user wants it applied remotely.
 4. **Final Step**: Confirm with the user that the migration successfully completed.
 
+### Implementation Checklist
+- [ ] Generate a new migration file: `npx supabase migration new [name]`
+- [ ] Write raw SQL in the generated migration file (DDL and DML).
+- [ ] Test the migration locally: `npx supabase db reset` or `npx supabase migration up`.
+- [ ] If using RLS, explicitly add policies to the new tables.
+- [ ] Commit the migration file to version control.
+
+### Example: Supabase Migration Command Flow
+```bash
+# 1. Create a new migration file
+npx supabase migration new create_users_table
+
+# 2. Write SQL to supabase/migrations/<timestamp>_create_users_table.sql
+# 3. Apply to local database
+npx supabase migration up
+
+# 4. Apply to remote production database
+npx supabase db push
+```
+
+## Orchestration & Integration
+- Integrates with: `supabase-security-expert`, `database-orm-expert`, `ci-cd-devops-architect`.
+
 ---
 
 <a name="bahasa-indonesia"></a>
@@ -43,3 +66,26 @@ Ketika pengguna meminta untuk membuat atau menerapkan migrasi database untuk Sup
    - Tulis skrip SQL ke file migrasi lokal yang terletak di `supabase/migrations/` menggunakan `write_to_file`. Gunakan timestamp standar atau perintah `supabase migration new` untuk mendapatkan nama file.
    - Jalankan `npx supabase migration up` untuk menguji secara lokal atau gunakan MCP remote `apply_migration` jika pengguna ingin menerapkannya secara remote.
 4. **Langkah Terakhir**: Konfirmasikan dengan pengguna bahwa migrasi telah berhasil diselesaikan.
+
+### Checklist Implementasi
+- [ ] Buat file migrasi baru: `npx supabase migration new [nama]`
+- [ ] Tulis SQL mentah di file migrasi yang dihasilkan (DDL dan DML).
+- [ ] Uji migrasi secara lokal: `npx supabase db reset` atau `npx supabase migration up`.
+- [ ] Jika menggunakan RLS, tambahkan kebijakan secara eksplisit ke tabel baru.
+- [ ] Commit file migrasi ke sistem kontrol versi.
+
+### Contoh: Alur Perintah Migrasi Supabase
+```bash
+# 1. Buat file migrasi baru
+npx supabase migration new create_users_table
+
+# 2. Tulis SQL ke supabase/migrations/<timestamp>_create_users_table.sql
+# 3. Terapkan ke database lokal
+npx supabase migration up
+
+# 4. Terapkan ke database remote produksi
+npx supabase db push
+```
+
+## Integrasi Orkestrasi
+- Terintegrasi dengan: `supabase-security-expert`, `database-orm-expert`, `ci-cd-devops-architect`.