skills/vendix-frontend-cache/SKILL.md
Frontend caching patterns for Vendix Angular services: shareReplay TTL caches, instance fields, module-level Map caches, parameterized cache keys, and invalidation after writes. Trigger: When caching frontend HTTP data or reducing repeated dashboard/report requests.
npx skillsauth add rzyfront/vendix vendix-frontend-cacheInstall 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.
Representative patterns live in:
.../super-admin/dashboard/services/super-admin-dashboard.service.ts.../organization/dashboard/services/organization-dashboard.service.ts.../store/reports/services/reports-data.service.tsVendix does not use one single cache shape.
Current patterns include:
Map caches keyed by params/entity idswithCache(key, factory)shareReplay({ bufferSize: 1, refCount: true }) and also refCount: falseDo not document a false rule that Angular service instances are always recreated on navigation or that all caches must be static globals.
vendix-frontend-statevendix-zoneless-signalsvendix-frontend-data-displaydevelopment
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.