Vendix

Patró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.

Establishes development best practices using the Vendix skills system. Trigger: ALWAYS when the user requests code changes, feature work, fixes, refactors, or development execution.

Defines the Vendix planning protocol before development. Trigger: When creating implementation plans, analyzing non-trivial changes, decomposing work, or preparing multi-agent development.

Runtime verification methodology for Vendix: curl for API/auth contracts and Playwright MCP for frontend end-to-end flows, run against the real local vhost (vendix.com). Every feature must be tested across THREE mandatory flow schemes — Happy Path, Sad Path, and Brute-Force. Trigger: Verifying an API endpoint or auth boundary with curl, running an end-to-end frontend flow, driving a browser to confirm UI behavior, designing happy/sad/brute-force test flows, security or data-integrity probing of a flow, installing or configuring Playwright MCP (with agent-browser as fallback), or choosing test credentials (seed accounts vs user-provided).

Controlled, non-destructive production verification that a Linear ticket is correctly deployed and behaves as its requirement demands. Drives Playwright MCP E2E against the live app at www.vendix.online, ALWAYS logged in as the demo account (never a real tenant). Runs Happy Path and Sad Path like how-to-test, plus a non-destructive Controlled Probe that OBSERVES weaknesses and REPORTS them instead of breaking the system; also reports any disparity between observed behavior and the ticket requirement. Trigger: Verifying a Linear ticket / Vendix issue is correctly applied in production, running a controlled E2E verification of a shipped ticket on www.vendix.online, confirming a production fix matches its requirement or reporting defects/anomalies, or doing non-destructive production verification with the demo account.

Date and timezone handling patterns: UTC-safe date-only display, form date strings, chart labels, date range queries, print formatting, and off-by-one day prevention. Trigger: When displaying dates, formatting date labels, using DatePipe/toLocaleDateString, querying date ranges, or adding DateTime fields.

Audit web↔mobile feature parity for Vendix: produce a granular functional inventory of a named web feature/module/flow (apps/frontend + its backend contracts), compare it capability-by-capability against the React Native mobile app (apps/mobile), emit a strategic gap map (Present / Partial / Absent / N/A), and hand the structured result to how-to-plan → how-to-dev → how-to-test to drive the mobile implementation. Trigger: When a developer asks to analyze/compare a web feature vs mobile, audit mobile parity, map what mobile is missing relative to web, produce a mobile implementation backlog from a web module, or plan mobile work that must mirror an existing web flow.

Colombian accounting rules for Vendix automatic entries: PUC account selection, debit/credit direction, payroll provisions, parafiscales, mapping-key ownership, and validation of balanced journal entries. Trigger: When working with journal entries, mapping keys, PUC accounts, payroll provisions, parafiscales, or any debit/credit logic.

Colombian payroll domain in Vendix: the payroll_runs and settlement state machines, the calculation engine (IBC caps, FSP, Ley 1607 exoneration, integral salary, art.383 withholding), novelty valuation, final settlement indemnification, DIAN electronic payroll (DSPNE), and the accounting events it emits. Trigger: working under apps/backend/src/domains/store/payroll, or editing payroll calculation, run/settlement state, novelties, advances, DIAN payroll, or bank export.

Generation of the Colombian PILA flat file (Planilla Integrada de Liquidación de Aportes, Resolución 2388/2016) in Vendix: fixed-width type-1 header and type-2 contributor records, IBC caps, novelty mapping (ING/RET/VSP/LMA/IGE/VAC/IRL), the positional layout serializer, and the export endpoint. Trigger: generating or editing the PILA flat file, its record layout, novelty flags, or IBC caps.

Author a sprint QA report as a self-contained, graphical HTML web presentation (a "slide deck") that summarizes bugs found by QA and tickets/flows validated within a time window, with charts, demonstrative listings, tasteful motion, and a prominent Critical/Urgent section. Data comes from one of two conversationally-negotiated paths: the QA user pastes the info as text, OR the agent autonomously queries Linear for the sprint window. Saved under docs/ and optionally published as a Claude Artifact. Trigger: Creating a QA sprint report as a web presentation, building an HTML slide-deck of bugs found and tickets validated in a sprint window, reporting QA results with charts and a critical/urgent section, or summarizing Linear bugs/validated tickets for a sprint into a visual report.

Authoring user stories as self-contained, animated HTML flow artifacts saved under docs/ at the repo root. Trigger: When documenting user stories, drawing user-story flow diagrams, or producing a graphical view of a feature's flows to save in docs/ and optionally publish as a Claude Artifact.

Automatic journal entry system: event-driven accounting, AutoEntryService, AccountingEventsListener, account mapping cascade, and mapping-key sync. Trigger: When adding automatic accounting flows, modifying auto-entry logic, adding mapping keys, or debugging missing journal entries.

Typed fiscal tax contract (tax_type) end-to-end: how a tax classification flows through calculation, persistence, accounting events, journal lines, declarations, DIAN scheme codes, reports, and frontend. Trigger: Adding a new tax_type value (INC, IBUA, ICUI, retefuente/reteiva/reteica), wiring a new accounting flow that carries tax, adding a fiscal declaration, or debugging a tax that posts to the wrong PUC account.

Governs parallel execution by multiple executive agents on the SAME current git branch and a shared working tree. Defines the hard prohibitions for executive agents (no branch switching, no touching out-of-scope files, no deletions, no destructive or history-rewriting git) and the commit-early protection that prevents irrecoverable loss of a neighbor's unstaged work. Trigger: NOT auto-invoked. Load ONLY when the user explicitly invokes it in a plan or workflow to run work in parallel on the current branch.

Checkout flow for STORE_ECOMMERCE: cart, shipping, payment methods, Wompi, WhatsApp checkout, bookings, and stock reservations. Trigger: When implementing or debugging ecommerce checkout, cart checkout, shipping/payment selection, or Wompi checkout.

Rules and patterns for commits, PRs, branching, and conflict resolution. Trigger: When making commits, creating PRs, working with branches, or resolving git conflicts.

Create, search, and list issues in the Vendix project on the Quickss Linear workspace. Use when the user asks to "crear issue en Linear", "crear ticket", "buscar issue", "¿existe un issue de...?", "listar issues de Vendix", "crear bug en Vendix", or describes a task that should become a Vendix issue. Operates ONLY against the Quickss workspace, team "Quickss" (key QUI), and project "Vendix" — hardcoded, not configurable. Do NOT use for editing the workspace, managing teams/projects, or working with a different Linear workspace.

Skill for reviewing Pull Requests from any GitHub repository using GitHub CLI (gh). Analyzes regression, security, logic, syntax, core files, and code quality. Trigger: When the user asks to review PRs, analyze PR code, or do code review.

Planillas de despacho (rutas DSD con recaudo) para distribuidoras colombianas: agrupar múltiples remisiones en una ruta con vehículo/conductor/auxiliares y orden de paradas, ejecutar captura progresiva desde la app móvil, y cuadrar el recaudo al regreso reutilizando caja/cartera/refunds/retenciones existentes. Trigger: When working with dispatch_routes, dispatch_route_stops, vehicles, DSD route settlement, withholding breakdown per stop, declared_cash variance, route PDF print, or any "agregador de ruta que orquesta primitivas".

Bootstrap a developer's local Linear setup for the Vendix project on the Quickss workspace. Use when the user says "configurar Linear", "no tengo credenciales", "conectar a Linear", or when the `linear-issues` skill reports a missing `LINEAR_API_KEY` or absent `.linear/config.json`. Validates the personal API key, resolves and caches the team/project/labels/state UUIDs in `.linear/config.json`, and confirms with a smoke-test read. Do NOT use for creating or mutating issues (use `linear-issues` instead).

Opt-in Bruno API testing template for Vendix collections: request files, auth inheritance, DTO-aligned payloads, post_response scripting, and pragmatic assertions. NOT an agent verification mechanism — agents verify endpoints with curl (see how-to-dev / how-to-plan). Trigger: ONLY when a developer explicitly asks to write or edit a Bruno (.bru) test.

Inventory stock management patterns: StockLevelManager, stock_levels source of truth, reservations, variant/base transitions, audit records, and denormalized stock sync. Trigger: When working with stock levels, inventory adjustments, stock transfers, reservations, or any operation that modifies product/variant quantities.

Inventory valuation rules for Vendix: current and historical valuation, CPP/FIFO costs, COGS, inventory snapshots, and alignment with accounting entities. Trigger: When implementing or debugging inventory valuation, COGS, cost layers, stock cost snapshots, or inventory valuation reports.

Panel UI module visibility system: industry dimension (stores.industries), store-level ceiling (store_settings.settings.panel_ui), per-user panel_ui, NgRx selectors, MenuFilterService, module flows, and sidebar filtering. Trigger: When adding sidebar modules, configuring panel_ui visibility, editing industry rules in INDUSTRY_HIDDEN_MODULES, adding per-industry module rules, debugging menu filtering, or distinguishing visibility from permissions.

Persistent shared memory for Vendix via Engram. Covers self-bootstrap for new devs, the daily save/search/context/sync cycle, project scope conventions (--project vendix), and how to handle memory conflicts. Trigger this skill whenever Engram is mentioned, when the user asks about cross-session or cross-agent memory, or when the agent detects Engram is not installed and the user wants the team-memory workflow enabled.

Organization fiscal scope for Vendix: STORE vs ORGANIZATION legal/tax entity behavior, DIAN configuration ownership, fiscal accounting entities, fiscal reports, and intercompany transfers. Trigger: When working with organizations.fiscal_scope, fiscal accounting entities, DIAN NIT ownership, fiscal reports by NIT, fiscal scope migrations, or intercompany stock-transfer entries.

Responsive data display patterns using TableComponent, ItemListComponent, and ResponsiveDataViewComponent. Trigger: When displaying lists of records, creating responsive admin tables, or configuring mobile card views.

Standard mobile-first admin list module layout for Vendix: stats, sticky search/header, Card wrapper, and ResponsiveDataView. Trigger: When creating or refactoring STORE_ADMIN, SUPER_ADMIN, or other private admin list modules.

Build and runtime verification steps for Vendix development. Trigger: Verifying Build, checking Docker watch-mode logs, checking current development app status, or confirming development changes do not introduce compile/runtime errors.

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.

Backend RBAC permission rows, @Permissions decorators, and PermissionsGuard behavior. Trigger: When adding permissions, editing @Permissions decorators, seeding roles/permissions, or distinguishing authorization from panel_ui visibility.

Angular 20 zoneless and signals patterns for Vendix frontend: app.config setup, signal inputs/outputs/models, toSignal in facades, CVA rules, audit script usage, and legacy patterns that must not be copied into new code.

Reusable sticky header pattern for Vendix form/detail pages. Trigger: When implementing sticky headers, page-level save/cancel actions, badges, or back navigation in frontend modules.

Vendix cloud operations guidance for using the private production runbook, SSH, and AWS CLI to inspect or administer cloud resources. Trigger: When consulting keys/README.md, using AWS CLI for Vendix cloud inventory, checking production resource locations, or deciding whether to use SSH versus AWS CLI.