skills/vendix-operating-scope/SKILL.md
Organization operating scope for Vendix: STORE vs ORGANIZATION behavior for inventory, suppliers, purchases, accounting entities, transfers, reports, and tenant isolation. Trigger: When working with organization account_type, onboarding scope, inventory/accounting visibility, suppliers, locations, transfers, or cross-store data access.
npx skillsauth add rzyfront/vendix vendix-operating-scopeInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use this skill whenever a change depends on whether an organization operates as one consolidated organization or as isolated stores.
Vendix has one global operating scope per organization:
STORE: every store is isolated.ORGANIZATION: operational and accounting data are shared/consolidated by organization.Do not introduce mixed per-store scope unless the business explicitly changes this rule.
SINGLE_STORE onboarding maps to operating_scope = STORE.MULTI_STORE_ORG onboarding maps to operating_scope = ORGANIZATION.SINGLE_STORE -> MULTI_STORE_ORG may change STORE -> ORGANIZATION.ORGANIZATION -> STORE is blocked by default because splitting historical inventory/accounting data is unsafe.STORE, a store must not see another store's inventory, locations, suppliers, purchases, accounting, valuation, or reports.ORGANIZATION, stores behave as channels/locations/segments under one organization scope.OperatingScopeService; do not duplicate scope decisions in feature services.accounting_entities through the operating scope.STORE, operational records should carry store_id directly or be reachable through a store-scoped parent.ORGANIZATION, records can use organization_id with store_id = null when they are shared.STORE; block them unless a future commercial/intercompany flow exists.vendix-prisma-scopesvendix-settings-systemvendix-inventory-stockvendix-auto-entriesvendix-accounting-rulesdevelopment
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.
development
Feature gating by store subscription state: global store write guard, AI feature gate, Redis feature resolution, quota consumption, frontend paywall interceptor, banner, and subscription UI states. Trigger: When adding feature gates, paywalls, subscription-based access control, protecting store write operations, AI feature gates, or rollout flags.
testing
SaaS subscription billing for Vendix stores: plan pricing, invoices, Wompi platform payments, manual payments, partner commissions, payouts, proration, and dunning. Trigger: When creating SaaS invoices, working with partner rev-share, margin/surcharge pricing, invoice sequence allocation, partner payout batches, subscription payments, manual payments, or dunning flows.
development
Periodic quota counters with Redis, UTC period keys, Lua-based idempotent AI quota consumption, request-id deduplication, and post-success consumption. Trigger: When building quota counters, enforcing monthly/daily feature caps, or reusing AI quota patterns for uploads, emails, exports, or rate-limited features.