菜单
Mobile app development rules for Vendix Expo/React Native project. Trigger: When editing, creating, or modifying any file under apps/mobile, or when developing mobile-specific features.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | mobile-dev |
| description | Mobile app development rules for Vendix Expo/React Native project. Trigger: When editing, creating, or modifying any file under apps/mobile, or when developing mobile-specific features. |
| license | MIT |
| metadata | {"author":"rzyfront","version":"1.0","scope":["root"],"auto_invoke":["Editing or creating any file under apps/mobile","Developing features for the mobile app","Adding dependencies to apps/mobile/package.json"]} |
| allowed-tools | Read, Edit, Write, Glob, Grep, Bash |
This skill governs all development within the mobile app (apps/mobile). Its primary purpose is to enforce strict boundaries: never edit files outside apps/mobile, even when referencing patterns from other projects for alignment.
The mobile app is an Expo/React Native project. It can reference frontend (apps/frontend) components/styles for UI alignment and backend (apps/backend) DTOs/interfaces for API contract alignment, but must never modify those files.
ALL edits, creations, and modifications are exclusively within apps/mobile/.
ALLOWED:
apps/mobile/src/...
apps/mobile/app/...
apps/mobile/assets/...
apps/mobile/package.json
apps/mobile/tsconfig.json
apps/mobile/*.config.js
FORBIDDEN:
apps/backend/src/... ← Read only
apps/frontend/src/... ← Read only
libs/shared-types/src/... ← Read only
Any file outside apps/mobile/
The mobile project may read files from other projects for reference:
| Source | Purpose | Allowed |
|---|---|---|
apps/frontend/src/... | UI patterns, component structure, styling conventions | ✅ Read only |
apps/backend/src/... | DTOs, API contracts, TypeScript interfaces | ✅ Read only |
libs/shared-types/... | Shared enums, types, constants | ✅ Read only |
apps/backend/prisma/... | Data models for understanding API entities | ✅ Read only |
Any file outside apps/mobile/ | Reference only | ✅ Read only |
NEVER edit, modify, or write to any file outside apps/mobile/.
All mobile-specific dependencies must be declared in apps/mobile/package.json only.
ALLOWED:
npm install <pkg> --prefix apps/mobile
# or edit apps/mobile/package.json directly
FORBIDDEN:
npm install <pkg> at root ← Breaks monorepo isolation
Editing root package.json ← Belongs to vendix-monorepo-workspaces
Adding deps to apps/frontend/ ← Not mobile's concern
Adding deps to apps/backend/ ← Not mobile's concern
When aligning mobile interfaces with backend DTOs or frontend patterns:
apps/backend/... to understand the API contract.apps/mobile/src/....CORRECT (read backend, create mobile version):
// Read: apps/backend/src/domains/product/dto/product.dto.ts
// Create: apps/mobile/src/app/products/interfaces/product.interface.ts
export interface Product {
id: string;
name: string;
price: number;
}
FORBIDDEN (direct import from backend):
import { ProductDto } from '../../../../backend/...'; // ✗ NO
Do not modify libs/shared-types/ or any shared library as part of mobile development. If a type needs to be shared, it must be defined independently in apps/mobile/src/ or requested as a separate cross-project change.
Mobile app consumes the same backend API as the frontend. When implementing API calls:
vendix-core - Repository architecture and app boundary understandingvendix-monorepo-workspaces - Monorepo dependency and package managementvendix-backend-api - Understanding backend API endpoint patternsvendix-frontend-component - Reference for UI component patternsPatrón unificado de direcciones + geocoding para checkout, clientes, remisiones y planilla. Cubre tabla `addresses`, endpoints `store/addresses`, snapshot `dispatch_notes.customer_address`, componente `app-address-map-picker` (MapLibre), `GeocodingService` frontend, proxy Nominatim backend, validación sintáctica + warning no-bloqueante, cascade `resolveStopCoordinates` y customer-modal crear-mode. Trigger: cuando editar/agregar dirección de cliente, remisión o stop; cuando el mapa del despacho rechaza una dirección; cuando integrar dirección + mapa opcional + geocoding.
High-level AI Engine integration guide for Vendix: choosing the right AI subsystem, creating AI-powered features, and consuming AI Applications. Trigger: When creating AI-powered features, integrating AI Engine into domains, configuring AI providers/apps, or styling AI interaction elements.
AI async queue system using BullMQ: generation jobs, embedding jobs, queue registration, processors, retries, and job status. Trigger: When working with AI async processing, BullMQ queues, AI job processors, or embedding/generation background jobs.
Suite restaurante para Vendix: modelado plato/insumo, recetas/BOM, producción de sub-recetas en lote, fire-to-kitchen con descuento y COGS, mesas con cuenta abierta y split financiero, KDS en tiempo real vía SSE, menú con carta/secciones/ combos/ventanas horarias/ingeniería BCG, e integración POS con gating por industria. Trigger: When working on restaurant suite, recipes, BOM, prepared products, ingredient flags, kitchen fire, KDS, kitchen tickets, table sessions, open tabs, bill split, menu engineering, menu availability windows, or any store whose `industries` includes `restaurant`.
Flujo QR-de-mesa para comensales escaneando desde el storefront (`{shop-hostname}/?mesa=<public_token>`): tokens, modos de escaneo, re-asociación a sesión activa, cuenta compartida, SSE del comensal y reactivación automática desde mesa en limpieza. Complementa `vendix-restaurant-ops` (lado POS/admin) cubriendo el lado storefront/comensal que la otra skill no gobierna. Trigger: When editing QR de mesa comensal, public_token, table_session desde storefront, `ecommerce/tables/*` endpoints, table-banner UI, or `qr_scan_behavior` in restaurant settings.
Cómo nacen bien los reportes descargables de Vendix: exportación XLSX profesional con ExcelJS (nunca CSV), fechas en la timezone de la tienda (fallback SIEMPRE America/Bogota), dataset completo, agregación única (pantalla == archivo), y flujo de export unificado backend→frontend. OBLIGATORIA al crear, editar, fixear o mejorar cualquier reporte. Trigger: Creating, editing, fixing or improving any downloadable/report/export feature in apps/backend/src/domains/store/analytics or apps/frontend .../store/reports.