skills/vendix-frontend-state/SKILL.md
Vendix frontend state patterns: NgRx facades with signal parallels, toSignal with initialValue, local signal state, takeUntilDestroyed, and pragmatic service-level cache/state. Trigger: When managing state.
npx skillsauth add rzyfront/vendix vendix-frontend-stateInstall 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.
apps/frontend/src/app/core/store/**vendix-zoneless-signals for critical Angular 20 rulesVendix uses a hybrid state model:
toSignal(..., { initialValue }).signal() state for component/service UI state.Legacy BehaviorSubject + destroy$ + ngOnDestroy service templates are not the primary pattern anymore.
initialValue where required.takeUntilDestroyed() in components/directives instead of ad-hoc destroy$ subjects when subscribing imperatively.vendix-zoneless-signalsvendix-frontendvendix-error-handlingdevelopment
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.