@nurix/etna 0.18.22 → 0.18.24

package/data/harnesses/mobile/agents/performance-review.md

@@ -1,223 +0,0 @@
----
-name: performance-review
-description: Combined dependency + code health audit. Part A audits the dependency supply chain — security CVEs, outdated packages, license compliance, abandoned packages, unwanted transitive dependencies, install size. Part B audits code-level health — bundle size, tree-shaking issues, performance anti-patterns, code-quality flags. Run weekly or before releases. Merges the former `dep-health` and `review` agents so the package tree and the code that uses it are audited together.
-tools: Read, Glob, Grep, Bash
-model: inherit
----
-
-# Performance-Review Agent
-
-You audit project health on two fronts that reinforce each other: the **dependency supply chain** (Part A) and the **code that consumes it** (Part B). A heavy dependency and a tree-shaking failure that ships it are the same problem seen from two ends — auditing them together lets you connect cause to symptom (e.g., a 10 MB package flagged in Part A that a namespace import in Part B pulls fully into the bundle).
-
-## Before Starting
-
-1. If `./docs/memory/performance-review.md` exists, read it for baselines (vulnerability trends, completed remediations, known exceptions, chunk sizes, prior anti-pattern counts). This prevents re-recommending solved issues and gives comparison points.
-2. Read `./package.json` for direct dependencies, entry points, and scripts.
-3. Detect the package manager by checking for lockfiles: `pnpm-lock.yaml` (pnpm), `package-lock.json` (npm), `yarn.lock` (yarn). Use the matching commands throughout.
-4. If `.claude/rules/general.instructions.md` (or `.claude/rules/general.md`) exists, read the Recommended Packages table for version pins/baselines.
-
----
-
-# Part A — Dependency Health
-
-## Step 1: Security Vulnerabilities
-
-Run the audit command for the detected PM:
-
-```bash
-# pnpm
-pnpm audit --json 2>/dev/null || pnpm audit
-
-# npm
-npm audit --json 2>/dev/null || npm audit
-
-# yarn
-yarn npm audit --json 2>/dev/null || yarn audit
-```
-
-Parse results by severity (critical, high, moderate, low). For each critical/high CVE report:
-
-- Package name and installed version
-- CVE ID
-- Affected version range
-- Fixed version (if available)
-- Which direct dependency pulls it in
-
-Compare against the previous scan in `docs/memory/performance-review.md` — flag new vulnerabilities since last audit.
-
-## Step 2: Outdated Dependencies
-
-```bash
-pnpm outdated --format json 2>/dev/null || pnpm outdated
-# or: npm outdated --json
-# or: yarn outdated
-```
-
-Classify into:
-
-- **Major behind** (2+ majors) — highest risk
-- **Minor behind** — moderate risk
-- **Patch behind** — low risk
-
-Cross-reference against the Recommended Packages table in the project rules — flag packages where the installed version is behind the pinned version. Report the top 10 most outdated by semver distance.
-
-## Step 3: License Compliance
-
-```bash
-pnpm licenses list --json 2>/dev/null || pnpm licenses list
-# npm: npx license-checker --json
-```
-
-Flag non-permissive licenses in the dependency tree: GPL, AGPL, SSPL, EUPL, or other copyleft. For each: package name, license type, direct or transitive.
-
-## Step 4: Abandoned Packages
-
-For each direct dependency, check npm registry metadata:
-
-```bash
-npm view {package} time --json 2>/dev/null
-```
-
-Flag packages with no publish in 18+ months. Report package name, last publish date, and whether the upstream repository appears archived.
-
-## Step 5: Unwanted Transitive Dependencies
-
-Check for known-bloat packages in the dependency tree:
-
-- `moment` (use date-fns instead)
-- `lodash` (use subpath imports)
-- `underscore`
-- `request` (deprecated)
-- `node-fetch` (when runtime has native fetch)
-
-For each found:
-
-```bash
-pnpm why {package}
-# or: npm ls {package}
-```
-
-Report which direct dependency pulls it in and the installed size. Carry the package names you find here into Part B Step 7 — a transitive bloat package that gets imported as a namespace import is a bundle problem, not just a tree problem.
-
-## Step 6: Dependency Size Impact
-
-```bash
-du -sh node_modules/.pnpm/*/ 2>/dev/null | sort -rh | head -15
-# or for npm: du -sh node_modules/*/ | sort -rh | head -15
-```
-
-List the 15 largest packages by installed size. Flag any single package over 10 MB. Compare against the previous snapshot.
-
----
-
-# Part B — Code Health
-
-## Step 7: Bundle Size Analysis
-
-1. Run the build (`pnpm build` / `npm run build` / `yarn build` per detected PM) to generate the production bundle
-2. Parse build output to extract chunk sizes (raw and gzip)
-3. Identify the top 10 largest chunks by raw size
-4. Compare against known baselines in `docs/memory/performance-review.md`
-5. Flag any chunk that grew >50 KB since last review
-
-### Common bundle-bloat patterns
-
-Search for anti-patterns that defeat tree-shaking:
-
-- `import * as` namespace imports from large libraries (lucide-react, lodash, etc.)
-- Dynamic string-based icon/component resolution (`Icons[name]`, `Components[type]`)
-- Barrel file re-exports pulling in unused code
-- Missing `React.lazy()` for heavy components (Monaco, Uppy, D3, Plotly, Mermaid)
-- Full library imports where subpath imports exist (`import _ from 'lodash'` vs `import get from 'lodash/get'`)
-
-```bash
-# Find namespace imports from large libraries
-grep -rn "import \* as" src/ --include="*.jsx" --include="*.tsx" --include="*.js" --include="*.ts"
-
-# Find dynamic component/icon resolution
-grep -rn "Icons\[" src/ --include="*.jsx" --include="*.tsx"
-```
-
-## Step 8: Performance Anti-Patterns
-
-Scan for React performance issues:
-
-### Missing memoization
-
-- Components rendering large lists without `React.memo`
-- Expensive computations without `useMemo`
-- Callback props without `useCallback` causing child re-renders
-- Focus on components in tables, lists, grids, repeated rows
-
-### Request waterfalls
-
-- Sequential `await` calls that could be `Promise.all`
-- `useEffect` chains where one fetch triggers another
-- Component trees where parent fetches block child renders
-
-### Missing virtualization
-
-- Lists rendering >50 items without react-window or similar
-- Tables with unbounded row counts
-- Grids without lazy loading
-
-## Step 9: Import Health
-
-1. Check for circular dependencies using import chains
-2. Identify unused exports (files exporting functions not imported elsewhere)
-
-## Step 10: Code-Quality Flags
-
-- `dangerouslySetInnerHTML` usage without sanitization context
-- `// TODO` and `// FIXME` comments older than 30 days
-- `console.log` / `console.warn` / `console.error` left in production code
-- Hardcoded API URLs, credentials, or environment-specific values
-- Missing error boundaries around async components
-
-```bash
-grep -rn "console\.\(log\|warn\|error\)" src/ --include="*.jsx" --include="*.tsx" --include="*.js" --include="*.ts" | grep -v "// eslint"
-grep -rn "TODO\|FIXME\|HACK\|XXX" src/ --include="*.jsx" --include="*.tsx" --include="*.js" --include="*.ts"
-```
-
----
-
-## Step 11: Report & Track
-
-### Report format
-
-**Dependencies**
-
-- **Vulnerabilities**: critical/high CVEs, new since last audit
-- **Outdated**: top outdated packages by semver distance
-- **Licenses**: non-permissive license flags
-- **Abandoned**: packages with no recent publishes
-- **Transitive bloat**: unwanted packages pulled in transitively
-- **Dependency size**: largest installed packages
-
-**Code**
-
-- **Bundle size**: total vendor size, top offenders, growth since last review
-- **Tree-shaking issues**: namespace imports, barrel-file problems (cross-referenced with the heavy/bloat packages from Part A)
-- **Performance**: missing memoization, request waterfalls, missing virtualization
-- **Code quality**: console statements, TODOs, hardcoded values
-
-**Recommendations**: a single prioritized list spanning both fronts, with estimated impact. A critical CVE outranks everything; bundle growth and tree-shaking fixes follow by impact.
-
-### Update tracking
-
-1. Write a snapshot to `docs/memory/performance-review.md` with date including: vulnerability count by severity, outdated count by category, flagged licenses, abandoned packages, chunk sizes, top packages, anti-pattern counts.
-2. Append new items to `docs/history/backlog.md`:
-   - `- **[P0]** Critical CVE in \`{package}\`: {CVE-ID} — discovered by performance-review`
-   - `- **[P2]** Abandoned dependency: \`{package}\` (last published {date}) — discovered by performance-review`
-   - `- **[P2]** Bundle grew by 80KB in chunk \`{name}\` — discovered by performance-review`
-3. Report summary to the user
-
-## Rules
-
-- Read-only for source code — never modify `src/` files
-- Never run `npm install`, `pnpm install`, `yarn install`, or any command that modifies dependencies
-- May write to `docs/memory/performance-review.md` and `docs/history/backlog.md`
-- Be specific: include package names, byte sizes, CVE IDs, version numbers, file paths, line numbers
-- Prioritize by impact — a critical CVE matters more than a patch update; trends matter more than absolutes when baselines exist
-- If a command isn't available or applicable (e.g., audit unsupported, build fails on a non-JS project), skip that step and note it in the report
-- A clean report is valid — do not invent issues

package/data/harnesses/mobile/harness.json

@@ -1,11 +0,0 @@
-{
-  "harness": "mobile",
-  "name": "mobile",
-  "version": "1.1.5",
-  "files": [
-    ".prettierrc.json",
-    ".prettierignore",
-    ".vscode/settings.json"
-  ],
-  "digest": "e42a39e54bdb"
-}

package/data/harnesses/mobile/hooks/generate-ownership-index.mjs

@@ -1,148 +0,0 @@
-// plugins/code/hooks/generate-ownership-index.mjs — SessionStart hook: scan docs/features/**/*.md,
-// extract the focal frontmatter (owns / module / keywords / status), and inject a compact
-// code-path → owning-doc index via additionalContext. Fires on startup/resume/clear/compact so the
-// map survives /clear and /compact and is regenerated fresh every time. Writes no file.
-
-import fs from "node:fs";
-import path from "node:path";
-
-// Read all of stdin synchronously; returns "" if nothing is piped.
-function readStdin() {
-  try {
-    return fs.readFileSync(0, "utf8");
-  } catch (e) {
-    return "";
-  }
-}
-
-// Resolve the project root: CLAUDE_PROJECT_DIR env, else payload cwd, else process cwd.
-function resolveProjectDir(payload) {
-  return process.env.CLAUDE_PROJECT_DIR || (payload && payload.cwd) || process.cwd();
-}
-
-// Recursively collect every .md file under dir (returns [] if the dir is absent).
-function listMarkdown(dir) {
-  const out = [];
-  let entries;
-  try {
-    entries = fs.readdirSync(dir, { withFileTypes: true });
-  } catch (e) {
-    return out;
-  }
-  for (const entry of entries) {
-    const full = path.join(dir, entry.name);
-    if (entry.isDirectory()) out.push(...listMarkdown(full));
-    else if (entry.isFile() && entry.name.endsWith(".md")) out.push(full);
-  }
-  return out;
-}
-
-// Pull the leading `--- … ---` frontmatter block; "" if the file has none.
-function frontmatter(text) {
-  const m = /^?---\r?\n([\s\S]*?)\r?\n---/.exec(text);
-  return m ? m[1] : "";
-}
-
-// Trim surrounding whitespace, then strip one layer of matching quotes.
-function unquote(s) {
-  return String(s).trim().replace(/^["']|["']$/g, "").trim();
-}
-
-// Read one frontmatter key: scalar (`k: v`), inline array (`k: [a, b]`), or a following `- item` block.
-// Returns a string for scalars, an array for lists, or undefined when the key is absent.
-function field(block, key) {
-  const lines = block.split(/\r?\n/);
-  const head = new RegExp(`^${key}\\s*:\\s*(.*)$`);
-  for (let i = 0; i < lines.length; i++) {
-    const m = head.exec(lines[i]);
-    if (!m) continue;
-    const raw = m[1].trim();
-    if (raw === "") {
-      const items = [];
-      for (let j = i + 1; j < lines.length; j++) {
-        const li = /^\s*-\s+(.*)$/.exec(lines[j]);
-        if (!li) break;
-        items.push(unquote(li[1]));
-      }
-      return items;
-    }
-    if (raw.startsWith("[")) {
-      return raw.replace(/^\[|\]$/g, "").split(",").map((s) => unquote(s)).filter(Boolean);
-    }
-    return unquote(raw);
-  }
-  return undefined;
-}
-
-// Coerce a field that may be scalar/array/undefined into a clean string array.
-function asList(v) {
-  if (v == null) return [];
-  return (Array.isArray(v) ? v : [v]).map((s) => String(s).trim()).filter(Boolean);
-}
-
-// Build the ownership index text from every feature doc's frontmatter.
-function buildIndex(projectDir) {
-  const featuresDir = path.join(projectDir, "docs", "features");
-  const files = listMarkdown(featuresDir);
-  const lines = [];
-  let deprecated = 0;
-  for (const file of files) {
-    let text;
-    try {
-      text = fs.readFileSync(file, "utf8");
-    } catch (e) {
-      continue;
-    }
-    const block = frontmatter(text);
-    if (!block) continue;
-    const owns = asList(field(block, "owns"));
-    if (owns.length === 0) continue;
-    const status = (field(block, "status") || "active").toString().toLowerCase();
-    if (status === "deprecated") {
-      deprecated += 1;
-      continue; // keep deprecated docs out of the routing lines
-    }
-    const moduleLabel = (field(block, "module") || "—").toString();
-    const keywords = asList(field(block, "keywords"));
-    const doc = path.relative(projectDir, file).split(path.sep).join("/");
-    const kw = keywords.length ? `[${keywords.join(", ")}]` : "[]";
-    for (const glob of owns) {
-      lines.push(`${glob} → ${doc} · ${moduleLabel} · ${kw} · ${status}`);
-    }
-  }
-  if (lines.length === 0) return "";
-  lines.sort();
-  const header =
-    "# Ownership index (generated) — code-path glob → owning feature doc · module · keywords · status\n" +
-    "# Match the file or topic you're about to touch, then read the owning doc before changing it.\n";
-  const footer = deprecated > 0 ? `\n# (${deprecated} deprecated feature doc(s) omitted)` : "";
-  return header + lines.join("\n") + footer;
-}
-
-function main() {
-  const raw = readStdin();
-  let payload = {};
-  try {
-    payload = raw ? JSON.parse(raw) : {};
-  } catch (e) {
-    payload = {};
-  }
-  const index = buildIndex(resolveProjectDir(payload));
-  if (!index) return; // no feature docs yet → inject nothing
-  process.stdout.write(
-    JSON.stringify({
-      hookSpecificOutput: {
-        hookEventName: "SessionStart",
-        additionalContext: index,
-      },
-    })
-  );
-}
-
-try {
-  main();
-} catch (e) {
-  // Best-effort: a routing index is a convenience, never a gate. Inject nothing on failure.
-} finally {
-  process.exit(0);
-}

package/data/harnesses/mobile/hooks/hooks.json

@@ -1,16 +0,0 @@
-{
-  "hooks": {
-    "SessionStart": [
-      {
-        "matcher": "",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "node \"$CLAUDE_PROJECT_DIR/.claude/hooks/generate-ownership-index.mjs\"",
-            "timeout": 10
-          }
-        ]
-      }
-    ]
-  }
-}

package/data/harnesses/mobile/rules/database.md

@@ -1,38 +0,0 @@
-# Database
-
-Fixed conventions for relational schemas — table/column/index **names**, the **key vocabulary** (`id` / `slug` / `label`), column types, and Drizzle mirrors — so the same concept carries the same name in **every** Nurix project. This is a cross-project consistency rule: **one concept, one name, everywhere** — never `slug` in one repo and `handle` / `key` / `code` in another. General code naming (variables, files, casing) is [`nomenclature.md`](nomenclature.md); this rule owns the database.
-
-Written for SQLite / Cloudflare D1 + Drizzle (the concrete types below). The **names and key vocabulary are engine-agnostic** — a Postgres project keeps the same column names and semantics with native types (`uuid`, `timestamptz`, `boolean`).
-
-## Keys & the shared vocabulary
-
-Three column roles are fixed across every table and every project:
-
-- **`id`** — the primary key, **always a UUID** (`TEXT PRIMARY KEY` on D1, `uuid` on Postgres). Never a synthetic or natural key (`type_page_button`, `human:default` are ❌). Runtime rows mint a UUIDv7; seed rows derive a deterministic UUIDv5 of the natural key so re-seeds stay stable. Never mix synthetic and UUID ids in one table.
-- **`slug`** — the **stable key other rows reference**: `UNIQUE`, lowercase `snake_case`. **Foreign keys point at `slug`, not `id`.** One concept = one slug name across every table and repo. ❌ Never rename this role `handle`, `key`, `code`, or `name` in a different project — it is always `slug`.
-- **`label`** — the **human display name**. Always `label` — ❌ never `name`, `title`, or `display_name`.
-
-Reference columns name what they point at: `<entity>_id` for a UUID-PK reference (`user_id`, `app_id`), `<entity>_slug` for a slug reference (`source_slug`).
-
-- **Enforced** (the referenced row must exist) → a real `FOREIGN KEY (<x>_slug) REFERENCES <table>(slug)`.
-- **Drift-tolerant** (a controlled-vocabulary value that may fall off-list) → a plain value column, **no** FK, paired with an `is_*` boolean recording whether the value is in the canonical set.
-
-## Naming
-
-- **Tables** — `snake_case`, plural noun for what they hold (`users`, `apps`, `devices`).
-- **Junction (M:N) tables** — `<entityA>_<entityB>_map`, **always**, even when the join carries its own columns; singular stems, owning/anchor entity first (`app_user_map`, `app_device_map`). ❌ Never a "nice" noun (`members`, `installs`, `memberships`, `enrolments`) — the name must read as a join, and a reviewer should know both sides from it.
-- **Columns** — `snake_case`; booleans `is_*` / `has_*`; timestamps `created_at` / `updated_at`; foreign keys `<entity>_id`.
-- **Indexes** — `<table>_<col(s)>_idx`; unique `<table>_<col(s)>_unique`; a junction's composite unique reads `<table>_<colA>_<colB>_unique` (`app_user_map_app_user_unique`).
-- **Drizzle mirror** — the exported object is the camelCase table name (`app_user_map` → `appUserMap`); column props are the camelCase of the column (`created_at` → `createdAt`). The `sqliteTable("…")` string and every index name must match the DDL (`init.sql`) exactly — the schema-parity boundary.
-
-## Column types (SQLite / D1)
-
-- **Timestamps** — `created_at` + `updated_at`, both `TEXT NOT NULL DEFAULT (datetime('now'))`, on **every** table — except append-only logs, which carry only `created_at`.
-- **Booleans** — `INTEGER`, named `is_*` / `has_*` (Drizzle `integer(…, { mode: "boolean" })`).
-- **JSON** — `TEXT` (Drizzle `text(…, { mode: "json" })`).
-
-## Vocabulary / lookup tables
-
-A controlled-vocabulary table (statuses, kinds, categories) follows a fixed shape: `id` (UUID) · `slug` (UNIQUE) · `label` · optional `description` · `status` · timestamps.
-
-- **Seeds are generated, never hand-written** — the source of truth is a CSV or a shared package; a generator emits the `*.seed.sql` with UUIDv5 ids and an idempotent `ON CONFLICT(slug)` upsert that preserves live counts / admin-tuned columns. Hand-editing seed SQL is ❌ — regenerate it.

package/data/harnesses/mobile/rules/general.md

@@ -1,49 +0,0 @@
-# General Standards
-
-Runtime versions and the canonical package list — the workspace baseline every Nurix code harness loads. Web-frontend/styling conventions are [`frontend.md`](frontend.md); the Express server and the API response envelope are [`express.md`](express.md).
-
-## Runtime Versions
-
-- **Node.js:** 22 LTS (latest)
-- **Package manager:** detect from lockfile (`pnpm-lock.yaml` → pnpm, `yarn.lock` → yarn, `package-lock.json` → npm). Don't hardcode one.
-- **PostgreSQL:** 17 · **Redis:** 7.x (latest)
-
-## Recommended Packages
-
-No alternatives. Just use these.
-
-| Package                  | Version   | Use                    | Don't use                  |
-| ------------------------ | --------- | ---------------------- | -------------------------- |
-| react                    | ^19.2.3   | UI components          | -                          |
-| vite                     | ^8.0.0    | Build tool, dev server | webpack, CRA               |
-| tailwindcss              | ^4.1.18   | Styling                | styled-components          |
-| @vitejs/plugin-react-swc | ^4.2.2    | JSX compilation        | @vitejs/plugin-react       |
-| react-router-dom         | ^7.11.0   | Routing                | -                          |
-| @reduxjs/toolkit         | ^2.11.2   | State management       | zustand, jotai             |
-| react-redux              | ^9.2.0    | Redux React bindings   | -                          |
-| axios                    | ^1.13.2   | HTTP requests          | fetch                      |
-| date-fns                 | ^4.1.0    | Date formatting        | moment, dayjs              |
-| @dnd-kit/core            | ^6.3.1    | Drag and drop          | react-beautiful-dnd        |
-| motion                   | ^12.23.26 | Animations             | react-spring               |
-| sonner                   | ^2.0.7    | Toast notifications    | react-toastify             |
-| react-window             | ^2.2.3    | List virtualization    | react-virtualized          |
-| nanoid                   | ^5.1.6    | ID generation          | uuid                       |
-| express                  | ^5.2.1    | HTTP server            | fastify, koa               |
-| drizzle-orm              | latest    | Database ORM           | prisma, sequelize, typeorm |
-| drizzle-kit              | latest    | Schema tooling         | -                          |
-| zod                      | ^4.2.1    | Schema validation      | yup, joi                   |
-| jose                     | ^6.1.3    | JWT handling           | jsonwebtoken               |
-| microdiff                | ^1.5.0    | JSON object diffing    | deep-diff, just-diff       |
-| react18-json-view        | ^0.2.9    | JSON tree view         | react-json-view            |
-| @tiptap/react            | ^3.11.1   | Rich text editor       | slate, quill, draft-js     |
-| shiki                    | ^3.22.0   | Syntax highlighting    | prism, highlight.js        |
-| lucide-react             | ^0.562.0  | Icons                  | react-icons, heroicons     |
-| @pdfme/generator         | ^5.5.8    | PDF generation         | jspdf, pdfkit              |
-| cmdk                     | ^1.1.1    | Command palette        | kbar, ninja-keys           |
-| @monaco-editor/react     | ^4.7.0    | Code editor            | codemirror, ace            |
-| localforage              | ^1.10.0   | Client-side storage    | idb, dexie                 |
-| react-markdown           | ^10.1.0   | Markdown rendering     | marked, markdown-it        |
-| remark-gfm               | ^4.0.1    | GFM (tables, tasklists) | remark-github, custom      |
-| fast-deep-equal          | ^3.1.3    | Deep equality checks   | lodash.isEqual             |
-| @ngneat/falso            | latest    | Fake data generation   | @faker-js/faker, chance    |
-| pino                     | ^10.1.0   | Logging                | winston                    |

package/data/harnesses/mobile/rules/nomenclature.md

@@ -1,34 +0,0 @@
-# Nomenclature Guidelines
-
-## Naming Guidelines
-
-- Use descriptive names that reveal intent, purpose, and usage
-- Names should explain why something exists and how it's used
-- Favor clarity over brevity
-- Maintain consistency within the codebase
-- Avoid abbreviations unless they're universally understood
-
-## Naming Styles
-
-- Variables : Use nouns or noun phrases. Examples: `userData`, `firstName`, `paymentStatus`, `configOptions`
-- Functions & Methods : Use verbs or verb phrases that describe the action. Examples: `calculateTotal`, `getUserInfo`, `validateInput`, `sendNotification`
-- Boolean Variables : Prefix with is**, has**, can**, or should**. Examples: `isValid`, `hasPermission`, `canEdit`, `shouldRefresh`
-- Arrays : Use plural nouns. Examples: `users`, `productList`, `errorMessages`, `activeConnections`
-- Classes & Components : Use singular nouns or noun phrases. Examples: `RequestHandler`, `UserProfile`, `PaymentProcessor`, `DataValidator`
-- Constants : Use uppercase with meaningful names. Examples: `DEFAULT_TIMEOUT`, `API_BASE_URL`, `MAX_RETRY_COUNT`, `COLOR_PRIMARY`
-- Event Handlers : Use Prefix with handle or on. Examples: `handleSubmit`, `onUserLogin`, `handleInputChange`, `onPageLoad`
-- Interfaces & Types : Use Consider prefixing with I for interfaces (if preferred). Examples: `IUserData`, `IConfigOptions`, `AuthResponse`, `RequestParams`
-- Promises & Async Functions : Use Consider using future tense or suffixes like Async. Examples: `fetchUserData`, `getUserProfileAsync`, `loadConfigAsync`, `processPayment`
-- File & Folder Structure : Use lowercase with descriptive names. Group by feature or function type. Example: `auth/login_service.js`
-
-## Casing Styles
-
-- camelCase : Used in Variables, function names, method names, property names. Examples: `userData`, `calculateTotal`, `firstName`, `isValidEmail`
-- PascalCase : Used in Class names, component names, type definitions. Examples: `UserProfile`, `DataService`, `AuthProvider`, `RequestHandler`
-- snake_case : Used in File names, folder names. Examples: `user_service`, `api_utils`, `auth_middleware`, `data_models`
-- UPPER_SNAKE_CASE : Used in Constants, environment variables. Examples: `MAX_RETRY_COUNT`, `API_KEY`, `DEFAULT_TIMEOUT`, `COLOR_PRIMARY`
-- kebab-case : Used in URLs, CSS class names, HTML IDs. Examples: `nav-container`, `user-profile`, `button-primary`, `form-wrapper`
-
-## Database
-
-Table, column, index, and key naming for relational schemas — the `id` / `slug` / `label` vocabulary, junction `_map` tables, and Drizzle mirrors — lives in [`database.md`](database.md), the cross-project database conventions rule. Kept there, not here, so there is one canonical home and the same concept carries the same name in every project.